lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Tue, 19 Jul 2022 04:42:17 +0000
From:   Shinichiro Kawasaki <shinichiro.kawasaki@....com>
To:     "yangx.jy@...itsu.com" <yangx.jy@...itsu.com>
CC:     "hch@...radead.org" <hch@...radead.org>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Tejun Heo <tj@...nel.org>, Bjorn Helgaas <bhelgaas@...gle.com>,
        Jason Gunthorpe <jgg@...pe.ca>,
        Leon Romanovsky <leon@...nel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
        "linux-block@...r.kernel.org" <linux-block@...r.kernel.org>
Subject: Re: [bug report from blktests nvme/032] WARNING: possible circular
 locking dependency detected

On Jul 19, 2022 / 02:05, yangx.jy@...itsu.com wrote:
> On 2022/7/5 8:48, Shinichiro Kawasaki wrote:
> > On Jun 27, 2022 / 23:18, Christoph Hellwig wrote:
> >> On Tue, Jun 28, 2022 at 08:12:51AM +0200, Greg Kroah-Hartman wrote:
> >>> Ah, so it's a fake PCI device, or is it a real one?
> >>
> >> Whatever the blktests configuration points to.  But even if it is
> >> "fake" that fake would come from the hypervisor.
> > 
> > FYI, the WARN was observed with real PCI NVMe device also. I observed the WARN
> > with v5.19-rc1 and still observe with v5.19-rc5. I'm not sure which version
> > introduced the WARN.
> > 
> > I once reported this failure, and shared with linux-pci list.
> > 
> > https://lore.kernel.org/linux-block/20220614010907.bvbrgbz7nnvpnw5w@shindev/
> > 
> 
> Hi Shinichiro,
> 
> I wonder if the failure has been fixed? If so, could you tell me the fix 
> patch?

No, I'm not aware of fix for the failure yet. At v5.19-rc6, I still observe the
failure.

-- 
Shin'ichiro Kawasaki

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ