Linux block layer
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: [GIT PULL] block fixes for 7.4-rc3
Date: Fri, 13 Nov 2026 05:54:11 -0700	[thread overview]
Message-ID: <0c3fd1a8-c530-44c9-9dd0-3dec5a6dea11@kernel.dk> (raw)

Hi Linus,

block fixes for this week. This pull request contains:

- ublk fixes: don't publish a new device in the idr until it's fully
  set up, and don't hold ublk_ctl_mutex across device removal, as a
  stuck filesystem on one device otherwise blocked ADD_DEV and DEL_DEV
  for every other ublk device.

- s390/dasd fixes: re-initialize the RCD buffer magic before every
  request start, fix a wrong free and refcount leak in the check_tcw
  error path, don't trust the userspace-supplied result field in the
  format check, and a typo fix.

Please pull!


The following changes since commit 28f7d31c2aeb350df9a0116093fade0a840fb4ce:

  Merge tag 'nvme-7.4-2026-11-05' of git://git.infradead.org/nvme into block-7.4 (2026-11-05 13:47:13 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux tags/block-7.4-20261112

for you to fetch changes up to 7cc2dda4f7aaf596c1796184649007151ff98f8d:

  s390/dasd: Don't trust userspace-supplied result field in format check (2026-11-12 09:18:12 -0700)

----------------------------------------------------------------
block-7.4-20261112

----------------------------------------------------------------
Mark Korenberg (2):
      ublk: publish a new device by its id only once it is set up
      ublk: don't take ublk_ctl_mutex in DEL_DEV

Stefan Haberland (4):
      s390/dasd: Fix typo 'immediatly' -> 'immediately'
      s390/dasd: Re-initialize RCD buffer with "V1.0" before every start
      s390/dasd: Fix wrong free and refcount leak in build_check_tcw error path
      s390/dasd: Don't trust userspace-supplied result field in format check

 drivers/block/ublk_drv.c        | 66 ++++++++++++++++++-------------
 drivers/s390/block/dasd.c       |  5 ++-
 drivers/s390/block/dasd_alias.c |  2 +-
 drivers/s390/block/dasd_eckd.c  | 69 +++++++++++++--------------------
 drivers/s390/block/dasd_int.h   | 17 +++++++-
 drivers/s390/block/dasd_ioctl.c |  4 +-
 6 files changed, 90 insertions(+), 73 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2026-11-13 12:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-13 12:54 Jens Axboe [this message]
2026-11-13 18:40 ` [GIT PULL] block fixes for 7.4-rc3 pr-tracker-bot

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=0c3fd1a8-c530-44c9-9dd0-3dec5a6dea11@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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