Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Leech <cleech@redhat.com>
To: linux-nvme@lists.infradead.org
Cc: Surabhi Gogte <sgogte@purestorage.com>,
	 Hannes Reinecke <hare@kernel.org>,
	Keith Busch <kbusch@kernel.org>
Subject: nvme-tls failing with (61b0ed3be81b6) nvme-tcp: parallelize I/O queue allocation and startup
Date: Thu, 12 Nov 2026 10:46:16 -0800	[thread overview]
Message-ID: <20261112-9505880f2c33f0134ef20c39@redhat.com> (raw)

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.

- Chris



             reply	other threads:[~2026-11-12 18:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12 18:46 Chris Leech [this message]
2026-11-12 22:35 ` nvme-tls failing with (61b0ed3be81b6) nvme-tcp: parallelize I/O queue allocation and startup Surabhi Gogte (she/her)
2026-11-13  1:44   ` Chris Leech

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-9505880f2c33f0134ef20c39@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