linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: Chaitanya Kulkarni <chaitanyak@nvidia.com>,
	Yi Zhang <yi.zhang@redhat.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>,
	"mstowe@redhat.com" <mstowe@redhat.com>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Xiao Yang <yangx.jy@fujitsu.com>, Keith Busch <kbusch@kernel.org>
Subject: Re: blktests failures with v5.19-rc1
Date: Tue, 19 Jul 2022 17:31:27 -0500	[thread overview]
Message-ID: <20220719223127.GA1585747@bhelgaas> (raw)
In-Reply-To: <20220719045036.h273puvs3cibafix@shindev>

On Tue, Jul 19, 2022 at 04:50:36AM +0000, Shinichiro Kawasaki wrote:
> On Jun 15, 2022 / 17:16, Keith Busch wrote:
> > On Wed, Jun 15, 2022 at 02:47:27PM -0500, Bjorn Helgaas wrote:
> > > On Tue, Jun 14, 2022 at 04:00:45AM +0000, Shinichiro Kawasaki wrote:
> > > > 
> > > > Yeah, this WARN is confusing for us then it would be valuable to
> > > > test by blktests not to repeat it. One point I wonder is: which test
> > > > group the test case will it fall in? The nvme group could be the
> > > > group to add, probably.
> > > > 
> > > > Another point I wonder is other kernel test suite than blktests.
> > > > Don't we have more appropriate test suite to check PCI device
> > > > rescan/remove race ? Such a test sounds more like a PCI bus
> > > > sub-system test than block/storage test.
> > > 
> > > I'm not aware of such a test, but it would be nice to have one.
> > > 
> > > Can you share your qemu config so I can reproduce this locally?
> > > 
> > > Thanks for finding and reporting this!
> > 
> > This ought to be reproducible with any pci device that can be
> > removed. Since we initially observed with nvme, you can try with
> > such a device. A quick way to get one appearing in qemu is to add
> > parameters:
> > 
> >         -drive id=n,if=none,file=null-co://,format=raw \
> > 	-device nvme,serial=foobar,drive=n
> 
> Did you have chance to reproduce the WARN? Recently, it was reported
> again [1] and getting attention.

I have not paid any attention to this yet.  From what I can tell, the
problem was discovered by a test case (i.e., not reported by a
real-world user), it is not a recent regression, we haven't identified
a commit that introduced the problem, and we do not have a potential
fix for it.  Obviously it needs to be fixed and I'm not trying to
minimize the problem; I just want to calibrate it against everything
else.

> [1] https://lore.kernel.org/linux-block/4ed3028b-2d2f-8755-fec2-0b9cb5ad42d2@fujitsu.com/
> 
> -- 
> Shin'ichiro Kawasaki

  reply	other threads:[~2022-07-19 22:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220609235329.4jbz4wr3eg2nmzqa@shindev>
     [not found] ` <717734c9-c633-fb48-499e-7e3e15113020@nvidia.com>
     [not found]   ` <19d09611-42cc-5a81-d676-c5375865c14c@nvidia.com>
     [not found]     ` <20220610122517.6pt5y63hcosk5mes@shindev>
     [not found]       ` <YqNZiMw+rH5gyZDI@kbusch-mbp.dhcp.thefacebook.com>
     [not found]         ` <CAHj4cs9G0WDrnSS6iVZJfgfOcRR0ysJhw+9yqcbqE=_8mkF0zw@mail.gmail.com>
2022-06-14  1:09           ` blktests failures with v5.19-rc1 Shinichiro Kawasaki
2022-06-14  2:23             ` Keith Busch
2022-06-14  2:38               ` Chaitanya Kulkarni
2022-06-14  4:00                 ` Shinichiro Kawasaki
2022-06-15 19:47                   ` Bjorn Helgaas
2022-06-15 22:01                     ` Chaitanya Kulkarni
2022-06-15 23:13                       ` Yi Zhang
2022-06-16  4:42                         ` Shinichiro Kawasaki
2022-06-16 17:55                           ` Chaitanya Kulkarni
2022-06-15 23:16                     ` Keith Busch
2022-07-19  4:50                       ` Shinichiro Kawasaki
2022-07-19 22:31                         ` Bjorn Helgaas [this message]
2022-07-20  2:27                           ` Shinichiro Kawasaki
2022-12-19 11:27                             ` Shinichiro Kawasaki
2022-12-29 18:13                               ` Bjorn Helgaas

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=20220719223127.GA1585747@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=chaitanyak@nvidia.com \
    --cc=kbusch@kernel.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mstowe@redhat.com \
    --cc=shinichiro.kawasaki@wdc.com \
    --cc=yangx.jy@fujitsu.com \
    --cc=yi.zhang@redhat.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;
as well as URLs for NNTP newsgroup(s).