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
Subject: Re: [PATCH net 1/2] netfilter: nft_socket: make cgroup match work in input too
Date: Tue, 12 Apr 2022 17:50:11 +0000 [thread overview]
Message-ID: <164978581188.6445.15587964483471417022.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220412094246.448055-2-pablo@netfilter.org>
Hello:
This series was applied to netdev/net.git (master)
by Pablo Neira Ayuso <pablo@netfilter.org>:
On Tue, 12 Apr 2022 11:42:45 +0200 you wrote:
> From: Florian Westphal <fw@strlen.de>
>
> cgroupv2 helper function ignores the already-looked up sk
> and uses skb->sk instead.
>
> Just pass sk from the calling function instead; this will
> make cgroup matching work for udp and tcp in input even when
> edemux did not set skb->sk already.
>
> [...]
Here is the summary with links:
- [net,1/2] netfilter: nft_socket: make cgroup match work in input too
https://git.kernel.org/netdev/net/c/05ae2fba821c
- [net,2/2] netfilter: nf_tables: nft_parse_register can return a negative value
https://git.kernel.org/netdev/net/c/6c6f9f31ecd4
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-04-12 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 9:42 [PATCH net 0/2] Netfilter fixes for net Pablo Neira Ayuso
2022-04-12 9:42 ` [PATCH net 1/2] netfilter: nft_socket: make cgroup match work in input too Pablo Neira Ayuso
2022-04-12 17:50 ` patchwork-bot+netdevbpf [this message]
2022-04-12 9:42 ` [PATCH net 2/2] netfilter: nf_tables: nft_parse_register can return a negative value 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=164978581188.6445.15587964483471417022.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--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.