All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: [GIT PULL] Block fixes for 4.20-rc6
Date: Fri, 7 Dec 2018 10:12:12 -0700	[thread overview]
Message-ID: <8ebbe50a-9f33-21e2-0747-e461cecb40cd@kernel.dk> (raw)

Hi Linus,

Let's try this again... We're finally happy with the DM livelock issue,
and it's also passed overnight testing and the corruption regression
test. The end result is much nicer now too, which is great. Outside of
that fix, there's a pull request for NVMe with two small fixes, and a
regression fix for BFQ from this merge window. The BFQ fix looks bigger
than it is, it's 90% comment updates.

Please pull!


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


----------------------------------------------------------------
Israel Rukshin (1):
      nvmet-rdma: fix response use after free

James Smart (1):
      nvme: validate controller state before rescheduling keep alive

Jens Axboe (2):
      blk-mq: punt failed direct issue to dispatch list
      Merge branch 'nvme-4.20' of git://git.infradead.org/nvme into for-linus

Paolo Valente (1):
      block, bfq: fix decrement of num_active_groups

 block/bfq-iosched.c        | 76 ++++++++++++++++++++++++++++++++--------------
 block/bfq-iosched.h        | 51 +++++++++++++++++++++++++++++--
 block/bfq-wf2q.c           |  5 ++-
 block/blk-mq.c             | 33 +++-----------------
 drivers/nvme/host/core.c   | 10 +++++-
 drivers/nvme/target/rdma.c |  3 +-
 6 files changed, 123 insertions(+), 55 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2018-12-07 17:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-07 17:12 Jens Axboe [this message]
2018-12-07 18:55 ` [GIT PULL] Block fixes for 4.20-rc6 pr-tracker-bot
  -- strict thread matches above, loose matches on Subject: below --
2018-12-05 20:25 Jens Axboe
2018-12-05 22:35 ` pr-tracker-bot

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=8ebbe50a-9f33-21e2-0747-e461cecb40cd@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=linux-block@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.