linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Hannes Reinecke <hare@suse.de>
Cc: "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>
Subject: Re: blktests failures with v6.6
Date: Wed, 1 Nov 2023 12:37:51 +0000	[thread overview]
Message-ID: <xllt2ceb67yumezan7623rqqabq3xklq7l5wcui2zzz2eeopkj@7lj3p726mac3> (raw)
In-Reply-To: <d1d179ea-ae0f-497a-a2af-f1c60cf90362@suse.de>

On Nov 01, 2023 / 11:33, Hannes Reinecke wrote:
> On 11/1/23 05:09, Shinichiro Kawasaki wrote:
[...]
> > #2: nvme/003 (fabrics transport)
> > 
> >     When nvme test group is run with trtype=rdma or tcp, the test case fails
> >     due to lockdep WARNING "possible circular locking dependency detected".
> >     Reported in May/2023. Fix discussions were held [4][5].
> > 
> >     [4] https://lore.kernel.org/linux-nvme/20230511150321.103172-1-bvanassche@acm.org/
> >     [5] https://lore.kernel.org/linux-nvme/5cb63b10-72ab-4b7c-7574-48583ea8ffd1@grimberg.me/
> > 
> Just send a patchset which should resolve these issues.
> Can you test with them?

Hannes, thank you very much! This failure magically disappeared with your patch
set. I confirmed it both trtype=rdma and tcp :)

      reply	other threads:[~2023-11-01 12:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-01  4:09 blktests failures with v6.6 Shinichiro Kawasaki
2023-11-01 10:33 ` Hannes Reinecke
2023-11-01 12:37   ` Shinichiro 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=xllt2ceb67yumezan7623rqqabq3xklq7l5wcui2zzz2eeopkj@7lj3p726mac3 \
    --to=shinichiro.kawasaki@wdc.com \
    --cc=hare@suse.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-scsi@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).