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, johannes@sipsolutions.net,
razor@blackwall.org, nicolas.dichtel@6wind.com,
gnault@redhat.com, florent.fourcot@wifirst.fr,
pablo@netfilter.org, fw@strlen.de, jhs@mojatatu.com,
jacob.e.keller@intel.com, liuhangbin@gmail.com
Subject: Re: [PATCH net-next RESEND] genetlink: reject use of nlmsg_flags for new commands
Date: Sat, 01 Oct 2022 01:10:15 +0000 [thread overview]
Message-ID: <166458661500.24943.15612491035615658901.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220929142809.1167546-1-kuba@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 29 Sep 2022 07:28:09 -0700 you wrote:
> Commit 9c5d03d36251 ("genetlink: start to validate reserved header bytes")
> introduced extra validation for genetlink headers. We had to gate it
> to only apply to new commands, to maintain bug-wards compatibility.
> Use this opportunity (before the new checks make it to Linus's tree)
> to add more conditions.
>
> Validate that Generic Netlink families do not use nlmsg_flags outside
> of the well-understood set.
>
> [...]
Here is the summary with links:
- [net-next,RESEND] genetlink: reject use of nlmsg_flags for new commands
https://git.kernel.org/netdev/net-next/c/cff2d762cde6
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-10-01 1:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 14:28 [PATCH net-next RESEND] genetlink: reject use of nlmsg_flags for new commands Jakub Kicinski
2022-09-29 14:53 ` Pablo Neira Ayuso
2022-09-29 15:06 ` Jakub Kicinski
2022-09-29 15:49 ` Pablo Neira Ayuso
2022-09-29 15:55 ` Jakub Kicinski
2022-09-29 17:27 ` Keller, Jacob E
2022-10-01 1:10 ` 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=166458661500.24943.15612491035615658901.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=florent.fourcot@wifirst.fr \
--cc=fw@strlen.de \
--cc=gnault@redhat.com \
--cc=jacob.e.keller@intel.com \
--cc=jhs@mojatatu.com \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=razor@blackwall.org \
/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).