From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Keith Busch <kbusch@kernel.org>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: [GIT PULL] second round of nvme updates for Linux 5.13
Date: Thu, 15 Apr 2021 17:03:09 +0200 [thread overview]
Message-ID: <YHhVrZD7/Q4qtFjL@infradead.org> (raw)
The following changes since commit f8ee34a929a4adf6d29a7ef2145393e6865037ad:
lightnvm: deprecated OCSSD support and schedule it for removal in Linux 5.15 (2021-04-13 09:16:12 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-5.13-2021-04-15
for you to fetch changes up to d6609084b0b81abc74dc9db0281cdd0e074df5d4:
nvme: fix NULL derefence in nvme_ctrl_fast_io_fail_tmo_show/store (2021-04-15 08:12:56 +0200)
----------------------------------------------------------------
nvme updates for Linux 5.13
- refactor the ioctl coee
- fix a segmentation fault during io parsing error in nvmet-tcp
(Elad Grupi)
- fix NULL derefence in nvme_ctrl_fast_io_fail_tmo_show/store
(Gopal Tiwari)
- properly respect the sgl_threshold flag in nvme-pci (Niklas Cassel)
- misc cleanups (Niklas Cassel, Amit Engel, Minwoo Im, Colin Ian King)
----------------------------------------------------------------
Amit Engel (1):
nvmet-fc: simplify nvmet_fc_alloc_hostport
Christoph Hellwig (11):
nvme: cleanup setting the disk name
nvme: pass a user pointer to nvme_nvm_ioctl
nvme: factor out a nvme_ns_ioctl helper
nvme: simplify the compat ioctl handling
nvme: simplify block device ioctl handling for the !multipath case
nvme: don't bother to look up a namespace for controller ioctls
nvme: move the ioctl code to a separate file
nvme: factor out a nvme_tryget_ns_head helper
nvme: move nvme_ns_head_ops to multipath.c
nvme: factor out nvme_ns_open and nvme_ns_release helpers
nvme: let namespace probing continue for unsupported features
Colin Ian King (1):
nvmet: fix a spelling mistake "nubmer" -> "number"
Elad Grupi (1):
nvmet-tcp: fix a segmentation fault during io parsing error
Gopal Tiwari (1):
nvme: fix NULL derefence in nvme_ctrl_fast_io_fail_tmo_show/store
Minwoo Im (1):
nvme: add a nvme_ns_head_multipath helper
Niklas Cassel (4):
nvme-pci: don't simple map sgl when sgls are disabled
nvme-pci: remove single trailing whitespace
nvme-multipath: remove single trailing whitespace
nvme: remove single trailing whitespace
drivers/nvme/host/Makefile | 2 +-
drivers/nvme/host/core.c | 562 +++++------------------------------------
drivers/nvme/host/ioctl.c | 455 +++++++++++++++++++++++++++++++++
drivers/nvme/host/lightnvm.c | 8 +-
drivers/nvme/host/multipath.c | 51 +++-
drivers/nvme/host/nvme.h | 40 +--
drivers/nvme/host/pci.c | 4 +-
drivers/nvme/host/zns.c | 4 +-
drivers/nvme/target/configfs.c | 2 +-
drivers/nvme/target/fc.c | 77 +++---
drivers/nvme/target/tcp.c | 39 ++-
11 files changed, 669 insertions(+), 575 deletions(-)
create mode 100644 drivers/nvme/host/ioctl.c
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2021-04-15 15:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-15 15:03 Christoph Hellwig [this message]
2021-04-15 18:16 ` [GIT PULL] second round of nvme updates for Linux 5.13 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=YHhVrZD7/Q4qtFjL@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
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).