From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jens Axboe <axboe@kernel.dk>, Keith Busch <keith.busch@intel.com>,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] NVMe fixes for 4.18-rc6
Date: Sun, 22 Jul 2018 14:44:13 +0200 [thread overview]
Message-ID: <20180722124413.GA16254@infradead.org> (raw)
Hi Linus,
please pull these NVMe fixes directly instead of through Jens so that
he can enjoy more of his vacation!
The following changes since commit 70dbcc2254fa2a9add74a122b9dac954c4736e01:
bsg: fix bogus EINVAL on non-data commands (2018-07-11 08:48:28 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-for-4.18
for you to fetch changes up to 9b382768135ee3ff282f828c906574a8478e036b:
nvme: fix handling of metadata_len for NVME_IOCTL_IO_CMD (2018-07-20 07:43:59 -0700)
----------------------------------------------------------------
NVMe fixes for 4.18-rc6:
- fix a regression in 4.18 that causes a memory leak on probe failure
(Keith Bush)
- fix a deadlock in the passthrough ioctl code (Scott Bauer)
- don't enable AENs if not supported (Weiping Zhang)
- fix an old regression in metadata handling in the passthrough ioctl
code (Roland Dreier)
----------------------------------------------------------------
Keith Busch (1):
nvme-pci: fix memory leak on probe failure
Roland Dreier (1):
nvme: fix handling of metadata_len for NVME_IOCTL_IO_CMD
Scott Bauer (1):
nvme: ensure forward progress during Admin passthru
Weiping Zhang (1):
nvme: don't enable AEN if not supported
drivers/nvme/host/core.c | 63 ++++++++++++++++++++++++++----------------------
drivers/nvme/host/pci.c | 12 +++++----
2 files changed, 41 insertions(+), 34 deletions(-)
reply other threads:[~2018-07-22 12:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180722124413.GA16254@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=keith.busch@intel.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--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;
as well as URLs for NNTP newsgroup(s).