From: Christoph Hellwig <hch@lst.de>
To: Yi Zhang <yi.zhang@redhat.com>
Cc: linux-block <linux-block@vger.kernel.org>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [bug report] RIP: 0010:blkg_free+0xa/0xe0 observed on latest linux-block/for-next
Date: Mon, 6 Feb 2023 07:20:37 +0100 [thread overview]
Message-ID: <20230206062037.GA9567@lst.de> (raw)
In-Reply-To: <CAHj4cs-ZvyXKU9iAVKSkh2NfN5238rh-OaU8_uDBHVFtJb2ASQ@mail.gmail.com>
On Mon, Feb 06, 2023 at 01:22:23PM +0800, Yi Zhang wrote:
> Hello
> CKI reported one new issue with the latest linux-block/for-next, pls
> help check it, thanks.
>
> linux-block.git@for-next
> commit: 99bd489eac97
>
> [ 4407.784047] Running test [R:13334567 T:10 - Storage - block -
What actual test is this?
> storage fio numa - Kernel: 6.2.0-rc6]
> [ 4509.133240] BUG: kernel NULL pointer dereference, address: 0000000000000000
> [ 4509.133654] #PF: supervisor read access in kernel mode
> [ 4509.133930] #PF: error_code(0x0000) - not-present page
> [ 4509.134206] PGD 0 P4D 0
> [ 4509.134373] Oops: 0000 [#1] PREEMPT SMP PTI
> [ 4509.134579] CPU: 2 PID: 965 Comm: auditd Tainted: G I
> 6.2.0-rc6 #1
> [ 4509.135384] Hardware name: HP ProLiant DL360p Gen8, BIOS P71 05/24/2019
> [ 4509.135758] RIP: 0010:blkg_free+0xa/0xe0
Can you resolve this to a line using
gdb vmlinux
l *(blkg_free+0xa/0xe0)
next prev parent reply other threads:[~2023-02-06 6:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 5:22 [bug report] RIP: 0010:blkg_free+0xa/0xe0 observed on latest linux-block/for-next Yi Zhang
2023-02-06 6:20 ` Christoph Hellwig [this message]
2023-02-06 6:46 ` Yi Zhang
2023-02-06 6:53 ` Christoph Hellwig
2023-02-06 7:31 ` Yi Zhang
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=20230206062037.GA9567@lst.de \
--to=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--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