All of lore.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 followup fixes for 4.4-rc3
Date: Wed, 25 Nov 2015 11:24:30 -0700	[thread overview]
Message-ID: <20151125182430.GA10504@kernel.dk> (raw)

Hi Linus,

Wasn't going to send off a new pull before next week, but the blk flush
fix from Jan from the other day introduced a regression. It's rare
enough not to have hit during testing, since it requires both a device
that rejects the first flush, and bad timing while it does that. But
since someone did hit it, let's get the revert into 4.4-rc3 so we don't
have a released rc with that known issue.

Apart from that revert, three other fixes:

- From Christoph, a fix for a missing unmap in NVMe request preparation.

- An NVMe fix from Nishanth that fixes data corruption on powerpc.

- Also from Christoph, fix a list_del() attempt on blk-mq that didn't
  have a matching list_add() at timer start.

Please pull!


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


----------------------------------------------------------------
Christoph Hellwig (2):
      nvme: add missing unmaps in nvme_queue_rq
      block: fix blk_abort_request for blk-mq drivers

Jens Axboe (1):
      Revert "blk-flush: Queue through IO scheduler when flush not required"

Nishanth Aravamudan (1):
      NVMe: default to 4k device page size

 block/blk-flush.c       |  2 +-
 block/blk-timeout.c     |  8 +++++---
 drivers/nvme/host/pci.c | 30 ++++++++++++++++++------------
 3 files changed, 24 insertions(+), 16 deletions(-)

-- 
Jens Axboe


                 reply	other threads:[~2015-11-25 18:24 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=20151125182430.GA10504@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.