mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Martin Belanger <martin.nvme.dev@gmail.com>
To: Keith Busch <kbusch@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>, Christoph Hellwig <hch@lst.de>,
	Sagi Grimberg <sagi@grimberg.me>,
	Hannes Reinecke <hare@kernel.org>,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
	Martin Belanger <martin.belanger@dell.com>
Subject: Re: [PATCH v2 0/2] nvme-tcp: handle TLS control records at connect and on receive errors
Date: Wed, 28 Oct 2026 11:19:36 -0400	[thread overview]
Message-ID: <a0e96bea-b2bd-4c7b-ae94-a13c57c86f3f@gmail.com> (raw)
In-Reply-To: <auEreAhSYCdGCWvt@kbusch-mbp>



On 10/27/26 18:53, Keith Busch wrote:

> Thanks, applied to nvme-7.4.

Hi Keith,

Could you add these tags to "nvme-tcp: start error recovery when
read_sock fails", if nvme-7.4 can still change?

Fixes: be8e82caa685 ("nvme-tcp: enable TLS handshake upcall")
Cc: stable@vger.kernel.org

Since 6.7, a TLS record that is not application data (for example a
KeyUpdate) makes the queue stall until a command times out. This patch
makes the queue reconnect at once. It applies cleanly to 6.12 and 6.18.

Thanks,
Martin


  reply	other threads:[~2026-10-28 15:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 10:38 Martin Belanger via B4 Relay
2026-10-27 10:38 ` [PATCH v2 1/2] nvme-tcp: start error recovery when read_sock fails Martin Belanger via B4 Relay
2026-10-28 14:43   ` Christoph Hellwig
2026-10-27 10:38 ` [PATCH v2 2/2] nvme-tcp: skip TLS control records while waiting for the ICResp Martin Belanger via B4 Relay
2026-10-28 14:43   ` Christoph Hellwig
2026-10-27 22:53 ` [PATCH v2 0/2] nvme-tcp: handle TLS control records at connect and on receive errors Keith Busch
2026-10-28 15:19   ` Martin Belanger [this message]
2026-10-28 15:28     ` Keith Busch

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=a0e96bea-b2bd-4c7b-ae94-a13c57c86f3f@gmail.com \
    --to=martin.nvme.dev@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=hare@kernel.org \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=martin.belanger@dell.com \
    --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
all inboxes | Powered by JetHome®