Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: Leon Romanovsky <leon@kernel.org>
To: Michael Margolin <mrgolin@amazon.com>,
	Gal Pressman <gal.pressman@linux.dev>,
	Yossi Leybovich <sleybo@amazon.com>,
	Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
	Shiraz Saleem <shiraz.saleem@intel.com>,
	Steve Wise <larrystevenwise@gmail.com>,
	Firas JahJah <firasj@amazon.com>
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH rdma-next 0/2] RDMA/efa: Synchronize IRQ before freeing admin queue and EQ
Date: Mon,  7 Sep 2026 21:44:45 +0300	[thread overview]
Message-ID: <20260907-use-after-free-of-admin-queue-struct-v1-0-dd9d9267fbf4@nvidia.com> (raw)

Two similar patches for pre-existing issues.

Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
---
Leon Romanovsky (2):
      RDMA/efa: Keep admin queues alive while IRQ is registered
      RDMA/efa: Keep EQ resources alive while IRQ is registered

 drivers/infiniband/hw/efa/efa_com.c  |  7 ++-----
 drivers/infiniband/hw/efa/efa_com.h  |  1 +
 drivers/infiniband/hw/efa/efa_main.c | 33 +++++++++++++++++++--------------
 3 files changed, 22 insertions(+), 19 deletions(-)
---
base-commit: 63367df6e7255067ad6a83abe0d2799dfa491876
change-id: 20260907-use-after-free-of-admin-queue-struct-5c10e817ce3a

Best regards,
--  
Leon Romanovsky <leonro@nvidia.com>


             reply	other threads:[~2026-09-07 18:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07 18:44 Leon Romanovsky [this message]
2026-09-07 18:44 ` [PATCH rdma-next 1/2] RDMA/efa: Keep admin queues alive while IRQ is registered Leon Romanovsky
2026-09-10  8:53   ` Michael Margolin
2026-09-07 18:44 ` [PATCH rdma-next 2/2] RDMA/efa: Keep EQ resources " Leon Romanovsky
2026-09-10  8:54   ` Michael Margolin
2026-09-10 13:35 ` [PATCH rdma-next 0/2] RDMA/efa: Synchronize IRQ before freeing admin queue and EQ Leon Romanovsky

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=20260907-use-after-free-of-admin-queue-struct-v1-0-dd9d9267fbf4@nvidia.com \
    --to=leon@kernel.org \
    --cc=firasj@amazon.com \
    --cc=gal.pressman@linux.dev \
    --cc=jgg@ziepe.ca \
    --cc=larrystevenwise@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mrgolin@amazon.com \
    --cc=shiraz.saleem@intel.com \
    --cc=sleybo@amazon.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