[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y2p5u8N+Hou/5v53@kbusch-mbp>
Date: Tue, 8 Nov 2022 08:46:03 -0700
From: Keith Busch <kbusch@...nel.org>
To: Chaitanya Kulkarni <chaitanyak@...dia.com>
Cc: Gerd Bayer <gbayer@...ux.ibm.com>, Jens Axboe <axboe@...com>,
Christoph Hellwig <hch@....de>,
Sagi Grimberg <sagi@...mberg.me>,
Niklas Schnelle <schnelle@...ux.ibm.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-nvme@...ts.infradead.org" <linux-nvme@...ts.infradead.org>
Subject: Re: nvme-pci: NULL pointer dereference in nvme_dev_disable() on
linux-next
On Tue, Nov 08, 2022 at 03:50:33AM +0000, Chaitanya Kulkarni wrote:
> On 11/7/22 09:28, Gerd Bayer wrote:
>
> > We believe this to be a race-condition somewhere, since this sequence does not produce the panic
> > when executed interactively.
> >
>
> You can try and bisect the code to point out at exact commit.
Bisect doesn't work without a known good commit point.
Powered by blists - more mailing lists