From: patchwork-bot+netdevbpf@kernel.org
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: netfilter-devel@vger.kernel.org, davem@davemloft.net,
netdev@vger.kernel.org, kuba@kernel.org, pabeni@redhat.com,
edumazet@google.com
Subject: Re: [PATCH net 1/2] netfilter: nf_tables: stricter validation of element data
Date: Sun, 03 Jul 2022 11:30:12 +0000 [thread overview]
Message-ID: <165684781291.480.12626712312264137835.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220702191029.238563-2-pablo@netfilter.org>
Hello:
This series was applied to netdev/net.git (master)
by Pablo Neira Ayuso <pablo@netfilter.org>:
On Sat, 2 Jul 2022 21:10:27 +0200 you wrote:
> Make sure element data type and length do not mismatch the one specified
> by the set declaration.
>
> Fixes: 7d7402642eaf ("netfilter: nf_tables: variable sized set element keys / data")
> Reported-by: Hugues ANGUELKOV <hanguelkov@randorisec.fr>
> Signed-off-by: Pablo Neira Ayuso <pablo@netfilter.org>
>
> [...]
Here is the summary with links:
- [net,1/2] netfilter: nf_tables: stricter validation of element data
https://git.kernel.org/netdev/net/c/7e6bc1f6cabc
- [net,2/2] netfilter: nft_set_pipapo: release elements in clone from abort path
https://git.kernel.org/netdev/net/c/9827a0e6e23b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2022-07-03 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-02 19:10 [PATCH net 0/2] Netfilter fixes for net Pablo Neira Ayuso
2022-07-02 19:10 ` [PATCH net 1/2] netfilter: nf_tables: stricter validation of element data Pablo Neira Ayuso
2022-07-03 11:30 ` patchwork-bot+netdevbpf [this message]
2022-07-02 19:10 ` [PATCH net 2/2] netfilter: nft_set_pipapo: release elements in clone from abort path Pablo Neira Ayuso
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=165684781291.480.12626712312264137835.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.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 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.