From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, willemdebruijn.kernel@gmail.com,
keescook@chromium.org, horms@kernel.org, kuni1840@gmail.com,
netdev@vger.kernel.org, slyich@gmail.com
Subject: Re: [PATCH v1 net] af_packet: Fix fortified memcpy() without flex array.
Date: Thu, 12 Oct 2023 07:30:24 +0000 [thread overview]
Message-ID: <169709582458.1593.10221782315144344818.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231009153151.75688-1-kuniyu@amazon.com>
Hello:
This patch was applied to netdev/net.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Mon, 9 Oct 2023 08:31:52 -0700 you wrote:
> 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.
>
> [...]
Here is the summary with links:
- [v1,net] af_packet: Fix fortified memcpy() without flex array.
https://git.kernel.org/netdev/net/c/e2bca4870fda
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2023-10-12 7:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 15:31 [PATCH v1 net] af_packet: Fix fortified memcpy() without flex array Kuniyuki Iwashima
2023-10-09 16:01 ` Kees Cook
2023-10-09 17:12 ` Kuniyuki Iwashima
2023-10-09 17:21 ` Kees Cook
2023-10-12 7:30 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=169709582458.1593.10221782315144344818.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--cc=kuniyu@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=slyich@gmail.com \
--cc=willemdebruijn.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.