Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: linux-nvme@lists.infradead.org
Cc: Logan Gunthorpe <logang@deltatee.com>, Chao Shi <coshi036@gmail.com>
Subject: Re: [PATCH blktests] nvme/{033,036,037}: skip when the test target namespace has metadata
Date: Sun, 12 Jul 2026 08:14:08 +0900	[thread overview]
Message-ID: <alLOKw5RMsFd2tsK@shinmob> (raw)
In-Reply-To: <20260630113714.848831-1-shinichiro.kawasaki@wdc.com>

On Jun 30, 2026 / 20:37, Shin'ichiro Kawasaki wrote:
> The kernel commit c8cdecdb47d3 ("nvme: core: reject invalid LBA data
> size from Identify Namespace") in the v7.2-rc1 tag triggered failures of
> blktests test cases nvme/033, 036 and 037. The failures are observed
> when TEST_DEV specifies a NVMe device with metadata. The commit
> introduced a new check in nvme_update_ns_info_block() to reject invalid
> LBA data size. After this commit, namespaces with zero LBA data size are
> rejected.
> 
> According to the comment in nvmet_passthru_override_id_ns() in the
> kernel code drivers/nvme/target/passthru.c, "Presently the NVMEoF target
> code does not support sending metadata, so we must disable it here". For
> that purpose, the function sets the LBA data size to zero for all LBA
> format (lbaf) entries with metadata. After the trigger commit, these
> entries become invalid for NVMEoF target passthru, then namespaces with
> metadata are not visible as block devices through the target setup.
> 
> These test cases set up NVMEoF target passthru assuming the namespace
> devices are visible, so they cannot find the namespaces and fail.
> 
> To avoid the failures, skip the test cases when TEST_DEV has metadata.

FYI, I applied this patch.


      reply	other threads:[~2026-07-11 23:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 11:37 [PATCH blktests] nvme/{033,036,037}: skip when the test target namespace has metadata Shin'ichiro Kawasaki
2026-07-11 23:14 ` Shin'ichiro Kawasaki [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=alLOKw5RMsFd2tsK@shinmob \
    --to=shinichiro.kawasaki@wdc.com \
    --cc=coshi036@gmail.com \
    --cc=linux-nvme@lists.infradead.org \
    --cc=logang@deltatee.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