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] nvme fixes for Linux 5.16
Date: Fri, 10 Dec 2021 07:15:53 +0100 [thread overview]
Message-ID: <YbLwmaLqilKEW0Q/@infradead.org> (raw)
The following changes since commit e3f9387aea67742b9d1f4de8e5bb2fd08a8a4584:
loop: Use pr_warn_once() for loop_control_remove() warning (2021-11-29 06:44:45 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-5.16-2021-12-10
for you to fetch changes up to 30e32f300be6d0160fd1b3fc6d0f62917acd9be2:
nvmet-tcp: fix possible list corruption for unexpected command failure (2021-12-08 16:36:58 +0100)
----------------------------------------------------------------
nvme fixes for Linux 5.16
- set ana_log_size to 0 after freeing ana_log_buf (Hou Tao)
- show subsys nqn for duplicate cntlids (Keith Busch)
- disable namespace access for unsupported metadata (Keith Busch)
- report write pointer for a full zone as zone start + zone len
(Niklas Cassel)
- fix use after free when disconnecting a reconnecting ctrl
(Ruozhu Li)
- fix a list corruption in nvmet-tcp (Sagi Grimberg)
----------------------------------------------------------------
Hou Tao (1):
nvme-multipath: set ana_log_size to 0 after free ana_log_buf
Keith Busch (2):
nvme: show subsys nqn for duplicate cntlids
nvme: disable namespace access for unsupported metadata
Niklas Cassel (1):
nvme: report write pointer for a full zone as zone start + zone len
Ruozhu Li (1):
nvme: fix use after free when disconnecting a reconnecting ctrl
Sagi Grimberg (1):
nvmet-tcp: fix possible list corruption for unexpected command failure
drivers/nvme/host/core.c | 23 ++++++++++++++++++-----
drivers/nvme/host/multipath.c | 3 ++-
drivers/nvme/host/nvme.h | 2 +-
drivers/nvme/host/zns.c | 5 ++++-
drivers/nvme/target/tcp.c | 9 ++++++++-
5 files changed, 33 insertions(+), 9 deletions(-)
next reply other threads:[~2021-12-10 6:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 6:15 Christoph Hellwig [this message]
2021-12-10 13:44 ` [GIT PULL] nvme fixes for Linux 5.16 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2021-11-25 14:04 Christoph Hellwig
2021-11-25 14:55 ` Jens Axboe
2021-11-25 15:05 ` Christoph Hellwig
2021-11-25 15:59 ` 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=YbLwmaLqilKEW0Q/@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