public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Jared Holzman <jholzman@nvidia.com>
To: stable@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Ming Lei <ming.lei@redhat.com>, Jens Axboe <axboe@kernel.dk>,
	Uday Shankar <ushankar@purestorage.com>
Subject: [PATCH v1 0/7] ublk: Backport to 6.14-stable: fix race between io_uring_cmd_complete_in_task and ublk_cancel_cmd
Date: Wed, 7 May 2025 01:00:11 +0300	[thread overview]
Message-ID: <11c4208b-ad97-4d26-80d7-e728ebe2552e@nvidia.com> (raw)
In-Reply-To: <20250506215511.4126251-1-jholzman@nvidia.com>


This patchset backports a series of ublk fixes from upstream to 6.14-stable.

Patch 7 fixes the race that can cause kernel panic when ublk server daemon is exiting.

It depends on patches 1-6 which simplifies & improves IO canceling when ublk server daemon
is exiting as described here:

https://lore.kernel.org/linux-block/20250416035444.99569-1-ming.lei@redhat.com/

Ming Lei (5):
  ublk: add helper of ublk_need_map_io()
  ublk: move device reset into ublk_ch_release()
  ublk: remove __ublk_quiesce_dev()
  ublk: simplify aborting ublk request
  ublk: fix race between io_uring_cmd_complete_in_task and
    ublk_cancel_cmd

Uday Shankar (2):
  ublk: properly serialize all FETCH_REQs
  ublk: improve detection and handling of ublk server exit

 drivers/block/ublk_drv.c | 550 +++++++++++++++++++++------------------
 1 file changed, 291 insertions(+), 259 deletions(-)

-- 
2.43.0


       reply	other threads:[~2025-05-06 22:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250506215511.4126251-1-jholzman@nvidia.com>
2025-05-06 22:00 ` Jared Holzman [this message]
2025-05-06 22:25   ` [PATCH v1 0/7] ublk: Backport to 6.14-stable: fix race between io_uring_cmd_complete_in_task and ublk_cancel_cmd Jared Holzman
2025-05-06 23:37 Jared Holzman
2025-05-07  8:08 ` Ming Lei
2025-05-07  9:14   ` Jared Holzman
2025-05-07  9:20 ` Greg KH

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=11c4208b-ad97-4d26-80d7-e728ebe2552e@nvidia.com \
    --to=jholzman@nvidia.com \
    --cc=axboe@kernel.dk \
    --cc=gregkh@linuxfoundation.org \
    --cc=ming.lei@redhat.com \
    --cc=stable@vger.kernel.org \
    --cc=ushankar@purestorage.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