From: Chris Leech <cleech@redhat.com>
To: "Surabhi Gogte (she/her)" <sgogte@purestorage.com>
Cc: linux-nvme@lists.infradead.org, Hannes Reinecke <hare@kernel.org>,
Keith Busch <kbusch@kernel.org>
Subject: Re: nvme-tls failing with (61b0ed3be81b6) nvme-tcp: parallelize I/O queue allocation and startup
Date: Thu, 12 Nov 2026 17:44:37 -0800 [thread overview]
Message-ID: <20261112-c241d8bc9d510b065f2bb277@redhat.com> (raw)
In-Reply-To: <CAMof9cWw6jDht3++cYcybQohq=Nf6DzY4ZL1m_E0b95r9CRxMQ@mail.gmail.com>
On Thu, Nov 12, 2026 at 02:35:23PM -0800, Surabhi Gogte (she/her) wrote:
> On Thu, Nov 12, 2026 at 10:46 AM Chris Leech <cleech@redhat.com> wrote:
> >
> > Hello,
> >
> > I was testing some patchs and ran into trouble with nvme-tls that I
> > bisected back to this change (61b0ed3be81b6 nvme-tcp: parallelize I/O
> > queue allocation and startup).
> >
> > I haven't determined what exactly is happening yet, but blktests
> > nvme/062 and nvme/063 both fail with this applied and pass again if I
> > revert it.
>
> Hi Chris,
> Can you check if the failures you saw are due to an older version of
> ktls-utils/tlshd being used?
> Ref: https://lore.kernel.org/linux-nvme/CAMof9cU5s0ck20fcSAYSvK-xpcP5_Hv2BmN20Bh3btpLum7THg@mail.gmail.com/.
Thanks for this. I should have found that, but was coming to the idea
that it might be related to having an older tlshd anyway.
> If the tests fail with ktls-utils 1.5.0 as well, please share further
> details about the blktest failure logs and kernel logs so I can also
> take a look.
The initial environment I was bisecting in still seemed to be having
issues, but a clean Fedora 44 + ktls-utils 1.5.0 does look to be working
as expected. I'll spend some time trying to sort out if I've made a
mess of this system in some other way.
- Chris
prev parent reply other threads:[~2026-11-13 1:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 18:46 nvme-tls failing with (61b0ed3be81b6) nvme-tcp: parallelize I/O queue allocation and startup Chris Leech
2026-11-12 22:35 ` Surabhi Gogte (she/her)
2026-11-13 1:44 ` Chris Leech [this message]
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=20261112-c241d8bc9d510b065f2bb277@redhat.com \
--to=cleech@redhat.com \
--cc=hare@kernel.org \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sgogte@purestorage.com \
/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