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 5.12
Date: Fri, 19 Mar 2021 08:14:12 +0100 [thread overview]
Message-ID: <YFRPRP/WLS/5FCSc@infradead.org> (raw)
The following changes since commit 1e28eed17697bcf343c6743f0028cc3b5dd88bf0:
Linux 5.12-rc3 (2021-03-14 14:41:02 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-5.12-20210319
for you to fetch changes up to bac04454ef9fada009f0572576837548b190bf94:
nvmet-tcp: fix kmap leak when data digest in use (2021-03-18 05:39:18 +0100)
----------------------------------------------------------------
nvme fixes for 5.12
- fix tag allocation for keep alive
- fix a unit mismatch for the Write Zeroes limits
- various TCP transport fixes (Sagi Grimberg, Elad Grupi)
- fix iosqes and iocqes validation for discovery controllers (Sagi Grimberg)
----------------------------------------------------------------
Christoph Hellwig (4):
nvme-fabrics: only reserve a single tag
nvme: merge nvme_keep_alive into nvme_keep_alive_work
nvme: allocate the keep alive request using BLK_MQ_REQ_NOWAIT
nvme: fix Write Zeroes limitations
Elad Grupi (1):
nvmet-tcp: fix kmap leak when data digest in use
Sagi Grimberg (5):
nvme-tcp: fix a NULL deref when receiving a 0-length r2t PDU
nvme-tcp: fix misuse of __smp_processor_id with preemption enabled
nvme-tcp: fix possible hang when failing to set io queues
nvme-rdma: fix possible hang when failing to set io queues
nvmet: don't check iosqes,iocqes for discovery controllers
drivers/nvme/host/core.c | 64 +++++++++++++++------------------------------
drivers/nvme/host/fabrics.h | 7 +++++
drivers/nvme/host/fc.c | 4 +--
drivers/nvme/host/rdma.c | 11 +++++---
drivers/nvme/host/tcp.c | 20 ++++++++++----
drivers/nvme/target/core.c | 17 +++++++++---
drivers/nvme/target/loop.c | 4 +--
drivers/nvme/target/tcp.c | 2 +-
8 files changed, 69 insertions(+), 60 deletions(-)
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2021-03-19 7:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 7:14 Christoph Hellwig [this message]
2021-03-19 12:41 ` [GIT PULL] nvme fixes for 5.12 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2021-03-12 9:25 Christoph Hellwig
2021-03-12 14:21 ` Jens Axboe
2021-03-12 19:59 ` Christoph Hellwig
2021-03-12 20:01 ` Jens Axboe
2021-03-12 20:20 ` Christoph Hellwig
2021-03-12 20:24 ` Jens Axboe
2021-03-05 16:11 Christoph Hellwig
2021-03-05 16:13 ` Jens Axboe
2021-03-04 17:59 Christoph Hellwig
2021-03-04 20:26 ` 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=YFRPRP/WLS/5FCSc@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).