public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nsz at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/27181] New: __tunables_init can oom fail
Date: Thu, 14 Jan 2021 11:02:56 +0000 [thread overview]
Message-ID: <bug-27181-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27181
Bug ID: 27181
Summary: __tunables_init can oom fail
Product: glibc
Version: 2.32
Status: NEW
Severity: normal
Priority: P2
Component: dynamic-link
Assignee: unassigned at sourceware dot org
Reporter: nsz at gcc dot gnu.org
Target Milestone: ---
__tunables_init happens very early (before libc ifunc
resolvers are run).
it should not unnecessarily introduce failures, but
it allocates memory in tunables_strdup. this is only
needed in setuid executables when the GLIBC_TUNABLES
env var has to be sanitized, so there should be no
failure mode in other cases.
with static pie __tunables_init will happen before self
relocation (after bug 27072 is fixed) so complex code
like _dl_fatal_printf should not be used there otherwise
it's hard to guarantee that there are no relocations.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-01-14 11:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 11:02 nsz at gcc dot gnu.org [this message]
2021-01-21 15:59 ` [Bug dynamic-link/27181] " cvs-commit at gcc dot gnu.org
2024-05-01 18:05 ` adhemerval.zanella at linaro dot org
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-27181-131@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: 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 read-only IMAP folder(s) and NNTP newsgroup(s).