From: Sagi Grimberg <sagi@grimberg.me>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Keith Busch <keith.busch@intel.com>,
Christoph Hellwig <hch@lst.de>,
linux-nvme@lists.infradead.org
Subject: [GIT PULL] second round of nvme updates for 5.4
Date: Thu, 12 Sep 2019 09:41:51 -0700 [thread overview]
Message-ID: <20190912164151.7788-1-sagi@grimberg.me> (raw)
Hey Jens,
This is the second batch of nvme updates for 5.4.
Highlights includes:
- controller reset and namespace scan races fixes
- nvme discovery log change uevent support
- naming improvements from Keith
- multiple discovery controllers reject fix from James
- some regular cleanups from various people
The following changes since commit 0a67b5a926e63ff5492c3c675eab5900580d056d:
block: fix race between switching elevator and removing queues (2019-09-12 07:13:22 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git nvme-5.4
for you to fetch changes up to 5f8badbcbeac298a77ee634a10a375f3e66923f9:
nvmet: fix a wrong error status returned in error log page (2019-09-12 08:50:46 -0700)
----------------------------------------------------------------
Amit (1):
nvmet: fix a wrong error status returned in error log page
Colin Ian King (1):
nvme: tcp: remove redundant assignment to variable ret
Edmund Nadolski (1):
nvme: include admin_q sync with nvme_sync_queues
Israel Rukshin (1):
nvme: Remove redundant assignment of cq vector
James Smart (2):
nvme-fc: Fail transport errors with NVME_SC_HOST_PATH
nvme: Treat discovery subsystems as unique subsystems
Keith Busch (1):
nvme: Assign subsys instance from first ctrl
Markus Elfring (1):
nvmet: Use PTR_ERR_OR_ZERO() in nvmet_init_discovery()
Sagi Grimberg (10):
nvme: fail cancelled commands with NVME_SC_HOST_PATH_ERROR
nvme-tcp: fail command with NVME_SC_HOST_PATH_ERROR send failed
nvme: pass status to nvme_error_status
nvme: make nvme_identify_ns propagate errors back
nvme: make nvme_report_ns_ids propagate error back
nvme: fix ns removal hang when failing to revalidate due to a transient error
nvme-fabrics: allow discovery subsystems accept a kato
nvme: enable aen regardless of the presence of I/O queues
nvme: add uevent variables for controller devices
nvme: send discovery log page change events to userspace
drivers/nvme/host/core.c | 158 +++++++++++++++++++++++++++++-----------
drivers/nvme/host/fabrics.c | 12 +--
drivers/nvme/host/fc.c | 37 ++++++++--
drivers/nvme/host/pci.c | 1 -
drivers/nvme/host/tcp.c | 4 +-
drivers/nvme/target/admin-cmd.c | 8 +-
drivers/nvme/target/discovery.c | 4 +-
7 files changed, 153 insertions(+), 71 deletions(-)
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2019-09-12 16:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 16:41 Sagi Grimberg [this message]
2019-09-12 17:20 ` [GIT PULL] second round of nvme updates for 5.4 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=20190912164151.7788-1-sagi@grimberg.me \
--to=sagi@grimberg.me \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).