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 5.12-rc5
Date: Sat, 27 Mar 2021 19:04:37 -0600 [thread overview]
Message-ID: <e5bb408c-534d-4255-8a97-e525e686c596@kernel.dk> (raw)
Hi Linus,
- Fix regression from this merge window with the xarray partition
change, which allowed partition counts that overflow the u8 that holds
the partition number (Ming)
- Fix zone append warning (Johannes)
- Segmentation count fix for multipage bvecs (David)
- Partition scan fix (Chris)
Please pull!
The following changes since commit d38b4d289486daee01c1fdf056b46b7cdfe72e9e:
Merge tag 'nvme-5.12-20210319' of git://git.infradead.org/nvme into block-5.12 (2021-03-19 06:40:47 -0600)
are available in the Git repository at:
git://git.kernel.dk/linux-block.git tags/block-5.12-2021-03-27
for you to fetch changes up to e82fc7855749aa197740a60ef22c492c41ea5d5f:
block: don't create too many partitions (2021-03-27 09:22:18 -0600)
----------------------------------------------------------------
block-5.12-2021-03-27
----------------------------------------------------------------
Chris Chiu (1):
block: clear GD_NEED_PART_SCAN later in bdev_disk_changed
David Jeffery (1):
block: recalculate segment count for multi-segment discards correctly
Johannes Thumshirn (1):
block: support zone append bvecs
Ming Lei (1):
block: don't create too many partitions
block/bio.c | 21 ++++++++++++++++++---
block/blk-merge.c | 8 ++++++++
block/partitions/core.c | 7 +++++++
fs/block_dev.c | 4 ++--
4 files changed, 35 insertions(+), 5 deletions(-)
--
Jens Axboe
next reply other threads:[~2021-03-28 1:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 1:04 Jens Axboe [this message]
2021-03-28 19:11 ` [GIT PULL] Block fixes for 5.12-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=e5bb408c-534d-4255-8a97-e525e686c596@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.