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 6.4-rc6
Date: Fri, 9 Jun 2023 14:20:18 -0600	[thread overview]
Message-ID: <54b8e861-a1a9-32b7-3160-60e323327008@kernel.dk> (raw)

Hi Linus,

Just a few minor fixes for this release:

- Fix an issue with the hardware queue nr_active, causing it to become
  imbalanced (Tian)

- Fix an issue with null_blk not releasing pages if configured as memory
  backed (Nitesh)

- Fix a locking issue in dasd (Jan)

Please pull!


The following changes since commit 2e45a49531fef55f4abbd6738c052545f53f43d4:

  Merge tag 'nvme-6.4-2023-06-01' of git://git.infradead.org/nvme into block-6.4 (2023-06-01 11:12:46 -0600)

are available in the Git repository at:

  git://git.kernel.dk/linux.git tags/block-6.4-2023-06-09

for you to fetch changes up to ccc45cb4e7271c74dbb27776ae8f73d84557f5c6:

  s390/dasd: Use correct lock while counting channel queue length (2023-06-09 11:35:52 -0600)

----------------------------------------------------------------
block-6.4-2023-06-09

----------------------------------------------------------------
Jan Höppner (1):
      s390/dasd: Use correct lock while counting channel queue length

Nitesh Shetty (1):
      null_blk: Fix: memory release when memory_backed=1

Tian Lan (1):
      blk-mq: fix blk_mq_hw_ctx active request accounting

 block/blk-mq.c                  | 8 ++++----
 drivers/block/null_blk/main.c   | 1 +
 drivers/s390/block/dasd_ioctl.c | 4 ++--
 3 files changed, 7 insertions(+), 6 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2023-06-09 20:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09 20:20 Jens Axboe [this message]
2023-06-09 21:24 ` [GIT PULL] Block fixes for 6.4-rc6 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=54b8e861-a1a9-32b7-3160-60e323327008@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