aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/event_analyzing_sample.py
diff options
context:
space:
mode:
authorKees Cook <[email protected]>2022-09-27 08:37:01 -0700
committerJakub Kicinski <[email protected]>2022-09-29 18:44:07 -0700
commit7cba18332e3635aaae60e4e7d4e52849de50d91b (patch)
tree8b18c900a236a5a65f6c612d0728687c5ef4abcd /tools/perf/scripts/python/event_analyzing_sample.py
parent5361660af6d35f2b84926f5fcbf0491a9c21d82e (diff)
net: sched: cls_u32: Avoid memcpy() false-positive warning
To work around a misbehavior of the compiler's ability to see into composite flexible array structs (as detailed in the coming memcpy() hardening series[1]), use unsafe_memcpy(), as the sizing, bounds-checking, and allocation are all very tightly coupled here. This silences the false-positive reported by syzbot: memcpy: detected field-spanning write (size 80) of single field "&n->sel" at net/sched/cls_u32.c:1043 (size 16) [1] https://lore.kernel.org/linux-hardening/[email protected] Cc: Cong Wang <[email protected]> Cc: Jiri Pirko <[email protected]> Reported-by: [email protected] Link: https://lore.kernel.org/lkml/[email protected]/ Signed-off-by: Kees Cook <[email protected]> Reviewed-by: Jamal Hadi Salim <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions