From: Matthew Wilcox <willy@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Zorro Lang <zlang@redhat.com>,
linux-mm@kvack.org, 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 01:43:48 +0100 [thread overview]
Message-ID: <YpVkxGe0reEaDoU+@casper.infradead.org> (raw)
In-Reply-To: <20220530222919.GA1098723@dread.disaster.area>
On Tue, May 31, 2022 at 08:29:19AM +1000, Dave Chinner wrote:
> On Tue, May 31, 2022 at 02:39:08AM +0800, Zorro Lang wrote:
> > 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
>
> Rather than make anyone looking at this download multiple files and
> run diff, perhaps you could just post the output of 'diff -u
> config.good config.bad'?
You guys know about tools/testing/ktest/config-bisect.pl right?
prev parent reply other threads:[~2022-05-31 0:43 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
2022-05-30 22:29 ` Dave Chinner
2022-05-31 0:43 ` Matthew Wilcox [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=YpVkxGe0reEaDoU+@casper.infradead.org \
--to=willy@infradead.org \
--cc=david@fromorbit.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--cc=zlang@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;
as well as URLs for NNTP newsgroup(s).