Linux block layer
 help / color / mirror / Atom feed
From: Nilay Shroff <nilay@linux.ibm.com>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	"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" <nbd@other.debian.org>,
	"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>
Subject: Re: blktests failures with v6.12 kernel
Date: Fri, 29 Nov 2024 13:25:39 +0530	[thread overview]
Message-ID: <6dee5d52-3fe2-4c3b-9eb3-47de7d7c5c62@linux.ibm.com> (raw)
In-Reply-To: <6crydkodszx5vq4ieox3jjpwkxtu7mhbohypy24awlo5w7f4k6@to3dcng24rd4>

Hi Shinichiro,

On 11/26/24 07:49, Shinichiro Kawasaki wrote:
> Hi all,
> 
> I ran the latest blktests (git hash: 83781f257857) with the v6.12 kernel. Also,
> I checked CKI project runs for the kernel. I observed five failures below.
> 
> Comparing with the previous report using the v6.12-rc1 kernel [1], two failures
> were resolved: nvme/014 and srp group. On the other hand, four new failures were
> observed.
> 
> [1] https://lore.kernel.org/linux-block/xpe6bea7rakpyoyfvspvin2dsozjmjtjktpph7rep3h25tv7fb@ooz4cu5z6bq6/
> 
> 
> List of failures
> ================
> #1: nvme/031 (fc transport)
> #2: nvme/037 (fc transport)
> #3: nvme/041 (fc transport)
> #4: nvme/052 (loop transport)
> #5: throtl/001 (CKI project, s390 arch)
> 
> Failure description
> ===================
> 
<snip>
> #4: nvme/052 (loop transport)
> 
>   The test case fails due to the "BUG: sleeping function called from invalid
>   context" [5]. A fix candidate was posted which sets NVME_F_BLOCKING to loop
>   transport, but it is not the best solution [6]. It is desired to have a better
>   fix and the test case to confirm it.
> 
>   [5] https://lore.kernel.org/linux-nvme/tqcy3sveity7p56v7ywp7ssyviwcb3w4623cnxj3knoobfcanq@yxgt2mjkbkam/
>   [6] https://lore.kernel.org/linux-nvme/20241017172052.2603389-1-kbusch@meta.com/
> 
I have developed a blktest to recreate this bug and also probable fix as suggested by Christoph[1].
I will send the blktest and patch later today.

[1] https://lore.kernel.org/linux-nvme/20241022070252.GA11389@lst.de/

Thanks,
--Nilay

  reply	other threads:[~2024-11-29  7:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26  2:19 blktests failures with v6.12 kernel Shinichiro Kawasaki
2024-11-29  7:55 ` Nilay Shroff [this message]
2024-11-29  8:37 ` Yu Kuai

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=6dee5d52-3fe2-4c3b-9eb3-47de7d7c5c62@linux.ibm.com \
    --to=nilay@linux.ibm.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 \
    --cc=shinichiro.kawasaki@wdc.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