diff options
author | Kuniyuki Iwashima <kuniyu@amazon.com> | 2023-10-09 18:31:52 +0300 |
---|---|---|
committer | Paolo Abeni <pabeni@redhat.com> | 2023-10-12 10:15:15 +0300 |
commit | e2bca4870fdaf855651ee80b083d892599c5d982 (patch) | |
tree | e7b39472334d3b0ec8b61e3f5b61846a36ce2c9e /net/core/sock_reuseport.c | |
parent | 71c299c711d1f44f0bf04f1fea66baad565240f1 (diff) | |
download | linux-e2bca4870fdaf855651ee80b083d892599c5d982.tar.xz |
af_packet: Fix fortified memcpy() without flex array.
Sergei Trofimovich reported a regression [0] caused by commit a0ade8404c3b
("af_packet: Fix warning of fortified memcpy() in packet_getname().").
It introduced a flex array sll_addr_flex in struct sockaddr_ll as a
union-ed member with sll_addr to work around the fortified memcpy() check.
However, a userspace program uses a struct that has struct sockaddr_ll in
the middle, where a flex array is illegal to exist.
include/linux/if_packet.h:24:17: error: flexible array member 'sockaddr_ll::<unnamed union>::<unnamed struct>::sll_addr_flex' not at end of 'struct packet_info_t'
24 | __DECLARE_FLEX_ARRAY(unsigned char, sll_addr_flex);
| ^~~~~~~~~~~~~~~~~~~~
To fix the regression, let's go back to the first attempt [1] telling
memcpy() the actual size of the array.
Reported-by: Sergei Trofimovich <slyich@gmail.com>
Closes: https://github.com/NixOS/nixpkgs/pull/252587#issuecomment-1741733002 [0]
Link: https://lore.kernel.org/netdev/20230720004410.87588-3-kuniyu@amazon.com/ [1]
Fixes: a0ade8404c3b ("af_packet: Fix warning of fortified memcpy() in packet_getname().")
Signed-off-by: Kuniyuki Iwashima <kuniyu@amazon.com>
Link: https://lore.kernel.org/r/20231009153151.75688-1-kuniyu@amazon.com
Signed-off-by: Paolo Abeni <pabeni@redhat.com>
Diffstat (limited to 'net/core/sock_reuseport.c')
0 files changed, 0 insertions, 0 deletions