From: Jens Axboe <axboe@fb.com>
To: <torvalds@linux-foundation.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] Block core followup bits for -rc1
Date: Wed, 4 Jun 2014 15:02:43 -0600 [thread overview]
Message-ID: <20140604210243.GA32698@kernel.dk> (raw)
Hi Linus,
A few minor (but important) fixes for blk-mq for the -rc1 window.
- Hot removal potential oops fix for single queue devices. From me.
- Two merged patches in late May meant that we accidentally lost a fix
for freeing an active queue. Fix that up. From me.
- A change of the blk_mq_tag_to_rq() API, passing in blk_mq_tags, to
make life considerably easier for scsi-mq. From me.
- A schedule-while-atomic fix from Ming Lei, which would hit if the tag
space was exhausted.
- Missing __percpu annotation in one place in blk-mq. Found by the magic
Wu compile bot due to code being moved around by the previous patch,
but it's actually an older issue. From Ming Lei.
- Clearing of tag of a flush request at end_io time. From Ming Lei.
Please pull!
git://git.kernel.dk/linux-block.git for-linus
----------------------------------------------------------------
Jens Axboe (3):
blk-mq: handle NULL req return from blk_map_request in single queue mode
blk-mq: fix regression from commit 624dbe475416
blk-mq: let blk_mq_tag_to_rq() take blk_mq_tags as the main parameter
Ming Lei (4):
blk-mq: move blk_mq_get_ctx/blk_mq_put_ctx to mq private header
blk-mq: fix schedule from atomic context
blk-mq: fix sparse warning on missed __percpu annotation
block: mq flush: clear flush_rq's tag in flush_end_io()
block/blk-flush.c | 2 +-
block/blk-mq-tag.c | 48 ++++++++++++++--------
block/blk-mq-tag.h | 2 +-
block/blk-mq.c | 83 +++++++++++++++++++--------------------
block/blk-mq.h | 45 +++++++++++++++++++++
drivers/block/mtip32xx/mtip32xx.c | 4 +-
include/linux/blk-mq.h | 2 +-
include/linux/blkdev.h | 2 +-
8 files changed, 123 insertions(+), 65 deletions(-)
--
Jens Axboe
reply other threads:[~2014-06-04 21:02 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=20140604210243.GA32698@kernel.dk \
--to=axboe@fb.com \
--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 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.