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, pablo@netfilter.org
Subject: Re: [PATCH net 1/3] netfilter: nft_ct: enable labels for get case too
Date: Thu, 30 Oct 2025 01:40:08 +0000 [thread overview]
Message-ID: <176178840875.3278679.16981730284389717212.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251029135617.18274-2-fw@strlen.de>
Hello:
This series was applied to netdev/net.git (main)
by Florian Westphal <fw@strlen.de>:
On Wed, 29 Oct 2025 14:56:15 +0100 you wrote:
> conntrack labels can only be set when the conntrack has been created
> with the "ctlabel" extension.
>
> For older iptables (connlabel match), adding an "-m connlabel" rule
> turns on the ctlabel extension allocation for all future conntrack
> entries.
>
> [...]
Here is the summary with links:
- [net,1/3] netfilter: nft_ct: enable labels for get case too
https://git.kernel.org/netdev/net/c/514f1dc8f2ca
- [net,2/3] netfilter: nft_connlimit: fix possible data race on connection count
https://git.kernel.org/netdev/net/c/8d96dfdcabef
- [net,3/3] netfilter: nft_ct: add seqadj extension for natted connections
https://git.kernel.org/netdev/net/c/90918e3b6404
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:[~2025-10-30 1:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 13:56 [PATCH net 0/3] netfilter: updates for net Florian Westphal
2025-10-29 13:56 ` [PATCH net 1/3] netfilter: nft_ct: enable labels for get case too Florian Westphal
2025-10-30 1:40 ` patchwork-bot+netdevbpf [this message]
2025-10-29 13:56 ` [PATCH net 2/3] netfilter: nft_connlimit: fix possible data race on connection count Florian Westphal
2025-10-29 13:56 ` [PATCH net 3/3] netfilter: nft_ct: add seqadj extension for natted connections 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=176178840875.3278679.16981730284389717212.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 \
--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.