mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Prathamesh Deshpande <prathameshdeshpande7@gmail.com>
Cc: saeedm@nvidia.com, leon@kernel.org, tariqt@nvidia.com,
	mbloch@nvidia.com, andrew+netdev@lunn.ch, davem@davemloft.net,
	edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com,
	dtatulea@nvidia.com, cjubran@nvidia.com, cratiu@nvidia.com,
	erezsh@mellanox.com, valex@mellanox.com, netdev@vger.kernel.org,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v2] net/mlx5e: IPOIB, Fix QPN lookup race
Date: Fri, 06 Nov 2026 20:40:17 +0000	[thread overview]
Message-ID: <179399761792.859444.16113939657791512927.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261031225749.14214-1-prathameshdeshpande7@gmail.com>

Hello:

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

On Sat, 31 Oct 2026 22:57:13 +0000 you wrote:
> The parent RX completion path can load a QPN hash entry before
> mlx5i_pkey_del_qpn() unlinks and frees it, then dereference freed memory.
> 
> Use RCU hlist operations and defer freeing with kfree_rcu(). The existing
> RCU read-side section in mlx5e_napi_poll() covers the lookup. Keep ht_lock
> for writers and acquire it before looking up the entry to delete.
> 
> [...]

Here is the summary with links:
  - [net,v2] net/mlx5e: IPOIB, Fix QPN lookup race
    https://git.kernel.org/netdev/net/c/29066b0fc046

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-06 20:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-31 22:57 Prathamesh Deshpande
2026-10-31 23:03 ` netdev-bot+sinfo
2026-11-05 18:48 ` Tariq Toukan
2026-11-06 20: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=179399761792.859444.16113939657791512927.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=cjubran@nvidia.com \
    --cc=cratiu@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=dtatulea@nvidia.com \
    --cc=edumazet@kernel.org \
    --cc=erezsh@mellanox.com \
    --cc=kuba@kernel.org \
    --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=prathameshdeshpande7@gmail.com \
    --cc=saeedm@nvidia.com \
    --cc=tariqt@nvidia.com \
    --cc=valex@mellanox.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
all inboxes | Powered by JetHome®