Linux block layer
 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 5.7-rc1
Date: Thu, 9 Apr 2020 18:07:56 -0700	[thread overview]
Message-ID: <0d580c9a-be04-0b48-0594-17a0339df1b5@kernel.dk> (raw)

Hi Linus,

Here's a set of fixes that should go into this merge window. This pull
request contains:

- NVMe pull request from Christoph with various fixes

- Better discard support for loop (Evan)

- Only call ->commit_rqs() if we have queued IO (Keith)

- blkcg offlining fixes (Tejun)

Please pull! 


  git://git.kernel.dk/linux-block.git tags/block-5.7-2020-04-09


----------------------------------------------------------------
Christoph Hellwig (1):
      block: fix busy device checking in blk_drop_partitions

Evan Green (2):
      loop: Report EOPNOTSUPP properly
      loop: Better discard support for block devices

Israel Rukshin (2):
      nvme-rdma: Replace comma with a semicolon
      nvmet-rdma: fix double free of rdma queue

James Smart (3):
      nvme-fcloop: fix deallocation of working context
      nvmet-fc: fix typo in comment
      nvme-fc: Revert "add module to ops template to allow module references"

Jens Axboe (1):
      Merge branch 'nvme-5.7' of git://git.infradead.org/nvme into block-5.7

Keith Busch (1):
      blk-mq: don't commit_rqs() if none were queued

Nick Bowler (1):
      nvme: fix compat address handling in several ioctls

Sagi Grimberg (7):
      nvme-tcp: fix possible crash in write_zeroes processing
      nvme-tcp: don't poll a non-live queue
      nvme-tcp: fix possible crash in recv error flow
      nvme: inherit stable pages constraint in the mpath stack device
      nvmet: fix NULL dereference when removing a referral
      nvmet-rdma: fix bonding failover possible NULL deref
      nvme: fix deadlock caused by ANA update wrong locking

Tejun Heo (2):
      blkcg: rename blkcg->cgwb_refcnt to ->online_pin and always use it
      blkcg: don't offline parent blkcg first

 block/blk-cgroup.c              |  22 ++++-
 block/blk-mq.c                  |   9 +-
 block/partitions/core.c         |   2 +-
 drivers/block/loop.c            |  49 +++++++---
 drivers/nvme/host/core.c        |  34 +++++--
 drivers/nvme/host/fc.c          |  14 +--
 drivers/nvme/host/multipath.c   |   4 +-
 drivers/nvme/host/rdma.c        |   2 +-
 drivers/nvme/host/tcp.c         |  18 ++--
 drivers/nvme/target/configfs.c  |  10 +-
 drivers/nvme/target/fc.c        |   2 +-
 drivers/nvme/target/fcloop.c    |  77 ++++++++++-----
 drivers/nvme/target/rdma.c      | 205 +++++++++++++++++++++++++++-------------
 drivers/scsi/lpfc/lpfc_nvme.c   |   2 -
 drivers/scsi/qla2xxx/qla_nvme.c |   1 -
 include/linux/blk-cgroup.h      |  43 ++++-----
 include/linux/nvme-fc-driver.h  |   4 -
 mm/backing-dev.c                |   6 +-
 18 files changed, 324 insertions(+), 180 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2020-04-10  1:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-10  1:07 Jens Axboe [this message]
2020-04-10 14:37 ` [GIT PULL] Block fixes for 5.7-rc1 Jens Axboe
2020-04-10 17:25   ` Linus Torvalds
2020-04-11  4:04     ` Jens Axboe
2020-04-10 17:30   ` pr-tracker-bot
2020-04-10 17:30 ` 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=0d580c9a-be04-0b48-0594-17a0339df1b5@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox