public inbox for linux-block@vger.kernel.org
 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.9-rc5
Date: Sat, 20 Apr 2024 09:28:17 -0600	[thread overview]
Message-ID: <b3c34e74-a86c-4595-954d-e73ef31e8cb8@kernel.dk> (raw)

Hi Linus,

Just two minor fixes that should go into the 6.9 kernel release, one
fixing a regression with partition scanning errors, and one fixing a
WARN_ON() that can get triggered if we race with a timer.

Please pull!


The following changes since commit 3ec4848913d695245716ea45ca4872d9dff097a5:

  block: fix that blk_time_get_ns() doesn't update time after schedule (2024-04-12 08:31:54 -0600)

are available in the Git repository at:

  git://git.kernel.dk/linux.git tags/block-6.9-20240420

for you to fetch changes up to 01bc4fda9ea0a6b52f12326486f07a4910666cf6:

  blk-iocost: do not WARN if iocg was already offlined (2024-04-19 08:06:24 -0600)

----------------------------------------------------------------
block-6.9-20240420

----------------------------------------------------------------
Christoph Hellwig (1):
      block: propagate partition scanning errors to the BLKRRPART ioctl

Li Nan (1):
      blk-iocost: do not WARN if iocg was already offlined

 block/bdev.c           | 29 +++++++++++++++++++----------
 block/blk-iocost.c     |  7 +++++--
 block/ioctl.c          |  3 ++-
 include/linux/blkdev.h |  2 ++
 4 files changed, 28 insertions(+), 13 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2024-04-20 15:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-20 15:28 Jens Axboe [this message]
2024-04-20 18:32 ` [GIT PULL] Block fixes for 6.9-rc5 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=b3c34e74-a86c-4595-954d-e73ef31e8cb8@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