From: Keith Busch <kbusch@kernel.org>
To: Chaitanya Kulkarni <chaitanyak@nvidia.com>
Cc: Gerd Bayer <gbayer@linux.ibm.com>, Jens Axboe <axboe@fb.com>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Niklas Schnelle <schnelle@linux.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: nvme-pci: NULL pointer dereference in nvme_dev_disable() on linux-next
Date: Tue, 8 Nov 2022 08:46:03 -0700 [thread overview]
Message-ID: <Y2p5u8N+Hou/5v53@kbusch-mbp> (raw)
In-Reply-To: <7a14c467-e67e-eede-4ebc-d8105cc3bcd5@nvidia.com>
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.
next prev parent reply other threads:[~2022-11-08 15:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 17:28 nvme-pci: NULL pointer dereference in nvme_dev_disable() on linux-next Gerd Bayer
2022-11-08 3:50 ` Chaitanya Kulkarni
2022-11-08 15:46 ` Keith Busch [this message]
2022-11-08 7:48 ` Christoph Hellwig
2022-11-08 17:11 ` Gerd Bayer
2022-11-08 17:23 ` Keith Busch
2022-11-09 6:20 ` Christoph Hellwig
2022-11-09 2:54 ` Sagi Grimberg
2022-11-09 7:41 ` Chao Leng
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=Y2p5u8N+Hou/5v53@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@fb.com \
--cc=chaitanyak@nvidia.com \
--cc=gbayer@linux.ibm.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=schnelle@linux.ibm.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