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: Tue, 05 Jul 2022 16:02:25 +0000 [thread overview]
Message-ID: <bug-215389-206035-NURmfdrVxD@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 #33 from Erhard F. (erhard_f@mailbox.org) ---
Created attachment 301337
--> https://bugzilla.kernel.org/attachment.cgi?id=301337&action=edit
dmesg (5.19-rc5, outline KASAN, PowerMac G4 DP)
Re-tested on 5.19-rc5 +
https://patchwork.ozlabs.org/project/linuxppc-dev/patch/2ee707512b8b212b079b877f4ceb525a1606a3fb.1656655567.git.christophe.leroy@csgroup.eu/
I can run the kernel with outline KASAN, default THREAD_SHIFT and without
advanced options necessary. Also I don't get the stack issue (bug #216041) any
longer.
However as long as CONFIG_SMP=y (CONFIG_NR_CPUS=2) is set I still get the
memory corruption:
[...]
pagealloc: memory corruption
f5fcfff0: 00 00 00 00 ....
CPU: 1 PID: 27635 Comm: estrip Not tainted 5.19.0-rc5-PMacG4+ #1
Call Trace:
[f380b9b0] [c0829ebc] dump_stack_lvl+0x60/0x90 (unreliable)
[f380b9d0] [c0307528] __kernel_unpoison_pages+0x1d8/0x220
[f380ba20] [c02dd3bc] post_alloc_hook+0x108/0x144
[f380ba50] [c02e0a70] get_page_from_freelist+0x9e0/0x1278
[f380bb90] [c02e1e04] __alloc_pages+0x250/0x1078
[f380bcf0] [c02af098] wp_page_copy+0x128/0xdb8
[f380bde0] [c02b6fdc] handle_mm_fault+0x954/0x1138
[f380bed0] [c0029938] ___do_page_fault+0x250/0x84c
[f380bf10] [c002a168] do_page_fault+0x28/0x5c
[f380bf30] [c000433c] DataAccess_virt+0x124/0x17c
--- interrupt: 300 at 0x65b734
NIP: 0065b734 LR: 0065b708 CTR: 00354600
REGS: f380bf40 TRAP: 0300 Not tainted (5.19.0-rc5-PMacG4+)
MSR: 0000d032 <EE,PR,ME,IR,DR,RI> CR: 82222420 XER: 00000000
DAR: 026fcea0 DSISR: 0a000000
GPR00: 00000000 afbd5250 a7b0c560 026bb5f0 0269deac 026bb628 696e6f64 026fcea0
GPR08: 00000000 00000000 00000000 00354600 42222420 0071fff4 026af620 0072243c
GPR16: 00723b50 007223a4 026b1770 026ec8a0 007222e4 0269de70 02700920 00000001
GPR24: 00721e9c 00721eb8 0072082c 00000000 afbd52ec 00000000 0072608c 00000000
NIP [0065b734] 0x65b734
LR [0065b708] 0x65b708
--- interrupt: 300
page:ef4bd6ec refcount:1 mapcount:0 mapping:00000000 index:0x1 pfn:0x310a3
flags: 0x80000000(zone=2)
raw: 80000000 00000100 00000122 00000000 00000001 00000000 ffffffff 00000001
raw: 00000000
page dumped because: pagealloc: corrupted page details
--
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-07-05 16:03 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
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 [this message]
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-NURmfdrVxD@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).