From: patchwork-bot+netdevbpf@kernel.org
To: Florian Westphal <fw@strlen.de>
Cc: netdev@vger.kernel.org, pabeni@redhat.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org,
netfilter-devel@vger.kernel.org
Subject: Re: [PATCH net-next 1/7] netfilter: xt_mangle: only check verdict part of return value
Date: Wed, 18 Oct 2023 10:10:23 +0000 [thread overview]
Message-ID: <169762382308.3133.9060197209130107475.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20231018085118.10829-2-fw@strlen.de>
Hello:
This series was applied to netdev/net-next.git (main)
by Florian Westphal <fw@strlen.de>:
On Wed, 18 Oct 2023 10:51:05 +0200 you wrote:
> These checks assume that the caller only returns NF_DROP without
> any errno embedded in the upper bits.
>
> This is fine right now, but followup patches will start to propagate
> such errors to allow kfree_skb_drop_reason() in the called functions,
> those would then indicate 'errno << 8 | NF_STOLEN'.
>
> [...]
Here is the summary with links:
- [net-next,1/7] netfilter: xt_mangle: only check verdict part of return value
https://git.kernel.org/netdev/net-next/c/e15e5027106f
- [net-next,2/7] netfilter: nf_tables: mask out non-verdict bits when checking return value
https://git.kernel.org/netdev/net-next/c/4d26ab0086aa
- [net-next,3/7] netfilter: conntrack: convert nf_conntrack_update to netfilter verdicts
https://git.kernel.org/netdev/net-next/c/6291b3a67ad5
- [net-next,4/7] netfilter: nf_nat: mask out non-verdict bits when checking return value
https://git.kernel.org/netdev/net-next/c/35c038b0a4be
- [net-next,5/7] netfilter: make nftables drops visible in net dropmonitor
https://git.kernel.org/netdev/net-next/c/e0d4593140b0
- [net-next,6/7] netfilter: bridge: convert br_netfilter to NF_DROP_REASON
https://git.kernel.org/netdev/net-next/c/cf8b7c1a5be7
- [net-next,7/7] netfilter: nf_tables: de-constify set commit ops function argument
https://git.kernel.org/netdev/net-next/c/256001672153
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:[~2023-10-18 10:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 8:51 [PATCH net-next 0/7] netfilter updates for net-next Florian Westphal
2023-10-18 8:51 ` [PATCH net-next 1/7] netfilter: xt_mangle: only check verdict part of return value Florian Westphal
2023-10-18 10:10 ` patchwork-bot+netdevbpf [this message]
2023-10-18 8:51 ` [PATCH net-next 2/7] netfilter: nf_tables: mask out non-verdict bits when checking " Florian Westphal
2023-10-18 8:51 ` [PATCH net-next 3/7] netfilter: conntrack: convert nf_conntrack_update to netfilter verdicts Florian Westphal
2023-10-18 8:51 ` [PATCH net-next 4/7] netfilter: nf_nat: mask out non-verdict bits when checking return value Florian Westphal
2023-10-18 8:51 ` [PATCH net-next 5/7] netfilter: make nftables drops visible in net dropmonitor Florian Westphal
2023-10-18 8:51 ` [PATCH net-next 6/7] netfilter: bridge: convert br_netfilter to NF_DROP_REASON Florian Westphal
2023-10-18 8:51 ` [PATCH net-next 7/7] netfilter: nf_tables: de-constify set commit ops function argument Florian Westphal
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=169762382308.3133.9060197209130107475.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@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 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.