From: Siddhesh Poyarekar <siddhesh@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>, libc-alpha@sourceware.org
Cc: carlos@redhat.com, adhemerval.zanella@linaro.org
Subject: Re: [PATCH 1/4] Add framework for tunables
Date: Tue, 27 Dec 2016 21:25:00 -0000 [thread overview]
Message-ID: <54925e9c-d83f-cc43-3224-46e1f1ef8ddb@sourceware.org> (raw)
In-Reply-To: <e3f8ab87-0372-afcf-3596-ab9e3d66cac8@redhat.com>
On Wednesday 28 December 2016 02:41 AM, Florian Weimer wrote:
> Are you sure this is sufficient? You need to make sure that the value
> is zeroed out again after it has been populated from the environment and
> before it is used in any way by the dynamic linker.
Right, it isn't. I guess I'll be better off only avoiding the unsetenv
in rtld.c for now when !HAVE_TUNABLES and clearing dl_debug_mask all the
time.
Siddhesh
next prev parent reply other threads:[~2016-12-27 21:25 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 8:35 [PATCHv6 0/4] glibc tunables Siddhesh Poyarekar
2016-11-16 8:35 ` [PATCH 3/4] Enhance --enable-tunables to select tunables frontend at build time Siddhesh Poyarekar
2016-12-27 11:44 ` Florian Weimer
2016-12-27 21:10 ` Siddhesh Poyarekar
2016-12-27 21:16 ` Florian Weimer
2016-11-16 8:35 ` [PATCH 1/4] Add framework for tunables Siddhesh Poyarekar
2016-12-27 11:08 ` Florian Weimer
2016-12-27 20:59 ` Siddhesh Poyarekar
2016-12-27 21:12 ` Florian Weimer
2016-12-27 21:25 ` Siddhesh Poyarekar [this message]
2016-12-30 13:28 ` Joseph Myers
2016-12-31 13:48 ` Siddhesh Poyarekar
2016-11-16 8:35 ` [PATCH 4/4] User manual documentation " Siddhesh Poyarekar
2016-11-16 13:49 ` Rical Jasan
2016-11-21 3:07 ` Siddhesh Poyarekar
2016-11-16 8:35 ` [PATCH 2/4] Initialize tunable list with the GLIBC_TUNABLES environment variable Siddhesh Poyarekar
2016-12-27 11:41 ` Florian Weimer
2016-12-27 21:35 ` Siddhesh Poyarekar
2016-11-21 2:58 ` [ping][PATCHv6 0/4] glibc tunables Siddhesh Poyarekar
2016-11-24 13:31 ` [PING 2][PATCHv6 " Siddhesh Poyarekar
2016-11-28 11:52 ` [PING 3][PATCHv6 " Siddhesh Poyarekar
2016-12-05 12:08 ` [PING 4][PATCHv6 " Siddhesh Poyarekar
2016-12-05 15:10 ` Steven Munroe
2016-12-12 16:20 ` [PING 5][PATCHv6 " Siddhesh Poyarekar
2016-12-26 14:29 ` [PING 6][PATCHv6 " Siddhesh Poyarekar
2016-12-27 9:49 ` [PATCHv6 " Florian Weimer
2016-12-30 4:09 [PATCH v7 " Siddhesh Poyarekar
2016-12-30 4:09 ` [PATCH 1/4] Add framework for tunables Siddhesh Poyarekar
2017-02-06 22:36 ` Andreas Schwab
2017-02-07 6:49 ` Siddhesh Poyarekar
2017-02-07 16:06 ` Andreas Schwab
2017-02-08 8:48 ` Siddhesh Poyarekar
2017-02-06 22:59 ` Andreas Schwab
2016-12-31 15:41 [PATCH v8 0/4] glibc tunables Siddhesh Poyarekar
[not found] ` <1483198831-2232-2-git-send-email-siddhesh@sourceware.org>
2016-12-31 16:49 ` [PATCH 1/4] Add framework for tunables Florian Weimer
2016-12-31 17:58 ` Siddhesh Poyarekar
2016-12-31 19:43 ` Florian Weimer
2016-12-31 19:50 ` Siddhesh Poyarekar
2016-12-31 19:52 ` Florian Weimer
2017-01-01 13:40 ` Nix
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=54925e9c-d83f-cc43-3224-46e1f1ef8ddb@sourceware.org \
--to=siddhesh@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@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).