summaryrefslogtreecommitdiff
path: root/fs/btrfs/tree-log.c
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <mchehab+samsung@kernel.org>2018-05-15 15:23:16 -0400
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-08-03 07:47:42 +0200
commit76dbad5017b54ba3602f54e4a4fa1a3f6ad82b94 (patch)
tree0e5c47fc54a9507166baa5ed4e2e47750cbfb05e /fs/btrfs/tree-log.c
parent605adcb4bbc6183b841a9adb9a2ddb62b9bc06a2 (diff)
media: cec-pin-error-inj: avoid a false-positive Spectre detection
[ Upstream commit a3d71f256c8a8b5d51ea0dfd09cd85ce3a09d9e1 ] The current logic makes Smatch to false-detect a Spectre variant 1 vulnerability. The problem is that it initializes an u32 indirectly from user space input. After trying to write a fixup, after a while I realized that, in practice, this shouldn't be a problem, as an u32 is initialized from u8, but it took some time to discover it. So, do some code cleanup to make it clearer for both humans and machines about the valid range for "op". Fix this warning: drivers/media/cec/cec-pin-error-inj.c:170 cec_pin_error_inj_parse_line() warn: potential spectre issue 'pin->error_inj_args' Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org> Signed-off-by: Hans Verkuil <hans.verkuil@cisco.com> Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org> Signed-off-by: Sasha Levin <alexander.levin@microsoft.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'fs/btrfs/tree-log.c')
0 files changed, 0 insertions, 0 deletions