Linux-Block Archive on lore.kernel.org
 help / color / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: axboe@kernel.dk
Cc: Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>,
	linux-nvme@lists.infradead.org, linux-block@vger.kernel.org
Subject: [GIT PULL] nvme fixes for 5.8
Date: Thu, 25 Jun 2020 18:53:33 +0200
Message-ID: <20200625165333.GA1982738@infradead.org> (raw)

The following changes since commit 0b8eb629a700c0ef15a437758db8255f8444e76c:

  block: release bip in a right way in error path (2020-06-24 08:49:07 -0600)

are available in the Git repository at:

  git://git.infradead.org/nvme.git nvme-5.8

for you to fetch changes up to c31244669f57963b6ce133a5555b118fc50aec95:

  nvme-multipath: fix bogus request queue reference put (2020-06-24 18:41:20 +0200)

----------------------------------------------------------------
Anton Eidelman (2):
      nvme-multipath: fix deadlock between ana_work and scan_work
      nvme-multipath: fix deadlock due to head->lock

Max Gurtovoy (6):
      nvme: set initial value for controller's numa node
      nvme-pci: override the value of the controller's numa node
      nvme-pci: initialize tagset numa value to the value of the ctrl
      nvme-tcp: initialize tagset numa value to the value of the ctrl
      nvme-loop: initialize tagset numa value to the value of the ctrl
      nvme-rdma: assign completion vector correctly

Sagi Grimberg (3):
      nvme: fix possible deadlock when I/O is blocked
      nvme: don't protect ns mutation with ns->head->lock
      nvme-multipath: fix bogus request queue reference put

 drivers/nvme/host/core.c      |  2 +-
 drivers/nvme/host/multipath.c | 46 +++++++++++++++++++++++++++----------------
 drivers/nvme/host/nvme.h      |  2 ++
 drivers/nvme/host/pci.c       |  6 ++++--
 drivers/nvme/host/rdma.c      |  2 +-
 drivers/nvme/host/tcp.c       |  4 ++--
 drivers/nvme/target/loop.c    |  4 ++--
 7 files changed, 41 insertions(+), 25 deletions(-)

             reply index

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-25 16:53 Christoph Hellwig [this message]
2020-06-25 18:57 ` Jens Axboe
  -- strict thread matches above, loose matches on Subject: below --
2020-07-29 17:30 Christoph Hellwig
2020-07-29 17:37 ` Jens Axboe
2020-07-29 17:09 Christoph Hellwig
2020-07-29 17:22 ` Jens Axboe
2020-07-29 17:29   ` Christoph Hellwig
2020-07-02  8:42 Christoph Hellwig
2020-07-02 18:11 ` Jens Axboe
2020-06-11  6:22 Christoph Hellwig
2020-06-11 15:10 ` Jens Axboe

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=20200625165333.GA1982738@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=kbusch@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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

Linux-Block Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-block/0 linux-block/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-block linux-block/ https://lore.kernel.org/linux-block \
		linux-block@vger.kernel.org
	public-inbox-index linux-block

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-block


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git