All of lore.kernel.org
 help / color / mirror / Atom feed
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.6-rc1
Date: Thu, 24 Mar 2016 15:04:40 -0600	[thread overview]
Message-ID: <20160324210440.GA22851@kernel.dk> (raw)

Hi Linus,

Final round of fixes for this merge window - some of this has come up
after the initial pull request, and some of it was put in a post-merge
branch before the merge window. This pull request contains:

- Fix for a bad check for an error on dma mapping in the mtip32xx
  driver, from Alexey Khoroshilov.

- A set of fixes for lightnvm, from Javier, Matias, and Wenwei.

- An NVMe completion record corruption fix from Marta, ensuring that we
  read things in the right order.

- Two writeback fixes from Tejun, marked for stable@ as well.

- A blk-mq sw queue iterator fix from Thomas, fixing an oops for sparse
  CPU maps. They hit this in the hot plug/unplug rework.

Please pull!


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


----------------------------------------------------------------
Alexey Khoroshilov (1):
      mtip32xx: fix checks for dma mapping errors

Javier González (2):
      lightnvm: do not reserve lun on l2p loading
      lightnvm: do not load L2P table if not supported

Marta Rybczynska (1):
      nvme: avoid cqe corruption when update at the same time as read

Matias Bjorling (1):
      nvme: lightnvm: return ppa completion status

Tejun Heo (2):
      writeback, cgroup: fix premature wb_put() in locked_inode_to_wb_and_lock_list()
      writeback, cgroup: fix use of the wrong bdi_writeback which mismatches the inode

Thomas Gleixner (1):
      blk-mq: Use proper cpumask iterator

Wenwei Tao (3):
      null_blk: add lightnvm null_blk device to the nullb_list
      lightnvm: specify target's logical address area
      lightnvm: add a bitmap of luns

 block/blk-mq-sysfs.c              |   6 ++-
 block/blk-mq.c                    |   3 +-
 drivers/block/mtip32xx/mtip32xx.c |   4 +-
 drivers/block/null_blk.c          |   3 +-
 drivers/lightnvm/core.c           |   7 +++
 drivers/lightnvm/gennvm.c         |  84 ++++++++++++++++++++++++++++-
 drivers/lightnvm/gennvm.h         |   6 +++
 drivers/lightnvm/rrpc.c           | 109 +++++++++++++++++++++++++++-----------
 drivers/lightnvm/rrpc.h           |   1 +
 drivers/nvme/host/lightnvm.c      |  17 +++++-
 drivers/nvme/host/pci.c           |  24 +++++----
 fs/fs-writeback.c                 |  37 ++++++++-----
 include/linux/blk-mq.h            |  14 -----
 include/linux/lightnvm.h          |  14 +++++
 14 files changed, 251 insertions(+), 78 deletions(-)

-- 
Jens Axboe

                 reply	other threads:[~2016-03-24 21:04 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=20160324210440.GA22851@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 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.