All of lore.kernel.org
 help / color / mirror / Atom feed
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, 31 Jan 2022 23:33:13 +0000	[thread overview]
Message-ID: <bug-215389-206035-4W4sAdcLtr@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 #11 from Erhard F. (erhard_f@mailbox.org) ---
(In reply to Christophe Leroy from comment #10)
> I'm wondering whether you could be running out of vmalloc space. I initially
> thought you were using KASAN, but it seems not according to your .config.
Correct, I was not using KASAN. I use it only for testing -rc kernels or when I
am particularly wary. This memory corruption I noticed during regular usage.
Seems running the kernel with slub_debug=FZP page_poison=1 is a good thing. ;)

> Could you try reducing CONFIG_LOWMEM_SIZE to 0x28000000 for instance and see
> if the memory corruption still happens ?
Thanks, that did the trick! With CONFIG_LOWMEM_SIZE=0x28000000 the memory
corruption is gone on VMAP_STACK enabled kernels. Tested it additionally on
current 5.16.4 where this works too.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-01-31 23:34 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 [this message]
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
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-4W4sAdcLtr@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 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.