public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Edward Srouji <edwards@nvidia.com>
Cc: Leon Romanovsky <leon@kernel.org>,
	Chiara Meiohas <cmeiohas@nvidia.com>,
	Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>,
	Gal Pressman <galpress@amazon.com>,
	Mark Bloch <markb@mellanox.com>,
	Steve Wise <larrystevenwise@gmail.com>,
	Mark Zhang <markzhang@nvidia.com>,
	Neta Ostrovsky <netao@nvidia.com>,
	Patrisious Haddad <phaddad@nvidia.com>,
	Doug Ledford <dledford@redhat.com>,
	Matan Barak <matanb@mellanox.com>,
	majd@mellanox.com, Maor Gottlieb <maorg@mellanox.com>,
	linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
	Michael Guralnik <michaelgur@nvidia.com>,
	Maher Sanalla <msanalla@nvidia.com>
Subject: Re: [PATCH rdma-next v3 0/5] RDMA: Stability and race condition fixes
Date: Wed, 29 Apr 2026 22:49:56 -0300	[thread overview]
Message-ID: <20260430014956.GA928887@nvidia.com> (raw)
In-Reply-To: <20260427-security-bug-fixes-v3-0-4621fa52de0e@nvidia.com>

On Mon, Apr 27, 2026 at 02:02:31PM +0300, Edward Srouji wrote:
> This series addresses several stability issues in RDMA core and the
> mlx5 driver.
> 
> Patches 1-2 fix xarray race conditions in the mlx5 SRQ and DCT destroy
> paths where a concurrent create can reuse the same firmware object
> number right after firmware releases it, causing the destroy path to
> incorrectly erase the newly created entry.
> 
> The remaining patches are independent fixes.
> 
> Signed-off-by: Edward Srouji <edwards@nvidia.com>
> ---
> Changes in v3:
> - Dropped restrack destroy-ordering fixes (patches 1-6 in v2) to
>   rework them in a dedicated series based on code-review feedback
> - Rebased onto latest for-next
> - Link to v2: https://lore.kernel.org/r/20260406-security-bug-fixes-v2-0-ee8815fa81b7@nvidia.com
> 
> Changes in v2:
> - Added patch "RDMA/mlx5: Remove raw RSS QP restrack tracking" to
>   also suppress broken tracking for raw RSS QPs, which suffer from
>   the same silent failures as DCTs
> - Link to v1: https://lore.kernel.org/r/20260325-security-bug-fixes-v1-0-c8332981ad26@nvidia.com
> 
> ---
> Edward Srouji (2):
>       RDMA/mlx5: Fix UAF in SRQ destroy due to race with create
>       RDMA/mlx5: Fix UAF in DCT destroy due to race with create
> 
> Maher Sanalla (1):
>       IB/core: Fix IPv6 netlink message size in ib_nl_ip_send_msg()
> 
> Michael Guralnik (2):
>       RDMA/core: Fix rereg_mr use-after-free race
>       RDMA/mlx5: Fix null-ptr-deref in Raw Packet QP creation

Applied to for-rc

Jason

      parent reply	other threads:[~2026-04-30  1:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-27 11:02 [PATCH rdma-next v3 0/5] RDMA: Stability and race condition fixes Edward Srouji
2026-04-27 11:02 ` [PATCH rdma-next v3 1/5] RDMA/mlx5: Fix UAF in SRQ destroy due to race with create Edward Srouji
2026-04-27 11:02 ` [PATCH rdma-next v3 2/5] RDMA/mlx5: Fix UAF in DCT " Edward Srouji
2026-04-29 19:46   ` Jason Gunthorpe
2026-04-27 11:02 ` [PATCH rdma-next v3 3/5] IB/core: Fix IPv6 netlink message size in ib_nl_ip_send_msg() Edward Srouji
2026-04-27 11:02 ` [PATCH rdma-next v3 4/5] RDMA/core: Fix rereg_mr use-after-free race Edward Srouji
2026-04-27 11:02 ` [PATCH rdma-next v3 5/5] RDMA/mlx5: Fix null-ptr-deref in Raw Packet QP creation Edward Srouji
2026-04-30  1:49 ` Jason Gunthorpe [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=20260430014956.GA928887@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=cmeiohas@nvidia.com \
    --cc=dennis.dalessandro@cornelisnetworks.com \
    --cc=dledford@redhat.com \
    --cc=edwards@nvidia.com \
    --cc=galpress@amazon.com \
    --cc=larrystevenwise@gmail.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=majd@mellanox.com \
    --cc=maorg@mellanox.com \
    --cc=markb@mellanox.com \
    --cc=markzhang@nvidia.com \
    --cc=matanb@mellanox.com \
    --cc=michaelgur@nvidia.com \
    --cc=msanalla@nvidia.com \
    --cc=netao@nvidia.com \
    --cc=phaddad@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox