public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@redhat.com>
To: Fergus Dall <sidereal@google.com>,
	libc-alpha@sourceware.org, clumptini <clumptini@google.com>,
	chromeos-toolchain@google.com
Subject: Re: [PATCH] rtld: Add --no-default-paths option
Date: Tue, 25 May 2021 08:01:26 -0400	[thread overview]
Message-ID: <88cbbd09-ce7a-7cb3-f2fd-38804eeac645@redhat.com> (raw)
In-Reply-To: <YKxtd/zxAHcim8Ch@vapier>

On 5/24/21 11:22 PM, Mike Frysinger via Libc-alpha wrote:
> On 25 May 2021 12:25, Fergus Dall via Libc-alpha wrote:
>> This option implies --inhibit-cache, as there is no point
>> in searching a cache of system libraries when we are not using the
>> system libraries at all.
> 
> i'm on the fence about this.  i don't disagree with your logic, but it
> still seems like we have a dedicated --inhibit-cache option, so might as
> well leave it at that.
> 
> logic-wise, code seems OK.  would be nice to add a test, but this is a bit
> hard as it relies on the installed / paths.

We have containerized tests now that can use installed paths.

We have tests for corrupted cache, NSS, localedef invocation etc. all that
depend on installed paths to trigger the specific code.

We *should* be creating tests in all of the cases where we lacked them
before because of installed path problems.

> 
>> +int _dl_no_default_paths;
> 
> i try to avoid negative variables as it makes reading code harder.
> how about "_dl_search_default_paths" ?
> 
>> --- a/elf/dl-usage.c
>> +++ b/elf/dl-usage.c
>>
>> +  --no-default-paths    Do not use the default library search path\n\a
>> +                        This option implies --inhibit-cache\n\
> 
> prob should read:
>   --no-default-paths    do not use the default library search path\n\a
>                         (this option implies --inhibit-cache)\n\
> -mike
> 


-- 
Cheers,
Carlos.


  reply	other threads:[~2021-05-25 12:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25  2:25 Fergus Dall
2021-05-25  3:22 ` Mike Frysinger
2021-05-25 12:01   ` Carlos O'Donell [this message]
2021-05-26  8:10     ` Fergus Dall
2021-05-25 17:34 ` Joseph Myers
2021-06-07 10:28 ` [PATCH v3 1/2] " Fergus Dall
2021-06-09  5:43   ` Mike Frysinger

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=88cbbd09-ce7a-7cb3-f2fd-38804eeac645@redhat.com \
    --to=carlos@redhat.com \
    --cc=chromeos-toolchain@google.com \
    --cc=clumptini@google.com \
    --cc=libc-alpha@sourceware.org \
    --cc=sidereal@google.com \
    /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).