From: Yujie Liu <yujie.liu@intel.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: kernel test robot <oliver.sang@intel.com>,
<oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Mike Rapoport <rppt@linux.ibm.com>,
Christoph Lameter <cl@linux.com>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>
Subject: Re: [linus:master] [mm, slub] fa9b88e459: kernel_BUG_at_include/linux/page-flags.h
Date: Wed, 11 Jan 2023 09:48:45 +0800 [thread overview]
Message-ID: <Y74VfdHtEAmmbAHP@yujie-X299> (raw)
In-Reply-To: <654982ed-0ccd-8285-65b2-dc05f8b5bd27@suse.cz>
On Mon, Jan 09, 2023 at 11:57:12PM +0100, Vlastimil Babka wrote:
> On 1/8/23 17:28, kernel test robot wrote:
> > Greeting,
> >
> > FYI, we noticed kernel_BUG_at_include/linux/page-flags.h due to commit (built with gcc-11):
> >
> > commit: fa9b88e459d710cadf3b01e8a64eda00cc91cdd6 ("mm, slub: refactor free debug processing")
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
>
> Thanks for trying to bisect the root cause to earlier commit than
> 0af8489b0216f, as we discussed. Here I strongly suspect it's also earlier
> than this commit. Because the code changed here is only used with
> SLUB_DEBUG, which is not enabled in your config. Only later in 0af8489b0216f
> it becomes used also by SLUB_TINY.
Sorry for this false report. We don't have much confidence in bisecting
this issue since the reproducing rate is very low, so it's difficult to
mark good or bad during bisection.
Thanks for the latest update at:
https://lore.kernel.org/all/d024b846-9282-4ecd-eafd-2e5571932a72@suse.cz/
The test results so far have been summarized by Oliver in the previous
report. Will keep you updated if we find other clues. Thanks.
--
Best Regards,
Yujie
> > [test failed on linux-next/master 469a89fd3bb73bb2eea628da2b3e0f695f80b7ce]
> >
> > in testcase: boot
> >
> > on test machine: qemu-system-i386 -enable-kvm -cpu SandyBridge -smp 2 -m 4G
> >
> > caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
> >
>
prev parent reply other threads:[~2023-01-11 1:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 16:28 kernel test robot
2023-01-09 22:57 ` Vlastimil Babka
2023-01-11 1:48 ` Yujie Liu [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=Y74VfdHtEAmmbAHP@yujie-X299 \
--to=yujie.liu@intel.com \
--cc=42.hyeyoo@gmail.com \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=rppt@linux.ibm.com \
--cc=vbabka@suse.cz \
/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