From: bugzilla-daemon@kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 215389] pagealloc: memory corruption at building glibc-2.33 and running its' testsuite
Date: Mon, 16 May 2022 18:51:04 +0000 [thread overview]
Message-ID: <bug-215389-206035-mXo54QCqwv@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215389-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215389
--- Comment #22 from Erhard F. (erhard_f@mailbox.org) ---
Created attachment 300977
--> https://bugzilla.kernel.org/attachment.cgi?id=300977&action=edit
dmesg (5.18-rc6, CONFIG_LOWMEM_SIZE=0x28000000, outline KASAN, PowerMac G4 DP)
I increased THREAD_SHIFT to 14 and used outline KASAN still with
CONFIG_LOWMEM_SIZE=0x28000000. The memory corruption output looks slightly
different (but not much):
[...]
pagealloc: memory corruption
f5fcfff0: 00 00 00 00 ....
CPU: 1 PID: 29742 Comm: ld.so.1 Not tainted 5.18.0-rc6-PMacG4 #7
Call Trace:
[eea3ba90] [c09890d4] dump_stack_lvl+0x80/0xc0 (unreliable)
[eea3bab0] [c03cce40] __kernel_unpoison_pages+0x208/0x250
[eea3bb00] [c03a2e48] post_alloc_hook+0x108/0x144
[eea3bb30] [c03a66e0] get_page_from_freelist+0x9d4/0x12dc
[eea3bc70] [c03a7ad0] __alloc_pages+0x23c/0x1570
[eea3bde0] [c0379c8c] handle_mm_fault+0x610/0x1240
[eea3bed0] [c002e2d4] ___do_page_fault+0x19c/0x850
[eea3bf10] [c002ebbc] do_page_fault+0x28/0x5c
[eea3bf30] [c000433c] DataAccess_virt+0x124/0x17c
--- interrupt: 300 at 0x6fe0338c
NIP: 6fe0338c LR: 6fe032c4 CTR: 6fe033e0
REGS: eea3bf40 TRAP: 0300 Not tainted (5.18.0-rc6-PMacG4)
MSR: 0000d032 <EE,PR,ME,IR,DR,RI> CR: 48002262 XER: 20000000
DAR: 046a5000 DSISR: 42000000
GPR00: 6ffbcb94 afc45940 a7c95560 046a4fe4 8a000000 000127e0 03e59a8b 00000003
GPR08: 046a5004 046a5000 04621cfc 6fe03170 6fe032c4 6ffece34 00000000 6ffef34d
GPR16: 02dea020 04416750 00000003 01f8cbec 02de9fa0 01f8c660 00000000 00000000
GPR24: afc45aa0 6ffef37c afc45a18 04678c7c 0007630c 04678c7c 6ff76ff4 045f5990
NIP [6fe0338c] 0x6fe0338c
LR [6fe032c4] 0x6fe032c4
--- interrupt: 300
page:e739d6ec refcount:1 mapcount:0 mapping:00000000 index:0x1 pfn:0x290a3
flags: 0x80000000(zone=2)
raw: 80000000 00000100 00000122 00000000 00000001 00000000 ffffffff 00000001
raw: 00000000
page dumped because: pagealloc: corrupted page details
[...]
With THREAD_SHIFT=14 the stack issue does not show up.
A kernel with inline KASAN and same setup otherwise won't boot showing me this
at the OpenFirmware prompt:
[...]
Finalizing device tree... using OF tree (promptr=ff847240)
Invalid memory access at %SRR0: 40000000 %SRR1: 00000000
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-05-16 18:51 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-22 17:52 [Bug 215389] New: pagealloc: memory corruption at building glibc-2.33 and running its' testsuite bugzilla-daemon
2021-12-22 18:00 ` [Bug 215389] " bugzilla-daemon
2021-12-24 13:35 ` bugzilla-daemon
2021-12-26 8:38 ` bugzilla-daemon
2022-01-08 1:07 ` bugzilla-daemon
2022-01-08 18:14 ` bugzilla-daemon
2022-01-25 22:23 ` bugzilla-daemon
2022-01-26 6:41 ` bugzilla-daemon
2022-01-26 7:55 ` bugzilla-daemon
2022-01-30 20:12 ` bugzilla-daemon
2022-01-31 7:41 ` bugzilla-daemon
2022-01-31 23:33 ` bugzilla-daemon
2022-04-18 13:54 ` bugzilla-daemon
2022-04-18 13:54 ` bugzilla-daemon
2022-05-02 9:43 ` bugzilla-daemon
2022-05-02 11:59 ` bugzilla-daemon
2022-05-11 7:43 ` bugzilla-daemon
2022-05-11 7:44 ` bugzilla-daemon
2022-05-11 14:08 ` bugzilla-daemon
2022-05-12 14:44 ` bugzilla-daemon
2022-05-12 21:43 ` bugzilla-daemon
2022-05-13 2:31 ` bugzilla-daemon
2022-05-16 18:51 ` bugzilla-daemon [this message]
2022-05-16 18:52 ` bugzilla-daemon
2022-05-17 8:25 ` bugzilla-daemon
2022-05-17 8:31 ` bugzilla-daemon
2022-05-17 8:35 ` bugzilla-daemon
2022-05-28 11:49 ` bugzilla-daemon
2022-06-28 23:01 ` bugzilla-daemon
2022-06-28 23:02 ` bugzilla-daemon
2022-06-29 5:13 ` bugzilla-daemon
2022-06-29 10:25 ` bugzilla-daemon
2022-06-30 13:41 ` bugzilla-daemon
2022-07-05 16:02 ` bugzilla-daemon
2022-08-23 21:45 ` bugzilla-daemon
2022-08-23 21:56 ` bugzilla-daemon
2023-05-19 18:48 ` bugzilla-daemon
2023-05-23 19:55 ` bugzilla-daemon
2023-05-23 19:56 ` bugzilla-daemon
2023-05-23 21:17 ` bugzilla-daemon
2023-10-26 23:40 ` bugzilla-daemon
2023-10-26 23:41 ` bugzilla-daemon
2023-10-26 23:46 ` [Bug 215389] pagealloc: memory corruption with VMAP_STACK=y set and burdening the memory subsystem via "stress -c 2 --vm 2 --vm-bytes 896M" bugzilla-daemon
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=bug-215389-206035-mXo54QCqwv@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--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 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).