From: Zorro Lang <zlang@redhat.com>
To: linux-mm@kvack.org
Cc: linux-xfs@vger.kernel.org, linux-ext4@vger.kernel.org,
nvdimm@lists.linux.dev
Subject: Re: Potential regression on kernel 5.19-rc0: kernel BUG at mm/page_table_check.c:51!
Date: Tue, 31 May 2022 02:39:08 +0800 [thread overview]
Message-ID: <20220530183908.vi7u37a6irji4gnf@zlang-mailbox> (raw)
In-Reply-To: <20220530080616.6h77ppymilyvjqus@zlang-mailbox>
On Mon, May 30, 2022 at 04:06:16PM +0800, Zorro Lang wrote:
> Hi mm folks:
>
> I reported a regression bug on latest upstream linux:
> https://bugzilla.kernel.org/show_bug.cgi?id=216047
>
> It's about xfs/ext4 + DAX, panic at mm/page_table_check.c:51!
>
> static struct page_table_check *get_page_table_check(struct page_ext *page_ext)
> {
> ==> BUG_ON(!page_ext);
> return (void *)(page_ext) + page_table_check_ops.offset;
> }
>
> It's 100% reproducible for me, by running fstests generic/623:
> https://git.kernel.org/pub/scm/fs/xfs/xfstests-dev.git/tree/tests/generic/623
> on xfs or ext4 with DAX enabled.
>
> It doesn't look like a xfs or ext4 issue, so send to linux-mm to get more
> reviewing. More details please refer to above bug link. I changed its Pruduct
> to mm, but the Assignee isn't changed by default.
It's not a regression *recently* at least, I still can reproduce this bug on
linux v5.16.
But I found it's related with someone kernel configuration (sorry I haven't
figured out which one config is). I've upload two kernel config files, one[1]
can build a kernel which reproduce this bug, the other[2] can't. Hope that
helps.
Thanks,
Zorro
[1]
https://bugzilla.kernel.org/attachment.cgi?id=301076
[2]
https://bugzilla.kernel.org/attachment.cgi?id=301077
>
> Thanks,
> Zorro
next prev parent reply other threads:[~2022-05-30 18:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-30 8:06 Potential regression on kernel 5.19-rc0: kernel BUG at mm/page_table_check.c:51! Zorro Lang
2022-05-30 18:39 ` Zorro Lang [this message]
2022-05-30 22:29 ` Dave Chinner
2022-05-31 0:43 ` Matthew Wilcox
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=20220530183908.vi7u37a6irji4gnf@zlang-mailbox \
--to=zlang@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).