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/7] netfilter: nf_tables: netlink notifier might race to release objects
Date: Thu, 03 Nov 2022 03:00:17 +0000 [thread overview]
Message-ID: <166744441724.18046.4557814101769741140.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221102184659.2502-2-pablo@netfilter.org>
Hello:
This series was applied to netdev/net.git (master)
by Pablo Neira Ayuso <pablo@netfilter.org>:
On Wed, 2 Nov 2022 19:46:53 +0100 you wrote:
> commit release path is invoked via call_rcu and it runs lockless to
> release the objects after rcu grace period. The netlink notifier handler
> might win race to remove objects that the transaction context is still
> referencing from the commit release path.
>
> Call rcu_barrier() to ensure pending rcu callbacks run to completion
> if the list of transactions to be destroyed is not empty.
>
> [...]
Here is the summary with links:
- [net,1/7] netfilter: nf_tables: netlink notifier might race to release objects
https://git.kernel.org/netdev/net/c/d4bc8271db21
- [net,2/7] netfilter: nf_tables: release flow rule object from commit path
https://git.kernel.org/netdev/net/c/26b5934ff419
- [net,3/7] ipvs: use explicitly signed chars
https://git.kernel.org/netdev/net/c/5c26159c97b3
- [net,4/7] ipvs: fix WARNING in __ip_vs_cleanup_batch()
https://git.kernel.org/netdev/net/c/3d00c6a0da8d
- [net,5/7] ipvs: fix WARNING in ip_vs_app_net_cleanup()
https://git.kernel.org/netdev/net/c/5663ed63adb9
- [net,6/7] netfilter: nf_nat: Fix possible memory leak in nf_nat_init()
https://git.kernel.org/netdev/net/c/cbc1dd5b659f
- [net,7/7] netfilter: ipset: enforce documented limit to prevent allocating huge memory
https://git.kernel.org/netdev/net/c/510841da1fcc
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-11-03 3:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-02 18:46 [PATCH net 0/7] Netfilter/IPVS fixes for net Pablo Neira Ayuso
2022-11-02 18:46 ` [PATCH net 1/7] netfilter: nf_tables: netlink notifier might race to release objects Pablo Neira Ayuso
2022-11-03 3:00 ` patchwork-bot+netdevbpf [this message]
2022-11-02 18:46 ` [PATCH net 2/7] netfilter: nf_tables: release flow rule object from commit path Pablo Neira Ayuso
2022-11-02 18:46 ` [PATCH net 3/7] ipvs: use explicitly signed chars Pablo Neira Ayuso
2022-11-02 18:46 ` [PATCH net 4/7] ipvs: fix WARNING in __ip_vs_cleanup_batch() Pablo Neira Ayuso
2022-11-02 18:46 ` [PATCH net 5/7] ipvs: fix WARNING in ip_vs_app_net_cleanup() Pablo Neira Ayuso
2022-11-02 18:46 ` [PATCH net 6/7] netfilter: nf_nat: Fix possible memory leak in nf_nat_init() Pablo Neira Ayuso
2022-11-02 18:46 ` [PATCH net 7/7] netfilter: ipset: enforce documented limit to prevent allocating huge memory 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=166744441724.18046.4557814101769741140.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 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).