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: Thu, 25 Nov 2021 15:04:46 +0100 [thread overview]
Message-ID: <YZ+X/qGC6/w3bp2c@infradead.org> (raw)
The following changes since commit efcf5932230b9472cfdbe01c858726f29ac5ec7d:
block: avoid to touch unloaded module instance when opening bdev (2021-11-22 18:35:37 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-5.16-2021-11-25
for you to fetch changes up to 95ec70a9f3f9133304a0295af58d4f05ed27661c:
nvmet: use IOCB_NOWAIT only if the filesystem supports it (2021-11-23 17:22:43 +0100)
----------------------------------------------------------------
nvme fixes for Linux 5.16
- add a NO APST quirk for a Kioxia device (Enzo Matsumiya)
- fix write zeroes pi (Klaus Jensen)
- various TCP transport fixes (Maurizio Lombardi and Varun Prakash)
- ignore invalid fast_io_fail_tmo values (Maurizio Lombardi)
- use IOCB_NOWAIT only if the filesystem supports it (Maurizio Lombardi)
----------------------------------------------------------------
Enzo Matsumiya (1):
nvme-pci: add NO APST quirk for Kioxia device
Klaus Jensen (1):
nvme: fix write zeroes pi
Maurizio Lombardi (6):
nvmet-tcp: fix a race condition between release_queue and io_work
nvmet-tcp: add an helper to free the cmd buffers
nvmet-tcp: fix memory leak when performing a controller reset
nvme-tcp: fix memory leak when freeing a queue
nvme-fabrics: ignore invalid fast_io_fail_tmo values
nvmet: use IOCB_NOWAIT only if the filesystem supports it
Varun Prakash (2):
nvmet-tcp: fix incomplete data digest send
nvme-tcp: validate R2T PDU in nvme_tcp_handle_r2t()
drivers/nvme/host/core.c | 29 +++++++++++++++++--
drivers/nvme/host/fabrics.c | 3 ++
drivers/nvme/host/tcp.c | 61 +++++++++++++++++++--------------------
drivers/nvme/target/io-cmd-file.c | 2 ++
drivers/nvme/target/tcp.c | 44 ++++++++++++++++++++--------
5 files changed, 93 insertions(+), 46 deletions(-)
next reply other threads:[~2021-11-25 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-25 14:04 Christoph Hellwig [this message]
2021-11-25 14:55 ` [GIT PULL] nvme fixes for Linux 5.16 Jens Axboe
2021-11-25 15:05 ` Christoph Hellwig
2021-11-25 15:59 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2021-12-10 6:15 Christoph Hellwig
2021-12-10 13:44 ` 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=YZ+X/qGC6/w3bp2c@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