public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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.6-rc
Date: Fri, 15 Apr 2016 16:02:03 -0600	[thread overview]
Message-ID: <20160415220203.GA25853@kernel.dk> (raw)

Hi Linus,

A few fixes for the current series. This pull request contains:

- Two fixes for NVMe. One fixes a reset race that can be triggered by
  repeated insert/removal of the module. The other fixes an issue on
  some platforms, where we get probe timeouts since legacy interrupts
  isn't working. This used not to be a problem since we had the worker
  thread poll for completions, but since that was killed off, it means
  those poor souls can't successfully probe their NVMe device. Use a
  proper IRQ check and probe (msi-x -> msi ->legacy), like most other
  drivers to work around this. Both from Keith.

- A loop corruption issue with offset in iters, from Ming Lei.

- A fix for not having the partition stat per cpu ref count initialized
  before sending out the KOBJ_ADD, which could cause user space to
  access the counter prior to initialization. Also from Ming Lei.

- A fix for using the wrong congestion state, from Kaixu Xia.

Please pull!


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


----------------------------------------------------------------
Kaixu Xia (1):
      writeback: fix the wrong congested state variable definition

Keith Busch (2):
      NVMe: Fix reset/remove race
      NVMe: Always use MSI/MSI-x interrupts

Ming Lei (2):
      block: partition: initialize percpuref before sending out KOBJ_ADD
      block: loop: fix filesystem corruption in case of aio/dio

 block/partition-generic.c | 13 ++++++++++---
 drivers/block/loop.c      |  6 ++++++
 drivers/nvme/host/pci.c   | 31 +++++++++++++++++++------------
 mm/backing-dev.c          |  4 ++--
 4 files changed, 37 insertions(+), 17 deletions(-)

-- 
Jens Axboe

                 reply	other threads:[~2016-04-15 22: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=20160415220203.GA25853@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