summaryrefslogtreecommitdiffstats
path: root/drivers/net/ethernet/intel/ice/ice_flex_pipe.c
diff options
context:
space:
mode:
authorGustavo A. R. Silva <gustavoars@kernel.org>2021-04-16 14:31:51 -0500
committerDavid S. Miller <davem@davemloft.net>2021-04-16 17:02:27 -0700
commit1e3d976dbb23b3fce544752b434bdc32ce64aabc (patch)
tree7680806e0d28d7c5a8f5e4e7e27710019a182dc9 /drivers/net/ethernet/intel/ice/ice_flex_pipe.c
parent1c86514d7fda55c5311c6b75aacb8c41b2e83999 (diff)
downloadlinux-1e3d976dbb23b3fce544752b434bdc32ce64aabc.tar.bz2
flow_dissector: Fix out-of-bounds warning in __skb_flow_bpf_to_target()
Fix the following out-of-bounds warning: net/core/flow_dissector.c:835:3: warning: 'memcpy' offset [33, 48] from the object at 'flow_keys' is out of the bounds of referenced subobject 'ipv6_src' with type '__u32[4]' {aka 'unsigned int[4]'} at offset 16 [-Warray-bounds] The problem is that the original code is trying to copy data into a couple of struct members adjacent to each other in a single call to memcpy(). So, the compiler legitimately complains about it. As these are just a couple of members, fix this by copying each one of them in separate calls to memcpy(). This helps with the ongoing efforts to globally enable -Warray-bounds and get us closer to being able to tighten the FORTIFY_SOURCE routines on memcpy(). Link: https://github.com/KSPP/linux/issues/109 Reported-by: kernel test robot <lkp@intel.com> Signed-off-by: Gustavo A. R. Silva <gustavoars@kernel.org> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/ethernet/intel/ice/ice_flex_pipe.c')
0 files changed, 0 insertions, 0 deletions