All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ido Schimmel <idosch@nvidia.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	pabeni@redhat.com, edumazet@kernel.org, dsahern@kernel.org,
	horms@kernel.org, andrew+netdev@lunn.ch, petrm@nvidia.com
Subject: Re: [PATCH net 0/2] ipv6: Fix suspicious RCU usage in route hardware flags notification
Date: Tue, 20 Oct 2026 21:30:08 +0000	[thread overview]
Message-ID: <179253180827.220085.5504005327866544536.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261019140337.2886875-1-idosch@nvidia.com>

Hello:

This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 19 Oct 2026 17:03:35 +0300 you wrote:
> fib6_info_hw_flags_set() is called by drivers to update the hardware
> flags of an IPv6 route and to emit a notification when
> fib_notify_on_flag_change is set. Drivers call it from process context
> without RTNL or RCU, so when the route uses a nexthop object, building
> the notification triggers suspicious RCU usage splats.
> 
> Patch #1 fixes the problem by holding RCU while building the
> notification.
> 
> [...]

Here is the summary with links:
  - [net,1/2] ipv6: Hold RCU when emitting route hardware flags notification
    https://git.kernel.org/netdev/net/c/7c9cb1edaf8f
  - [net,2/2] selftests: netdevsim: Add FIB notification tests for nexthop objects
    https://git.kernel.org/netdev/net/c/b5dc3fde8b92

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-10-20 21:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19 14:03 [PATCH net 0/2] ipv6: Fix suspicious RCU usage in route hardware flags notification Ido Schimmel
2026-10-19 14:03 ` [PATCH net 1/2] ipv6: Hold RCU when emitting " Ido Schimmel
2026-10-19 17:23   ` Eric Dumazet
2026-10-20 20:31   ` David Ahern
2026-10-19 14:03 ` [PATCH net 2/2] selftests: netdevsim: Add FIB notification tests for nexthop objects Ido Schimmel
2026-10-19 17:39   ` Eric Dumazet
2026-10-20 20:33   ` David Ahern
2026-10-20 21:30 ` 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=179253180827.220085.5504005327866544536.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@kernel.org \
    --cc=horms@kernel.org \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.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.