From: Jens Axboe <axboe@kernel.dk>
To: Keith Busch <kbusch@kernel.org>
Cc: hch@lst.de, sagi@grimberg.me, linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] nvme fixes for Linux 6.14
Date: Thu, 6 Mar 2025 04:33:14 -0700 [thread overview]
Message-ID: <e3f64ff3-99d8-4a2c-8f65-47f0eef7697d@kernel.dk> (raw)
In-Reply-To: <Z8j800qyBDDkQcDh@kbusch-mbp>
On 3/5/25 6:39 PM, Keith Busch wrote:
> 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)
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2025-03-06 12:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 1:39 [GIT PULL] nvme fixes for Linux 6.14 Keith Busch
2025-03-06 11:33 ` Jens Axboe [this message]
-- 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=e3f64ff3-99d8-4a2c-8f65-47f0eef7697d@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@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 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.