From: James Smart <jsmart2021@gmail.com>
To: Daniel Wagner <dwagner@suse.de>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Hannes Reinecke <hare@suse.de>
Subject: Re: nvme-6.3: blktests nvme/003 null pointer for fc transport
Date: Tue, 31 Jan 2023 15:27:20 -0800 [thread overview]
Message-ID: <40b14fe4-7d7f-b4ee-b058-d0d39b9fa6d4@gmail.com> (raw)
In-Reply-To: <20230130111532.ez63iip4qxrh42ga@carbon.lan>
On 1/30/2023 3:15 AM, Daniel Wagner wrote:
> Hi,
>
> Hannes added support to blktest to enable the FC transport for it. And as result
> blktests is able to crash the kernel. Haven't startet to look into it yet.
>
> run blktests nvme/003 at 2023-01-30 12:08:28
> nvmet: adding nsid 1 to subsystem blktests-subsystem-1
> BUG: kernel NULL pointer dereference, address: 0000000000000010
> #PF: supervisor read access in kernel mode
> #PF: error_code(0x0000) - not-present page
> PGD 0 P4D 0
> Oops: 0000 [#1] PREEMPT SMP NOPTI
> CPU: 3 PID: 14200 Comm: nvme Not tainted 6.2.0-rc4+ #1 c9afca57e89c2aa3234427c2cd6cd4dd2984ae8c
> Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 0.0.0 02/06/2015
> RIP: 0010:nvme_alloc_admin_tag_set+0x38/0x120 [nvme_core]
bingo...
The cleanup patch "nvme-fc: use the tagset alloc/free helpers"
introduced it.
See the fix patch "nvme-fc: Fix initialization order" about 10 days ago
that corrects it.
-- james
next prev parent reply other threads:[~2023-01-31 23:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 11:15 nvme-6.3: blktests nvme/003 null pointer for fc transport Daniel Wagner
2023-01-31 23:27 ` James Smart [this message]
2023-02-01 8:10 ` Daniel Wagner
2023-02-01 8:24 ` Hannes Reinecke
2023-02-20 16:04 ` Daniel Wagner
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=40b14fe4-7d7f-b4ee-b058-d0d39b9fa6d4@gmail.com \
--to=jsmart2021@gmail.com \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=linux-nvme@lists.infradead.org \
--cc=shinichiro.kawasaki@wdc.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