Re: [PATCH v3] sock: Use unsafe_memcpy() for sock_copy()

2024-03-05 Thread patchwork-bot+netdevbpf
Hello: This patch was applied to netdev/net-next.git (main) by Jakub Kicinski : On Mon, 4 Mar 2024 13:29:31 -0800 you wrote: > While testing for places where zero-sized destinations were still showing > up in the kernel, sock_copy() and inet_reqsk_clone() were found, which > are using very speci

Re: [PATCH v3] sock: Use unsafe_memcpy() for sock_copy()

2024-03-05 Thread Simon Horman
On Mon, Mar 04, 2024 at 01:29:31PM -0800, Kees Cook wrote: > While testing for places where zero-sized destinations were still showing > up in the kernel, sock_copy() and inet_reqsk_clone() were found, which > are using very specific memcpy() offsets for both avoiding a portion of > struct sock, an

[PATCH v3] sock: Use unsafe_memcpy() for sock_copy()

2024-03-04 Thread Kees Cook
While testing for places where zero-sized destinations were still showing up in the kernel, sock_copy() and inet_reqsk_clone() were found, which are using very specific memcpy() offsets for both avoiding a portion of struct sock, and copying beyond the end of it (since struct sock is really just a