From: Jens Axboe <axboe@fb.com>
To: <torvalds@linuxfoundation.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-block@vger.kernel.org>
Subject: [GIT PULL] Block fixes for 4.4 final
Date: Tue, 22 Dec 2015 14:39:02 -0700 [thread overview]
Message-ID: <20151222213902.GA18873@kernel.dk> (raw)
Hi Linus,
Three small fixes for 4.4 final. Specifically:
- The segment issue fix from Junichi, where the old IO path does a bio
limit split before potentially bouncing the pages. We need to do that
in the right order, to ensure that limitations are met.
- A NVMe surprise removal IO hang fix from Keith.
- A use-after-free in null_blk, introduced by a previous patch in this
series. From Mike Krinkin.
Please pull!
git://git.kernel.dk/linux-block.git for-linus
----------------------------------------------------------------
Junichi Nomura (1):
block: ensure to split after potentially bouncing a bio
Keith Busch (1):
NVMe: IO ending fixes on surprise removal
Mike Krinkin (1):
null_blk: fix use-after-free error
block/blk-core.c | 4 ++--
drivers/block/null_blk.c | 6 +++---
drivers/nvme/host/pci.c | 20 +++++++++++++++++++-
3 files changed, 24 insertions(+), 6 deletions(-)
--
Jens Axboe
reply other threads:[~2015-12-22 21:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20151222213902.GA18873@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
all inboxes | Powered by JetHome®