All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	 "linux-nvme@lists.infradead.org"
	<linux-nvme@lists.infradead.org>,
	"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	 nbd@other.debian.org, linux-rdma@vger.kernel.org
Subject: Re: blktests failures with v7.2 kernel
Date: Tue, 18 Aug 2026 21:11:17 +0900	[thread overview]
Message-ID: <aoRLc_etxQcbfd6f@shinhome> (raw)
In-Reply-To: <aoRGbVB70YCcxoxF@shinhome>

On Aug 18, 2026 / 20:50, Shin'ichiro Kawasaki wrote:
[...]
> #3: nvme/068 (new)
> 
>     When it is repeated several times, the test case nvme/068 fails with the
>     message below:
> 
>     nvme/068 (tr=rdma) (NVMe multipath delayed removal test)     [failed]
>         runtime  10.979s  ...  10.975s
>         --- tests/nvme/068.out      2026-05-21 11:44:28.070959369 +0900
>         +++ /home/shin/Blktests/blktests/results/nodev_tr_rdma/nvme/068.out.bad     2026-08-18 17:51:30.262228567 +0900
>         @@ -1,3 +1,4 @@
>          Running nvme/068
>          pwrite: Input/output error
>         +module refcount not as original
>          Test complete
> 
>     The failure is spoladic. I'm not sure if recent kernel changes triggered
>     the failure or not.
> 
>     The failure looks dependent on test nodes. It was observed with loop
>     transport and rdma transport, but was not observed with tcp transport.
>     This needs further debug.

Let me amend this part. I totally forgot that I myself chased down this failure
and posted the fix patch for blktests [*]. No need to debug further.

[*] https://lore.kernel.org/linux-nvme/20260806033146.2067433-1-shinichiro.kawasaki@wdc.com/

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-18 11:50 blktests failures with v7.2 kernel Shin'ichiro Kawasaki
2026-08-18 12:11 ` 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=aoRLc_etxQcbfd6f@shinhome \
    --to=shinichiro.kawasaki@wdc.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nbd@other.debian.org \
    /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.