public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>,
	GNU C Library <libc-alpha@sourceware.org>,
	Andreas Schwab <schwab@suse.de>,
	"Dmitry V. Levin" <ldv@altlinux.org>
Subject: Re: [PATCH] Improve DST handling (Bug 23102, Bug 21942, Bug 18018, Bug, 23259, CVE-2011-0536 ).
Date: Wed, 06 Jun 2018 15:59:00 -0000	[thread overview]
Message-ID: <0ba1f0fc-b48a-17ac-3730-9fd31bad516e@redhat.com> (raw)
In-Reply-To: <8bbb5ce3-f0ee-9656-1e11-17ba07d7722f@redhat.com>

On 06/06/2018 10:15 AM, Florian Weimer wrote:
> On 06/06/2018 07:02 AM, Carlos O'Donell wrote:
>> +/* Passed the start of a DST sequence at the first '$' occurrence.
>> +   See the DL_DST_COUNT macro which inlines the strchr to find the
>> +   first occurrence of '$' and optimizes that likely case that there
>> +   is no DST.  If there is a DST we call into _dl_dst_count to count
>> +   the number of DSTs.  We count all known DSTs regardless of
>> +   __libc_enable_secure; the caller is responsible for enforcing
>> +   the security of the substitution rules (usually
>> +   _dl_dst_substitute).  */
> 
> Maybe kill DL_DST_COUNT?  It doesn't look useful to me.

Killed.

>> +      /* All DSTs must follow ELF gABI rules, see is_dst ().  */
>> +      if ((len = is_dst (name, "ORIGIN")) != 0
>> +      || (len = is_dst (name, "PLATFORM")) != 0
>> +      || (len = is_dst (name, "LIB")) != 0)
>>       ++cnt;
> 
> len is never read, so you can remove the variable.

Removed.

v2 patch coming up.

Cheers,
Carlos

  reply	other threads:[~2018-06-06 15:59 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-06  5:03 Carlos O'Donell
2018-06-06 14:01 ` Florian Weimer
2018-06-06 14:55   ` Carlos O'Donell
2018-06-06 14:17 ` Florian Weimer
2018-06-06 15:59   ` Carlos O'Donell [this message]
2018-06-06 15:47 ` Andreas Schwab
2018-06-06 16:01   ` Carlos O'Donell
2018-06-06 16:10 ` Carlos O'Donell
2018-06-06 16:31   ` Andreas Schwab
2018-06-06 17:10     ` Carlos O'Donell
2018-06-06 17:28       ` Florian Weimer
2018-06-06 18:49         ` Carlos O'Donell
2018-06-06 18:56           ` Florian Weimer
2018-06-06 20:04             ` Carlos O'Donell
2018-06-07  6:49       ` Andreas Schwab
2018-06-08  2:08         ` Carlos O'Donell
2018-06-11  8:04           ` Andreas Schwab
2018-06-12  3:08             ` Carlos O'Donell
2018-06-12  7:31               ` Andreas Schwab
2018-06-12 12:46                 ` Carlos O'Donell
2018-06-12 13:02                   ` Andreas Schwab
2018-06-12 13:03                     ` Carlos O'Donell
2018-06-06 20:19   ` Carlos O'Donell
2018-06-07 11:38     ` Florian Weimer
2018-06-08  2:14       ` Carlos O'Donell
2018-06-07 12:16     ` Florian Weimer
2018-06-08  4:15       ` Carlos O'Donell
2018-06-08  5:21         ` Florian Weimer
2018-06-08  5:46           ` Carlos O'Donell
2018-06-08  5:50             ` Carlos O'Donell
2018-06-07 12:43     ` Florian Weimer
2018-06-08  5:37       ` Carlos O'Donell
2018-06-08  5:45     ` [PATCH v4] " Carlos O'Donell
2018-06-08  5:51       ` Florian Weimer
2018-06-08  6:03         ` Carlos O'Donell
2018-06-08  6:25           ` Florian Weimer
2018-06-11  2:55             ` Carlos O'Donell
2018-06-11  7:28               ` Florian Weimer
2018-06-11 14:44                 ` Carlos O'Donell
2018-06-12  3:46       ` Carlos O'Donell
2018-06-12 13:08         ` [PATCH v6] " Carlos O'Donell
2018-06-12 13:20           ` Andreas Schwab
2018-06-12 13:23             ` Andreas Schwab
2018-06-12 14:10               ` Carlos O'Donell
2018-06-12 14:34                 ` Andreas Schwab
2018-06-12 14:31           ` Florian Weimer
2018-06-12 14:36             ` Carlos O'Donell

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=0ba1f0fc-b48a-17ac-3730-9fd31bad516e@redhat.com \
    --to=carlos@redhat.com \
    --cc=fweimer@redhat.com \
    --cc=ldv@altlinux.org \
    --cc=libc-alpha@sourceware.org \
    --cc=schwab@suse.de \
    /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).