public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jaxboe@fusionio.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] block IO bits for 2.6.39-rc
Date: Wed, 20 Apr 2011 13:59:39 +0200	[thread overview]
Message-ID: <4DAECAAB.3040601@fusionio.com> (raw)

Hi Linus,

- Fix a long standing bug in CFQ that assumes that read_lock() implies
  rcu_read_lock() as well. No known cases of this hitting (it would have
  to be a lucky punch during IO scheduler switch), but a bug none the
  less.

- Get rid of QUEUE_FLAG_REENTER. I know you love it, but it must go.
  SCSI unconditionally does async queue runs, in most cases they don't
even need to do that. I'll pass a patch through James to correct that.

- Two buglets in the block sysfs code, missing cleanup on error and code
  clarification change.

- blk_flush_plug_list() is no longer used externally, it's only called
  by schedule(). So we can kill the export now.

Please pull!


  git://git.kernel.dk/linux-2.6-block.git for-linus

Jens Axboe (4):
      block: kill blk_flush_plug_list() export
      cfq-iosched: read_lock() does not always imply rcu_read_lock()
      block: get rid of QUEUE_FLAG_REENTER
      block: remove stale kerneldoc member from __blk_run_queue()

Liu Yuan (1):
      block, blk-sysfs: Fix an err return path in blk_register_queue()

Tao Ma (1):
      block: Remove the extra check in queue_requests_store

 block/blk-core.c                 |   13 ++-----------
 block/blk-sysfs.c                |    8 +++++---
 block/blk.h                      |    1 -
 block/cfq-iosched.c              |   20 ++++++--------------
 drivers/scsi/scsi_lib.c          |   17 +----------------
 drivers/scsi/scsi_transport_fc.c |   19 ++++---------------
 include/linux/blkdev.h           |   26 +++++++++++++-------------
 7 files changed, 31 insertions(+), 73 deletions(-)

-- 
Jens Axboe


                 reply	other threads:[~2011-04-20 11:59 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=4DAECAAB.3040601@fusionio.com \
    --to=jaxboe@fusionio.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox