Re: [PATCH 0/3] net: Cleanups for FORTIFY_SOURCE
From: Kees Cook <hidden>
Date: 2021-08-22 05:16:26
Also in:
bpf, linux-hardening, linux-wireless, lkml, netdev
Possibly related (same subject, not in this thread)
- 2021-08-21 · Re: [PATCH 0/3] net: Cleanups for FORTIFY_SOURCE · Kalle Valo <hidden>
- 2021-08-20 · Re: [PATCH 0/3] net: Cleanups for FORTIFY_SOURCE · Jakub Kicinski <kuba@kernel.org>
- 2021-08-19 · [PATCH 0/3] net: Cleanups for FORTIFY_SOURCE · Kees Cook <hidden>
On Sat, Aug 21, 2021 at 01:13:37PM +0300, Kalle Valo wrote:
Kalle Valo [off-list ref] writes:quoted
Jakub Kicinski [off-list ref] writes:quoted
On Thu, 19 Aug 2021 13:28:22 -0700 Kees Cook wrote:quoted
Hi, 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. These three changes have been living in my memcpy() series[1], but have no external dependencies. It's probably better to have these go via netdev.Thanks. Kalle, Saeed - would you like to take the relevant changes? Presumably they would get into net-next anyway by the time the merge window opens.Ok, I'll take patch 1 to wireless-drivers-next.Correction: I'll take patches 1 and 3 to wireless-drivers-next.
Great; thanks! -- Kees Cook