From: patchwork-bot+netdevbpf@kernel.org
To: Nikola Z. Ivanov <zlatistiv@gmail.com>
Cc: dsahern@kernel.org, idosch@nvidia.com, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, kuniyu@google.com, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+84d4a405ed798b40c96d@syzkaller.appspotmail.com
Subject: Re: [PATCH net] ipv6: Change allocation flags to match rcu_read_lock section requirements
Date: Thu, 23 Jul 2026 16:20:14 +0000 [thread overview]
Message-ID: <178482361439.2769750.329022673168190868.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260719105759.558050-1-zlatistiv@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sun, 19 Jul 2026 13:57:59 +0300 you wrote:
> Since the call to __ip6_del_rt_siblings has been converted under
> rcu read lock and it only has one call point
> we should no longer block or yield.
>
> Our stack trace from the syzbot reproducer looks as follows:
>
> __ip6_del_rt_siblings
> rtnl_notify (Here we pass gfp_any() -> GFP_KERNEL)
> nlmsg_notify
> nlmsg_multicast
> nlmsg_multicast_filtered
> netlink_broadcast_filtered (GFP_KERNEL passed from earlier)
>
> [...]
Here is the summary with links:
- [net] ipv6: Change allocation flags to match rcu_read_lock section requirements
https://git.kernel.org/netdev/net/c/313a123e1fca
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-07-23 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-19 10:57 [PATCH net] ipv6: Change allocation flags to match rcu_read_lock section requirements Nikola Z. Ivanov
2026-07-19 12:55 ` Ido Schimmel
2026-07-23 16:20 ` patchwork-bot+netdevbpf [this message]
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=178482361439.2769750.329022673168190868.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzbot+84d4a405ed798b40c96d@syzkaller.appspotmail.com \
--cc=zlatistiv@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox