Re: [PATCH v4] rtld: Add --no-default-paths option

[Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>]

On 8/1/21 10:34 PM, Fergus Dall wrote:
>>>> Changes from previous patchset:
>>>>  - Incorporated vapier's suggestions.
>>>>  - Initialized the path buffers in the tests, as strcat-ing into an
>>>>    uninitialized buffer is undefined behavior.
>>>>  - Stop adding support_install_prefix in tst-no-default-paths-dlopen
>>>>    when constructing the path to the system lib directory. This
>>>>    happened to work because I tested with prefix=/, but is in general
>>>>    unnecessary and incorrect.

I looked over the series in patchwork, particularly looking for a broader
explanation of use cases in the commit, but I didn't see it there, and
I went back over the various discussions around the patch series but didn't
see any justification there either. This doesn't constitute an objection
to the series, but just a note that the work is missing a purpose statement.

What is the purpose behind adding this behaviour?

What use cases exist?

How do users use this feature?

How do you see chromeos using the feature?

I can think of some ways to use this but I'm interested to hear your
explanation, and seeing that echoed in a man page, manual, or detailed
commit message.

-- 
Cheers,
Carlos.