All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Andrea Parri <parri.andrea@gmail.com>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
	 Keith Busch <kbusch@kernel.org>,
	Sagi Grimberg <sagi@grimberg.me>,
	 Chaitanya Kulkarni <kch@nvidia.com>,
	Daniel Wagner <dwagner@suse.de>,
	linux-nvme@lists.infradead.org
Subject: Re: [PATCH blktests v2 0/4] nvme: add nvmet zone report and FC regression tests
Date: Thu, 29 Oct 2026 12:46:06 +0900	[thread overview]
Message-ID: <auLBAhlTKh0hB8W4@shinmob> (raw)
In-Reply-To: <20261022130927.3583166-1-parri.andrea@gmail.com>

On Oct 22, 2026 / 15:09, Andrea Parri wrote:
> Add regression tests for three nvmet bugs fixed by the kernel series [1]:
> 
>   nvme/072  "nvmet-fc: only send read data for successful commands"
>   nvme/073  "nvmet: zns: don't leak stale memory in zone management receive"
>   nvme/074  "nvmet: zns: reject a NUMD whose byte count wraps"
> 
> The nvme/073 fix is already applied to nvme-7.4; the other two are still
> under review.
...

Thanks. I applied this series. I confirmed nvme/072 and nvme/074 cause failures
with the kernel at the block/for-next branch. Hope that they get fixed soon.


      parent reply	other threads:[~2026-10-29  3:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-22 13:09 [PATCH blktests v2 0/4] nvme: add nvmet zone report and FC regression tests Andrea Parri
2026-10-22 13:09 ` [PATCH blktests v2 1/4] nvme/rc: add zoned null_blk target helpers Andrea Parri
2026-10-22 13:09 ` [PATCH blktests v2 2/4] nvme/072: test that nvmet sends no data for a failed read Andrea Parri
2026-10-22 13:09 ` [PATCH blktests v2 3/4] nvme/073: test nvmet zone report initialization and length Andrea Parri
2026-10-22 13:09 ` [PATCH blktests v2 4/4] nvme/074: test that nvmet rejects a zone report NUMD that wraps Andrea Parri
2026-10-22 13:36 ` [PATCH blktests v2 0/4] nvme: add nvmet zone report and FC regression tests Andrea Parri
2026-10-28 14:59 ` Christoph Hellwig
2026-10-29  3:46 ` 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=auLBAhlTKh0hB8W4@shinmob \
    --to=shinichiro.kawasaki@wdc.com \
    --cc=dwagner@suse.de \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=kch@nvidia.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=parri.andrea@gmail.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 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.