All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Tariq Toukan <tariqt@nvidia.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
	kuba@kernel.org, netdev@vger.kernel.org, pabeni@redhat.com,
	dlinkin@nvidia.com, fmancera@suse.de, gal@nvidia.com,
	idosch@nvidia.com, jianbol@nvidia.com, kuniyu@google.com,
	leon@kernel.org, linux-kernel@vger.kernel.org,
	linux-rdma@vger.kernel.org, mbloch@nvidia.com,
	razor@blackwall.org, roid@nvidia.com, saeedm@nvidia.com,
	vladbu@nvidia.com
Subject: Re: [PATCH net] net/mlx5e: Release FIB event work flows before dropping RTNL
Date: Sat, 21 Nov 2026 00:40:07 +0000	[thread overview]
Message-ID: <179522160728.860209.2078425140293366542.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261118143653.1915247-1-tariqt@nvidia.com>

Hello:

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

On Wed, 18 Nov 2026 16:36:53 +0200 you wrote:
> From: Gal Pressman <gal@nvidia.com>
> 
> The FIB event work, neigh update work and the neigh stats work all use
> flow->tmp_list to hold the encap flows they work on, while RTNL is what
> keeps them from using it at the same time.
> 
> mlx5e_tc_fib_event_work() drops RTNL before it is done with its list.
> A neigh work can then take the same flows while the FIB work is still
> walking them, and the two overwrite each other's list.
> 
> [...]

Here is the summary with links:
  - [net] net/mlx5e: Release FIB event work flows before dropping RTNL
    https://git.kernel.org/netdev/net/c/bfccb4e44e47

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-11-21  0:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-18 14:36 [PATCH net] net/mlx5e: Release FIB event work flows before dropping RTNL Tariq Toukan
2026-11-18 14:49 ` sashiko-bot
2026-11-21  0:40 ` 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=179522160728.860209.2078425140293366542.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dlinkin@nvidia.com \
    --cc=edumazet@kernel.org \
    --cc=fmancera@suse.de \
    --cc=gal@nvidia.com \
    --cc=idosch@nvidia.com \
    --cc=jianbol@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=kuniyu@google.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=razor@blackwall.org \
    --cc=roid@nvidia.com \
    --cc=saeedm@nvidia.com \
    --cc=tariqt@nvidia.com \
    --cc=vladbu@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.