From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org, Keith Busch <kbusch@kernel.org>,
Jens Axboe <axboe@fb.com>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>,
linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme updates for Linux 6.15
Date: Thu, 10 Apr 2025 17:01:30 +0200 [thread overview]
Message-ID: <Z_fdSjFqscMuzxYq@infradead.org> (raw)
The following changes since commit 72070e57b0a518ec8e562a2b68fdfc796ef5c040:
selftests: ublk: fix test_stripe_04 (2025-04-03 20:13:38 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-6.15-2025-04-10
for you to fetch changes up to 70289ae5cac4d3a39575405aaf63330486cea030:
nvmet-fc: put ref when assoc->del_work is already scheduled (2025-04-09 13:03:56 +0200)
----------------------------------------------------------------
nvme updates for Linux 6.15
- nvmet fc/fcloop refcounting fixes (Daniel Wagner)
- fix missed namespace/ANA scans (Hannes Reinecke)
- fix a use after free in the new TCP netns support (Kuniyuki Iwashima)
- fix a NULL instead of false review in multipath (Uday Shankar)
----------------------------------------------------------------
Daniel Wagner (8):
nvmet-fcloop: swap list_add_tail arguments
nvmet-fcloop: replace kref with refcount
nvmet-fcloop: add ref counting to lport
nvmet-fc: inline nvmet_fc_delete_assoc
nvmet-fc: inline nvmet_fc_free_hostport
nvmet-fc: update tgtport ref per assoc
nvmet-fc: take tgtport reference only once
nvmet-fc: put ref when assoc->del_work is already scheduled
Hannes Reinecke (2):
nvme: requeue namespace scan on missed AENs
nvme: re-read ANA log page after ns scan completes
Kuniyuki Iwashima (1):
nvme-tcp: fix use-after-free of netns by kernel TCP socket.
Uday Shankar (1):
nvme: multipath: fix return value of nvme_available_path
drivers/nvme/host/core.c | 9 ++++++
drivers/nvme/host/multipath.c | 2 +-
drivers/nvme/host/tcp.c | 2 ++
drivers/nvme/target/fc.c | 60 ++++++++++++-----------------------
drivers/nvme/target/fcloop.c | 74 +++++++++++++++++++++++--------------------
5 files changed, 72 insertions(+), 75 deletions(-)
next reply other threads:[~2025-04-10 15:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 15:01 Christoph Hellwig [this message]
2025-04-10 15:29 ` [GIT PULL] nvme updates for Linux 6.15 Jens Axboe
2025-04-10 15:40 ` 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=Z_fdSjFqscMuzxYq@infradead.org \
--to=hch@infradead.org \
--cc=axboe@fb.com \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--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