mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Cheng Xu <chengyou@linux.alibaba.com>
To: Myeonghun Pak <mhun512@gmail.com>,
	Kai Shen <kaishen@linux.alibaba.com>,
	Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>
Cc: linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
	Ijae Kim <ae878000@gmail.com>
Subject: Re: [PATCH] RDMA/erdma: Fix CEQ tasklet use-after-free on removal
Date: Tue, 21 Jul 2026 17:01:07 +0800	[thread overview]
Message-ID: <5dda3040-67c9-7916-436e-47125daeb310@linux.alibaba.com> (raw)
In-Reply-To: <20260721082545.47395-1-mhun512@gmail.com>



On 7/21/26 4:25 PM, Myeonghun Pak wrote:
> Each CEQ interrupt handler only schedules eqc->tasklet. The tasklet calls
> erdma_ceq_completion_handler(), which reads the DMA-coherent EQ ring
> through get_next_valid_eqe() and updates eq->dbrec through notify_eq().
> 
> erdma_ceqs_uninit() frees each CEQ IRQ and then destroys its EQ.
> free_irq() prevents another hard IRQ and waits for an in-flight handler,
> but it does not drain a tasklet that the handler already scheduled. The
> tasklet can therefore access eq->qbuf or eq->dbrec after
> erdma_eq_destroy() frees them.
> 
> Clearing ceq_cb->ready does not synchronize with a tasklet that already
> passed the check at the start of erdma_ceq_completion_handler().
> 
> Kill the tasklet after free_irq(), when no handler can schedule it again,
> and before erdma_ceq_uninit_one() releases the EQ buffers.
> 
> Fixes: f2a0a630b953 ("RDMA/erdma: Add event queue implementation")
> Cc: stable@vger.kernel.org
> Co-developed-by: Ijae Kim <ae878000@gmail.com>
> Signed-off-by: Ijae Kim <ae878000@gmail.com>
> Signed-off-by: Myeonghun Pak <mhun512@gmail.com>
> ---
> Found by static analysis only; not tested on ERDMA hardware. Testing on
> hardware, particularly device removal while CEQ interrupts are active,
> would be appreciated.
> 
>  drivers/infiniband/hw/erdma/erdma_eq.c | 1 +
>  1 file changed, 1 insertion(+)
> 

Acked-by: Cheng Xu <chengyou@linux.alibaba.com>

Thanks.

While this is unlikely to happen in practice, since the ibdev has already
been removed and no CQs should remain to generate CEQ events, this patch
makes the CEQ teardown ordering explicit and robust.

Cheng Xu


> diff --git a/drivers/infiniband/hw/erdma/erdma_eq.c b/drivers/infiniband/hw/erdma/erdma_eq.c
> index d5b9d19882b2..a8784e07acd6 100644
> --- a/drivers/infiniband/hw/erdma/erdma_eq.c
> +++ b/drivers/infiniband/hw/erdma/erdma_eq.c
> @@ -220,6 +220,7 @@ static void erdma_free_ceq_irq(struct erdma_dev *dev, u16 ceqn)
>  
>  	irq_set_affinity_hint(eqc->irq.msix_vector, NULL);
>  	free_irq(eqc->irq.msix_vector, eqc);
> +	tasklet_kill(&eqc->tasklet);
>  }
>  
>  static int create_eq_cmd(struct erdma_dev *dev, u32 eqn, struct erdma_eq *eq)

  reply	other threads:[~2026-07-21  9:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21  8:25 Myeonghun Pak
2026-07-21  9:01 ` Cheng Xu [this message]
2026-07-21 13:24   ` Jacob Moroni
2026-07-22  2:18     ` Cheng Xu
2026-07-22  8:36 ` 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=5dda3040-67c9-7916-436e-47125daeb310@linux.alibaba.com \
    --to=chengyou@linux.alibaba.com \
    --cc=ae878000@gmail.com \
    --cc=jgg@ziepe.ca \
    --cc=kaishen@linux.alibaba.com \
    --cc=leon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=mhun512@gmail.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®