From: Jens Axboe <axboe@fb.com>
To: <torvalds@linuxfoundation.org>
Cc: <linux-block@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Block fixes for 4.5-final
Date: Fri, 4 Mar 2016 15:02:42 -0700 [thread overview]
Message-ID: <20160304220242.GA25415@kernel.dk> (raw)
Hi Linus,
Round 2 of this. I cut back to the bare necessities, the patch is still
larger than it usually would be at this time, due to the number of NVMe
fixes in there. This pull request contains:
- The 4 core fixes from Ming, that fix both problems with exceeding the
virtual boundary limit in case of merging, and the gap checking for
cloned bio's.
- NVMe fixes from Keith and Christoph:
- Regression on larger user commands, causing problems with
reading log pages (for instance). This touches both NVMe,
and the block core since that is now generally utilized also
for these types of commands.
- Hot removal fixes.
- User exploitable issue with passthrough IO commands, if !length
is given, causing us to fault on writing to the zero
page.
- Fix for a hang under error conditions
- And finally, the current series regression for umount with cgroup
writeback, where the final flush would happen async and hence open up
window after umount where the device wasn't consistent. fsck right
after umount would show this. From Tejun.
Please pull this round, and we'll ensure that the load is distributed
better going forward. Thanks.
git://git.kernel.dk/linux-block.git for-linus2
----------------------------------------------------------------
Christoph Hellwig (4):
nvme: set queue limits for the admin queue
nvme: fix max_segments integer truncation
block: fix blk_rq_get_max_sectors for driver private requests
block: support large requests in blk_rq_map_user_iov
Keith Busch (7):
NVMe: Don't unmap controller registers on reset
NVMe: Use IDA for namespace disk naming
NVMe: Fix namespace removal deadlock
NVMe: Simplify device reset failure
NVMe: Move error handling to failed reset handler
NVMe: Don't allow unsupported flags
NVMe: Fix 0-length integrity payload
Ming Lei (4):
block: bio: introduce helpers to get the 1st and last bvec
block: check virt boundary in bio_will_gap()
block: get the 1st and last bvec via helpers
block: merge: get the 1st and last bvec via helpers
Tejun Heo (1):
writeback: flush inode cgroup wb switches instead of pinning super_block
block/blk-map.c | 91 ++++++++++++++++++----------
block/blk-merge.c | 8 +--
drivers/nvme/host/core.c | 111 ++++++++++++++++++++++++----------
drivers/nvme/host/nvme.h | 8 +++
drivers/nvme/host/pci.c | 149 ++++++++++++++++++++++++++++------------------
fs/fs-writeback.c | 54 +++++++++++++----
fs/super.c | 1 +
include/linux/bio.h | 37 ++++++++++++
include/linux/blkdev.h | 25 +++++---
include/linux/writeback.h | 5 ++
10 files changed, 341 insertions(+), 148 deletions(-)
--
Jens Axboe
next reply other threads:[~2016-03-04 22:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-04 22:02 Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-03 17:25 [GIT PULL] Block fixes for 4.5-final Jens Axboe
2016-03-03 20:57 ` Linus Torvalds
2016-03-03 21:11 ` Linus Torvalds
2016-03-03 21:13 ` Jens Axboe
2016-03-03 21:11 ` Jens Axboe
2016-03-03 21:20 ` Linus Torvalds
2016-03-03 21:28 ` Jens Axboe
2016-03-03 21:53 ` Jens Axboe
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=20160304220242.GA25415@kernel.dk \
--to=axboe@fb.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linuxfoundation.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;
as well as URLs for NNTP newsgroup(s).