From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: [GIT PULL] Block fixes for 4.11-rc
Date: Wed, 15 Mar 2017 15:06:59 -0600 [thread overview]
Message-ID: <14098b6d-8eb1-0990-49dc-1cb911179456@kernel.dk> (raw)
Hi Linus,
Four small fixes for this cycle. This pull request contains:
- Followup fix from Neil for a fix that went in before -rc2, ensuring
that we always see the full per-task bio_list.
- Fix for blk-mq-sched from me that ensures that we retain similar
direct-to-issue behavior on running the queue.
- Fix from Sagi fixing a potential NULL pointer dereference in blk-mq on
spurious CPU unplug.
- A memory leak fix in writeback from Tahsin, fixing a case where device
removal of a mounted device can leak a struct wb_writeback_work.
Please pull!
git://git.kernel.dk/linux-block.git for-linus
----------------------------------------------------------------
Jens Axboe (1):
blk-mq-sched: don't run the queue async from blk_mq_try_issue_directly()
NeilBrown (1):
blk: Ensure users for current->bio_list can see the full list.
Sagi Grimberg (1):
blk-mq: Fix tagset reinit in the presence of cpu hot-unplug
Tahsin Erdogan (1):
writeback: fix memory leak in wb_queue_work()
block/bio.c | 12 +++++++++---
block/blk-core.c | 30 ++++++++++++++++++------------
block/blk-mq-tag.c | 3 +++
block/blk-mq.c | 9 +++++----
drivers/md/dm.c | 29 ++++++++++++++++-------------
drivers/md/raid10.c | 3 ++-
fs/fs-writeback.c | 35 +++++++++++++++++++++--------------
7 files changed, 74 insertions(+), 47 deletions(-)
--
Jens Axboe
next reply other threads:[~2017-03-15 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 21:06 Jens Axboe [this message]
2017-03-24 14:12 [GIT PULL] Block fixes for 4.11-rc Jens Axboe
2017-03-29 21:27 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=14098b6d-8eb1-0990-49dc-1cb911179456@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).