From: patchwork-bot+netdevbpf@kernel.org
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, keescook@chromium.org, nathan@kernel.org,
ndesaulniers@google.com, trix@redhat.com, llvm@lists.linux.dev
Subject: Re: [PATCH net-next] netlink: remove the flex array from struct nlmsghdr
Date: Sat, 19 Nov 2022 03:20:16 +0000 [thread overview]
Message-ID: <166882801614.12875.6125141397212888728.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221118033903.1651026-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 17 Nov 2022 19:39:03 -0800 you wrote:
> I've added a flex array to struct nlmsghdr in
> commit 738136a0e375 ("netlink: split up copies in the ack construction")
> to allow accessing the data easily. It leads to warnings with clang,
> if user space wraps this structure into another struct and the flex
> array is not at the end of the container.
>
> Reviewed-by: Kees Cook <keescook@chromium.org>
> Link: https://lore.kernel.org/all/20221114023927.GA685@u2004-local/
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
>
> [...]
Here is the summary with links:
- [net-next] netlink: remove the flex array from struct nlmsghdr
https://git.kernel.org/netdev/net-next/c/c73a72f4cbb4
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:[~2022-11-19 3:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 3:39 [PATCH net-next] netlink: remove the flex array from struct nlmsghdr Jakub Kicinski
2022-11-19 3:20 ` 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=166882801614.12875.6125141397212888728.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=keescook@chromium.org \
--cc=kuba@kernel.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=trix@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).