public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Siddhesh Poyarekar <siddhesh@sourceware.org>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH 1/2] Add framework for tunables
Date: Tue, 12 Jul 2016 09:00:00 -0000	[thread overview]
Message-ID: <6ffa6c62-c7be-22bf-18b2-ca98ef036d4d@redhat.com> (raw)
In-Reply-To: <20160711163929.GC29880@devel.intra.reserved-bit.com>

On 07/11/2016 06:39 PM, Siddhesh Poyarekar wrote:
>>> > > +- secure_env_alias:	Specify whether the environment variable should be read
>>> > > +			for setuid binaries.
>> >
>> > This needs to describe the exact meaning of the choices, and the default.
>> > I'm not sure if the current/name values are intuitive.
> It specifies if the env_alias should be read even for setuid binaries.
> This is currently only useful for MALLOC_CHECK_ since it is read even
> for setuid binaries.  Would env_alias_is_secure be clearer?

No, because I think the sense is reverted:

+    check {
+      type: INT_32
+      minval: 0
+      maxval: 3
+      env_alias: MALLOC_CHECK_
+      secure_env_alias: true
+    }

That's why I said you need to document what the options are and what 
they do in AT_SECURE mode, and the default value.

Thanks,
Florian

  parent reply	other threads:[~2016-07-12  9:00 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-09 18:49 [PATCHv3 0/2] tunables for glibc Siddhesh Poyarekar
2016-07-09 18:49 ` [PATCH 1/2] Add framework for tunables Siddhesh Poyarekar
2016-07-11 16:05   ` Florian Weimer
2016-07-11 16:39     ` Siddhesh Poyarekar
2016-07-11 19:13       ` DJ Delorie
2016-07-12  9:00       ` Florian Weimer [this message]
2016-07-12  8:51     ` Florian Weimer
2016-07-11 16:25   ` H.J. Lu
2016-07-11 16:41     ` Siddhesh Poyarekar
2016-07-13 14:43       ` H.J. Lu
2016-07-13 14:49         ` Siddhesh Poyarekar
2016-07-13 17:38           ` H.J. Lu
2016-07-13 17:56             ` Siddhesh Poyarekar
2016-07-13 17:59               ` H.J. Lu
2016-07-13 18:03                 ` H.J. Lu
2016-07-14  6:57                   ` Siddhesh Poyarekar
2016-07-11 16:56   ` Paul E. Murphy
2016-07-11 17:28     ` H.J. Lu
2016-07-11 19:06   ` Carlos O'Donell
2016-07-14 11:27     ` Siddhesh Poyarekar
2016-07-09 18:49 ` [PATCH 2/2] Initialize tunable list with the GLIBC_TUNABLES environment variable Siddhesh Poyarekar
  -- strict thread matches above, loose matches on Subject: below --
2016-08-15 20:05 [PATCHv4 0/2] tunables for glibc Siddhesh Poyarekar
2016-08-15 20:05 ` [PATCH 1/2] Add framework for tunables Siddhesh Poyarekar
2016-07-02 17:13 [PATCH 0/2] tunables for glibc Siddhesh Poyarekar
2016-07-02 17:13 ` [PATCH 1/2] Add framework for tunables Siddhesh Poyarekar
2016-07-03 14:30   ` H.J. Lu
2016-07-03 17:08     ` Siddhesh Poyarekar
2016-07-03 14:44   ` H.J. Lu
2016-07-03 17:14     ` Siddhesh Poyarekar
2016-07-03 17:41       ` H.J. Lu
2016-07-03 15:13   ` H.J. Lu
2016-07-03 17:43     ` H.J. Lu
2016-07-03 18:20       ` Siddhesh Poyarekar
2016-07-01 18:31 [PATCH 0/2] Tunables for glibc Siddhesh Poyarekar
2016-07-01 18:32 ` [PATCH 1/2] Add framework for tunables Siddhesh Poyarekar
2016-01-11 11:17 Siddhesh Poyarekar
2016-01-11 16:34 ` Andi Kleen
2016-01-11 16:55   ` Siddhesh Poyarekar
2016-01-11 16:39 ` Paul E. Murphy
2016-01-11 16:54   ` Siddhesh Poyarekar
2016-01-11 17:07     ` Andreas Schwab
2016-01-11 17:10       ` Siddhesh Poyarekar
2016-01-11 18:11         ` Zack Weinberg
2016-01-12  2:15           ` Siddhesh Poyarekar
2016-01-11 19:02 ` Joseph Myers
2016-01-12  2:18   ` Siddhesh Poyarekar

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=6ffa6c62-c7be-22bf-18b2-ca98ef036d4d@redhat.com \
    --to=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh@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).