From: Keith Busch <kbusch@kernel.org>
To: axboe@kernel.dk
Cc: hch@lst.de, sagi@grimberg.me, linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme fixes for Linux 6.9
Date: Thu, 9 May 2024 11:48:31 -0600 [thread overview]
Message-ID: <Zj0MbxfIuy8Hd03c@kbusch-mbp.mynextlight.net> (raw)
The following changes since commit ffd379c13fc0ab2c7c4313e7a01c71d9d202cc88:
block: set default max segment size in case of virt_boundary (2024-05-06 20:27:51 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-6.9-2024-05-09
for you to fetch changes up to 73964c1d07c054376f1b32a62548571795159148:
nvmet-rdma: fix possible bad dereference when freeing rsps (2024-05-08 06:17:01 -0700)
----------------------------------------------------------------
nvme fixes for Linux 6.9
- nvme target fixes (Sagi, Dan, Maurizo)
- new vendor quirk for broken MSI (Sean)
----------------------------------------------------------------
Dan Carpenter (1):
nvmet: prevent sprintf() overflow in nvmet_subsys_nsid_exists()
Maurizio Lombardi (1):
nvmet-auth: return the error code to the nvmet_auth_ctrl_hash() callers
Sagi Grimberg (2):
nvmet: make nvmet_wq unbound
nvmet-rdma: fix possible bad dereference when freeing rsps
Sean Anderson (1):
nvme-pci: Add quirk for broken MSIs
drivers/nvme/host/nvme.h | 5 +++++
drivers/nvme/host/pci.c | 14 +++++++++++---
drivers/nvme/target/auth.c | 2 +-
drivers/nvme/target/configfs.c | 5 ++---
drivers/nvme/target/core.c | 3 ++-
drivers/nvme/target/rdma.c | 16 ++++------------
6 files changed, 25 insertions(+), 20 deletions(-)
next reply other threads:[~2024-05-09 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 17:48 Keith Busch [this message]
2024-05-09 17:50 ` [GIT PULL] nvme fixes for Linux 6.9 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2024-05-02 13:00 Keith Busch
2024-05-02 13:46 ` Jens Axboe
2024-04-04 16:59 Keith Busch
2024-04-04 19:23 ` 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=Zj0MbxfIuy8Hd03c@kbusch-mbp.mynextlight.net \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--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).