From: Maxime Bizon <mbizon@freebox.fr>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Fail to boot 5.15 on mpc8347 with either debug_pagealloc or nobats
Date: Mon, 06 Dec 2021 11:32:06 +0100 [thread overview]
Message-ID: <b9a4afdc13d29100d562232b6376834782c02e92.camel@freebox.fr> (raw)
In-Reply-To: <854e7a5f-2b1b-47de-51fb-6cd0f3c6ccd3@csgroup.eu>
On Mon, 2021-12-06 at 09:07 +0000, Christophe Leroy wrote:
Hello,
> Looks like you can win something if you take the patch I just sent
> and replace the memblock_phys_alloc(k_size, k_size) by
> memblock_phys_alloc_range(k_size, k_size, 0, MEMBLOCK_ALLOC_ANYWHERE)
I tried your patch without your proposed modification and got something new:
[ 0.000000] ==================================================================
[ 0.000000] BUG: KASAN: unknown-crash in vprintk+0x30/0xe8
[ 0.000000] Read of size 4 at addr 80ad0740 by task swapper/0
[ 0.000000]
[ 0.000000] CPU: 0 PID: 0 Comm: swapper Not tainted 5.15.0+ #415
[ 0.000000] Call Trace:
[ 0.000000] [80cdfe50] [8017711c] print_address_description.constprop.0+0x78/0x338 (unreliable)
[ 0.000000] [80cdfe80] [80176e48] kasan_report+0x1c0/0x1d4
[ 0.000000] [80cdfec0] [80099a34] vprintk+0x30/0xe8
[ 0.000000] [80cdfee0] [80099600] _printk+0x9c/0xbc
[ 0.000000] [80cdff60] [80999628] kasan_init+0x14c/0x164
[ 0.000000] [80cdff90] [80995440] setup_arch+0x18/0x1c4
[ 0.000000] [80cdffc0] [809910c8] start_kernel+0x60/0x2fc
[ 0.000000] [80cdfff0] [000033c0] 0x33c0
[ 0.000000]
[ 0.000000] The buggy address belongs to the variable:
[ 0.000000] init_task+0x0/0xce0
[ 0.000000]
[ 0.000000] Memory state around the buggy address:
[ 0.000000] 80ad0600: de ad be ef de ad be ef de ad be ef de ad be ef
[ 0.000000] 80ad0680: de ad be ef de ad be ef de ad be ef de ad be ef
[ 0.000000] >80ad0700: de ad be ef de ad be ef de ad be ef de ad be ef
[ 0.000000] ^
[ 0.000000] 80ad0780: de ad be ef de ad be ef de ad be ef de ad be ef
[ 0.000000] 80ad0800: de ad be ef de ad be ef de ad be ef de ad be ef
[ 0.000000] ==================================================================
[ 0.000000] Disabling lock debugging due to kernel taint
[ 0.000000] KASAN init done
Looking at the archive when you introduced KASAN, you had this kind of
bug, and the conclusion of the thread was:
> Indeed the problem is in kasan_init() : memblock_phys_alloc()
> doesn't zeroize the allocated memory. I changed it to
> memblock_alloc() and now it works.
since your patch uses memblock_phys_alloc() again, maybe that's the
same issue
--
Maxime
next prev parent reply other threads:[~2021-12-06 10:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f23763d551e65d4a225ba13c7898f83853c2aeaf.camel@freebox.fr>
2021-12-03 12:49 ` Fail to boot 5.15 on mpc8347 with either debug_pagealloc or nobats Christophe Leroy
2021-12-03 18:43 ` Maxime Bizon
2021-12-04 10:01 ` Christophe Leroy
2021-12-04 14:10 ` Maxime Bizon
2021-12-04 17:42 ` Christophe Leroy
2021-12-05 16:42 ` Maxime Bizon
2021-12-05 18:11 ` Christophe Leroy
2021-12-05 21:44 ` Maxime Bizon
2021-12-06 7:03 ` Christophe Leroy
2021-12-06 8:47 ` Maxime Bizon
2021-12-06 9:07 ` Christophe Leroy
2021-12-06 10:32 ` Maxime Bizon [this message]
2021-12-06 14:22 ` Christophe Leroy
2021-12-06 15:48 ` Maxime Bizon
2021-12-07 5:50 ` Christophe Leroy
2021-12-07 6:11 ` Christophe Leroy
2021-12-12 11:21 ` Maxime Bizon
2021-12-07 5:54 ` Christophe Leroy
2021-12-07 9:04 ` Maxime Bizon
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=b9a4afdc13d29100d562232b6376834782c02e92.camel@freebox.fr \
--to=mbizon@freebox.fr \
--cc=christophe.leroy@csgroup.eu \
--cc=linuxppc-dev@lists.ozlabs.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 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.