diff options
author | Kees Cook <keescook@chromium.org> | 2021-12-13 14:33:26 -0800 |
---|---|---|
committer | Jason Gunthorpe <jgg@nvidia.com> | 2021-12-14 20:21:22 -0400 |
commit | c2ed5611afd75a37fa9f77ea71c661c2e087525a (patch) | |
tree | 1351860dcdfd976ec46f9e5f9c2ed60ff84343c0 /drivers/virt | |
parent | e517f76a3cb24b2a4749e0348390aece24cf9925 (diff) | |
download | linux-stable-c2ed5611afd75a37fa9f77ea71c661c2e087525a.tar.gz linux-stable-c2ed5611afd75a37fa9f77ea71c661c2e087525a.tar.bz2 linux-stable-c2ed5611afd75a37fa9f77ea71c661c2e087525a.zip |
iw_cxgb4: Use memset_startat() for cpl_t5_pass_accept_rpl
In preparation for FORTIFY_SOURCE performing compile-time and run-time
field bounds checking for memset(), avoid intentionally writing across
neighboring fields.
Use memset_startat() so memset() doesn't get confused about writing beyond
the destination member that is intended to be the starting point of
zeroing through the end of the struct. Additionally, since everything
appears to perform a roundup (including allocation), just change the size
of the struct itself and add a build-time check to validate the expected
size.
Link: https://lore.kernel.org/r/20211213223331.135412-13-keescook@chromium.org
Signed-off-by: Kees Cook <keescook@chromium.org>
Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
Diffstat (limited to 'drivers/virt')
0 files changed, 0 insertions, 0 deletions