public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/31076] Extra struct vm_area_struct with ---p created when PAGE_SIZE < max-page-size Date: Mon, 27 Nov 2023 15:11:07 +0000 [thread overview] Message-ID: <bug-31076-131-Vu4N5p2Ql9@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31076-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31076 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fweimer at redhat dot com --- Comment #5 from Florian Weimer <fweimer at redhat dot com> --- I don't see how a 152 byte struct results in 30 MB of unreclaimable kernel memory. Wouldn't that need ~200,000 instances? That seems really large. I've only got ~70,000 lines in /proc/*/maps on this desktop system, and not all these mappings will exhibit this issue. Would it help if we use MAP_FIXED with PROT_NONE to map over these unused parts? But as far as I understand it, these tails have not been written to, so it shouldn't matter if the underlying memory needs to be preserved by the kernel or not. Regarding not doing the mprotect altogether, I believe this would result in a loss of functionality. Today, you can use the current behavior to get as few gadgets as possible in the process image on systems with smaller page sizes, while still maintaining run-time compatibility with larger page sizes and avoiding on-disk padding (which would increase file size). If we stop doing the mprotect, then the gadgets would become visible even with smaller page sizes. At least in principle, it should be possible for a link editor to produce objects that do not require tail adjustment because the load segments are usable as-is (but I understand that there are link editor limitations in this area today). -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-11-27 15:11 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-11-18 18:48 [Bug dynamic-link/31076] New: " jyescas at google dot com 2023-11-18 18:50 ` [Bug dynamic-link/31076] " jyescas at google dot com 2023-11-21 13:42 ` carlos at redhat dot com 2023-11-22 0:39 ` i at maskray dot me 2023-11-22 4:33 ` kaleshsingh at google dot com 2023-11-22 18:19 ` jyescas at google dot com 2023-11-23 11:42 ` sam at gentoo dot org 2023-11-24 17:40 ` adhemerval.zanella at linaro dot org 2023-11-27 15:11 ` fweimer at redhat dot com [this message] 2023-11-27 15:22 ` fweimer at redhat dot com 2023-11-27 16:27 ` adhemerval.zanella at linaro dot org 2023-11-27 17:19 ` fweimer at redhat dot com 2023-11-27 17:39 ` adhemerval.zanella at linaro dot org 2023-11-27 17:45 ` fweimer at redhat dot com 2023-11-27 17:58 ` adhemerval.zanella at linaro dot org 2023-11-27 19:47 ` jyescas at google dot com 2023-11-27 19:55 ` jyescas at google dot com 2023-11-28 8:48 ` rprichard at google dot com 2023-11-28 18:59 ` kaleshsingh at google dot com 2023-11-28 23:58 ` jyescas at google dot com 2023-12-02 17:08 ` i at maskray dot me 2023-12-06 11:57 ` fweimer at redhat dot com 2023-12-07 5:11 ` i at maskray dot me 2023-12-07 9:30 ` fweimer at redhat dot com 2023-12-08 3:22 ` i at maskray dot me
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-31076-131-Vu4N5p2Ql9@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sourceware.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: linkBe 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 read-only IMAP folder(s) and NNTP newsgroup(s).