From: Ming Lei <ming.lei@redhat.com>
To: Changhui Zhong <czhong@redhat.com>
Cc: linux-block@vger.kernel.org
Subject: Re: [bug report] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000058
Date: Tue, 27 Dec 2022 16:00:37 +0800 [thread overview]
Message-ID: <Y6qmJT7H14Dfhn5y@T590> (raw)
In-Reply-To: <CAGVVp+WS5aHiF2Odc-C+fO56qKyV7vPsPRz35v9eWsPJDNj=ng@mail.gmail.com>
Hi Changhui,
On Mon, Dec 26, 2022 at 11:11:44AM +0800, Changhui Zhong wrote:
> Hello,
> Below issue was triggered with ( v6.0.15-996-g988abd970566), pls help check it
There isn't commit 988abd970566 in linux-6.0.y, so I guess the above
build must integrate other patches not in 6.0.y
From the source code in cki build[1], looks commit 80bd4a7aab4c ("blk-mq: move
the srcu_struct used for quiescing to the tagset") is included, but
commit 8537380bb988 ("blk-mq: skip non-mq queues in blk_mq_quiesce_queue")
is missed, that is why this panic is triggered.
BTW, if possible, I'd suggest to share kernel tree being tested in cki test
if non official kernel is tested.
[1] https://s3.amazonaws.com/arr-cki-prod-trusted-artifacts/trusted-artifacts/731863135/build%20aarch64/3522994262/artifacts/kernel-stable-queue-redhat_731863135_aarch64.tar.gz
thanks,
Ming
next prev parent reply other threads:[~2022-12-27 8:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 3:11 [bug report] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000058 Changhui Zhong
2022-12-27 3:32 ` Ming Lei
2022-12-27 8:00 ` Ming Lei [this message]
2022-12-27 8:16 ` Ming Lei
2022-12-27 8:30 ` Changhui Zhong
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=Y6qmJT7H14Dfhn5y@T590 \
--to=ming.lei@redhat.com \
--cc=czhong@redhat.com \
--cc=linux-block@vger.kernel.org \
/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