From: Jens Axboe <axboe@kernel.dk>
To: Guangwu Zhang <guazhang@redhat.com>,
linux-block@vger.kernel.org, Ming Lei <ming.lei@redhat.com>,
Jeff Moyer <jmoyer@redhat.com>,
io-uring@vger.kernel.org
Subject: Re: [bug report] BUG: unable to handle page fault for address: 00000002de3ac841
Date: Wed, 7 Feb 2024 10:06:55 -0700 [thread overview]
Message-ID: <de25b878-15d5-4299-996d-74c122e21e6d@kernel.dk> (raw)
In-Reply-To: <b1668ac2-3fa3-45e6-ae79-a127cb095eba@kernel.dk>
On 2/7/24 9:37 AM, Jens Axboe wrote:
> On 2/7/24 12:19 AM, Guangwu Zhang wrote:
>> HI,
>> Found the kernel issue with linux-block/for-next branch.
>> kernel repo https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git
>>
>> Reproducer :
>> 1. offline_online_cpu_in_bg
>> 2. some_io_in_bg
>
> I don't know what these two things are. Would be nice with an actual
> reproducer. I can trivially write something that offline and onlines CPU
> in the background, and I did, but I cannot reproduce this issue. Ditto
> on "some_io_in_bg", what does that mean??
I managed to reproduce this, it takes:
- Using polled IO, but you didn't set hipri in the given command line you
sent. What you sent cannot have been what was run, the trace as well
shows that polled IO is being done.
- NVMe device with _no_ poll queues defined.
Anyway, the current branch should work fine. In the future, please do
include the full setup description and exactly what was run. This one was
easy to find, but may not be so lucky in the future.
--
Jens Axboe
prev parent reply other threads:[~2024-02-07 17:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 7:19 [bug report] BUG: unable to handle page fault for address: 00000002de3ac841 Guangwu Zhang
2024-02-07 16:37 ` Jens Axboe
2024-02-07 17:06 ` Jens Axboe [this message]
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=de25b878-15d5-4299-996d-74c122e21e6d@kernel.dk \
--to=axboe@kernel.dk \
--cc=guazhang@redhat.com \
--cc=io-uring@vger.kernel.org \
--cc=jmoyer@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.