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.14
Date: Wed, 5 Mar 2025 18:39:31 -0700 [thread overview]
Message-ID: <Z8j800qyBDDkQcDh@kbusch-mbp> (raw)
The following changes since commit 70550442f28eba83b3e659618bba2b64eb91575f:
Merge tag 'nvme-6.14-2025-02-20' of git://git.infradead.org/nvme into block-6.14 (2025-02-20 17:43:59 -0700)
are available in the Git repository at:
git://git.infradead.org/nvme.git tags/nvme-6.14-2025-03-05
for you to fetch changes up to 528361c49962708a60f51a1afafeb00987cebedf:
nvme-tcp: fix signedness bug in nvme_tcp_init_connection() (2025-03-05 10:37:01 -0800)
----------------------------------------------------------------
nvme fixes for Linux 6.14
- TCP use after free fix on polling (Sagi)
- Controller memory buffer cleanup fixes (Icenowy)
- Free leaking requests on bad user passthrough commands (Keith)
- TCP error message fix (Maurizio)
- TCP corruption fix on partial PDU (Maurizio)
- TCP memory ordering fix for weakly ordered archs (Meir)
- Type coercion fix on message error for TCP (Dan)
----------------------------------------------------------------
Dan Carpenter (1):
nvme-tcp: fix signedness bug in nvme_tcp_init_connection()
Icenowy Zheng (2):
nvme-pci: clean up CMBMSC when registering CMB fails
nvme-pci: skip CMB blocks incompatible with PCI P2P DMA
Keith Busch (1):
nvme-ioctl: fix leaked requests on mapping error
Maurizio Lombardi (3):
nvmet: remove old function prototype
nvme-tcp: Fix a C2HTermReq error message
nvme-tcp: fix potential memory corruption in nvme_tcp_recv_pdu()
Meir Elisha (1):
nvmet-tcp: Fix a possible sporadic response drops in weakly ordered arch
Sagi Grimberg (1):
nvme-tcp: fix possible UAF in nvme_tcp_poll
drivers/nvme/host/ioctl.c | 12 ++++++++----
drivers/nvme/host/pci.c | 21 +++++++++++++--------
drivers/nvme/host/tcp.c | 45 ++++++++++++++++++++++++++++++++++++---------
drivers/nvme/target/nvmet.h | 1 -
drivers/nvme/target/tcp.c | 15 +++++++++++----
5 files changed, 68 insertions(+), 26 deletions(-)
next reply other threads:[~2025-03-06 1:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 1:39 Keith Busch [this message]
2025-03-06 11:33 ` [GIT PULL] nvme fixes for Linux 6.14 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2025-03-13 15:31 Keith Busch
2025-03-13 15:42 ` Jens Axboe
2025-02-21 0:07 Keith Busch
2025-02-21 0:45 ` Jens Axboe
2025-02-03 15:03 Keith Busch
2025-02-03 16:19 ` 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=Z8j800qyBDDkQcDh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox