From: Keith Busch <kbusch@kernel.org>
To: axboe@kernel.dk
Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me
Subject: [GIT PULL] nvme fixes for Linux 6.18
Date: Thu, 20 Nov 2025 08:35:56 -0700 [thread overview]
Message-ID: <aR81XMUX0mILxPpz@kbusch-mbp> (raw)
The following changes since commit 0194b65ab571430130a11f8500894bb88f7af2c0:
nvme-pci: use blk_map_iter for p2p metadata (2025-10-22 19:46:25 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-6.18-2025-11-20
for you to fetch changes up to 0a2c5495b6d1ecb0fa18ef6631450f391a888256:
nvme: nvme-fc: Ensure ->ioerr_work is cancelled in nvme_fc_delete_ctrl() (2025-11-17 09:00:42 -0800)
----------------------------------------------------------------
nvme fixes for Linux 6.18
- Admin queue use-after-free fix (Keith)
- Target authentication fix (Alistar)
- Multipath lockdep fix (Shin'ichiro)
- FC transport teardown fixes (Ewan)
----------------------------------------------------------------
Alistair Francis (1):
nvmet-auth: update sc_c in target host hash calculation
Ewan D. Milne (2):
nvme: nvme-fc: move tagset removal to nvme_fc_delete_ctrl()
nvme: nvme-fc: Ensure ->ioerr_work is cancelled in nvme_fc_delete_ctrl()
Keith Busch (1):
nvme: fix admin request_queue lifetime
Shin'ichiro Kawasaki (1):
nvme-multipath: fix lockdep WARN due to partition scan work
drivers/nvme/host/core.c | 3 ++-
drivers/nvme/host/fc.c | 15 ++++++++-------
drivers/nvme/host/multipath.c | 2 +-
drivers/nvme/target/auth.c | 4 ++--
drivers/nvme/target/fabrics-cmd-auth.c | 1 +
drivers/nvme/target/nvmet.h | 1 +
6 files changed, 15 insertions(+), 11 deletions(-)
next reply other threads:[~2025-11-20 15:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 15:35 Keith Busch [this message]
2025-11-20 15:42 ` [GIT PULL] nvme fixes for Linux 6.18 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2025-10-16 18:52 Keith Busch
2025-10-17 1:47 ` 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=aR81XMUX0mILxPpz@kbusch-mbp \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.