public inbox for linux-block@vger.kernel.org
 help / color / mirror / Atom feed
From: Ming Lei <ming.lei@redhat.com>
To: Jared Holzman <jholzman@nvidia.com>
Cc: Jens Axboe <axboe@kernel.dk>,
	linux-block@vger.kernel.org,
	Uday Shankar <ushankar@purestorage.com>,
	Caleb Sander Mateos <csander@purestorage.com>,
	Guy Eisenberg <geisenberg@nvidia.com>,
	Yoav Cohen <yoav@nvidia.com>, Omri Levi <omril@nvidia.com>,
	Ofer Oshri <ofer@nvidia.com>
Subject: Re: [PATCH 0/2] ublk: fix race between io_uring_cmd_complete_in_task and ublk_cancel_cmd
Date: Fri, 25 Apr 2025 09:43:35 +0800	[thread overview]
Message-ID: <aArox0HMI386qGZd@fedora> (raw)
In-Reply-To: <f7d8a462-7685-47e0-a206-77d358ff4639@nvidia.com>

On Fri, Apr 25, 2025 at 12:10:31AM +0300, Jared Holzman wrote:
> On 23/04/2025 12:24, Ming Lei wrote:
> > Hello Jens,
> > 
> > The 2 patches try to fix race between between io_uring_cmd_complete_in_task
> > and ublk_cancel_cmd, please don't apply until Jared verifies them.
> > 
> > Jared, please test and see if the two can fix your crash issue on v6.15-rc3.
> > 
> > If you can't reproduce it on v6.15-rc3, please backport them to v6.14, and I
> > can help the backport if you need.
> > 
> > Thanks,
> > Ming
> > 
> > Ming Lei (2):
> >   ublk: call ublk_dispatch_req() for handling UBLK_U_IO_NEED_GET_DATA
> >   ublk: fix race between io_uring_cmd_complete_in_task and
> >     ublk_cancel_cmd
> > 
> >  drivers/block/ublk_drv.c | 51 ++++++++++++++++++++++++++--------------
> >  1 file changed, 34 insertions(+), 17 deletions(-)
> > 
> 
> Hi Ming,
> 
> It's a solid fix. I ran it through our automation and it passed 300 iterations without an issue. Previously we were getting crash after less than 20.
> 

Jared, thanks for the test and feedback!


> I also back-ported the patches to 6.14 and it works there too.
> 
> Will these fixes make it into 6.15? Or only 6.16?

I think it is fine for v6.15 if Jens agrees.

> 
> Also is there a 6.14 maintenance branch that could also be fixed or is it end-of-life already?

Both the two are simple enough, which may be backported to any stable tree,
IMO.


thanks,
Ming


  reply	other threads:[~2025-04-25  1:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-23  9:24 [PATCH 0/2] ublk: fix race between io_uring_cmd_complete_in_task and ublk_cancel_cmd Ming Lei
2025-04-23  9:24 ` [PATCH 1/2] ublk: call ublk_dispatch_req() for handling UBLK_U_IO_NEED_GET_DATA Ming Lei
2025-04-23 14:44   ` Caleb Sander Mateos
2025-04-23 14:52     ` Caleb Sander Mateos
2025-04-24  1:53       ` Ming Lei
2025-04-23  9:24 ` [PATCH 2/2] ublk: fix race between io_uring_cmd_complete_in_task and ublk_cancel_cmd Ming Lei
2025-04-23 15:08   ` Caleb Sander Mateos
2025-04-23 15:39     ` Ming Lei
2025-04-23 16:48       ` Caleb Sander Mateos
2025-04-24  1:47         ` Ming Lei
2025-04-25  0:55           ` Caleb Sander Mateos
2025-04-24 21:10 ` [PATCH 0/2] " Jared Holzman
2025-04-25  1:43   ` Ming Lei [this message]
2025-04-25  1:53     ` Jens Axboe

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=aArox0HMI386qGZd@fedora \
    --to=ming.lei@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=csander@purestorage.com \
    --cc=geisenberg@nvidia.com \
    --cc=jholzman@nvidia.com \
    --cc=linux-block@vger.kernel.org \
    --cc=ofer@nvidia.com \
    --cc=omril@nvidia.com \
    --cc=ushankar@purestorage.com \
    --cc=yoav@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