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.11
Date: Thu, 7 Jan 2021 18:42:51 +0100 [thread overview]
Message-ID: <X/dIG7478C6ahGvo@infradead.org> (raw)
The following changes since commit aebf5db917055b38f4945ed6d621d9f07a44ff30:
block: fix use-after-free in disk_part_iter_next (2021-01-05 11:35:17 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-5.11-2021-01-07
for you to fetch changes up to 2b59787a223b79228fed9ade1bf6936194ddb8cd:
nvme: remove the unused status argument from nvme_trace_bio_complete (2021-01-06 10:30:37 +0100)
----------------------------------------------------------------
nvme updates for 5.11:
- fix a race in the nvme-tcp send code (Sagi Grimberg)
- fix a list corruption in an nvme-rdma error path (Israel Rukshin)
- avoid a possible double fetch in nvme-pci (Lalithambika Krishnakumar)
- add the susystem NQN quirk for a Samsung driver (Gopal Tiwari)
- fix two compiler warnings in nvme-fcloop (James Smart)
- don't call sleeping functions from irq context in nvme-fc (James Smart)
- remove an unused argument (Max Gurtovoy)
- remove unused exports (Minwoo Im)
----------------------------------------------------------------
Gopal Tiwari (1):
nvme-pci: mark Samsung PM1725a as IGNORE_DEV_SUBNQN
Israel Rukshin (1):
nvmet-rdma: Fix list_del corruption on queue establishment failure
James Smart (2):
nvme-fc: avoid calling _nvme_fc_abort_outstanding_ios from interrupt context
nvme-fcloop: Fix sscanf type and list_first_entry_or_null warnings
Lalithambika Krishnakumar (1):
nvme: avoid possible double fetch in handling CQE
Max Gurtovoy (1):
nvme: remove the unused status argument from nvme_trace_bio_complete
Minwoo Im (1):
nvme: unexport functions with no external caller
Sagi Grimberg (1):
nvme-tcp: Fix possible race of io_work and direct send
drivers/nvme/host/core.c | 8 +++-----
drivers/nvme/host/fc.c | 15 ++++++++++++++-
drivers/nvme/host/nvme.h | 9 ++-------
drivers/nvme/host/pci.c | 10 ++++++----
drivers/nvme/host/tcp.c | 12 +++++++++++-
drivers/nvme/target/fcloop.c | 7 ++++---
drivers/nvme/target/rdma.c | 10 ++++++++++
7 files changed, 50 insertions(+), 21 deletions(-)
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2021-01-07 17:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 17:42 Christoph Hellwig [this message]
2021-01-07 17:58 ` [GIT PULL] nvme fixes for 5.11 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2021-01-14 19:29 Christoph Hellwig
2021-01-15 2:48 ` Jens Axboe
2021-01-21 8:32 Christoph Hellwig
2021-01-21 12:41 ` Jens Axboe
2021-01-28 18:56 Christoph Hellwig
2021-01-28 18:58 ` Jens Axboe
2021-02-04 15:07 Christoph Hellwig
2021-02-04 15:25 ` Jens Axboe
2021-02-04 15:27 ` Christoph Hellwig
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=X/dIG7478C6ahGvo@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