diff options
author | Kees Cook <keescook@chromium.org> | 2021-11-18 16:46:46 -0800 |
---|---|---|
committer | Kalle Valo <kvalo@codeaurora.org> | 2021-11-29 12:45:17 +0200 |
commit | 601d2293e27f6fb37b30b836d724333a4ed79fe9 (patch) | |
tree | ea08d944e8ecac34de6053c11c8eb5840cae318b /tools/testing/selftests/bpf/prog_tests/prog_array_init.c | |
parent | 642a57475b30213ebac1f7061eaf4d0415d9c5a1 (diff) |
intersil: Use struct_group() for memcpy() region
In preparation for FORTIFY_SOURCE performing compile-time and run-time
field bounds checking for memcpy(), memmove(), and memset(), avoid
intentionally writing across neighboring fields.
Use struct_group() in struct hfa384x_tx_frame around members
frame_control, duration_id, addr1, addr2, addr3, and seq_ctrl, so they
can be referenced together. This will allow memcpy() and sizeof() to
more easily reason about sizes, improve readability, and avoid future
warnings about writing beyond the end of frame_control.
"pahole" shows no size nor member offset changes to struct
hfa384x_tx_frame. "objdump -d" shows no object code changes.
Signed-off-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Link: https://lore.kernel.org/r/20211119004646.2347920-1-keescook@chromium.org
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/prog_array_init.c')
0 files changed, 0 insertions, 0 deletions