From: Carlos O'Donell <carlos@redhat.com>
To: Florian Weimer <fweimer@redhat.com>,
Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: nsswitch: do not reload if "/" changes
Date: Tue, 19 Jan 2021 09:30:09 -0500 [thread overview]
Message-ID: <7109c06d-5f0b-99a2-2aad-9c50bb89c0cb@redhat.com> (raw)
In-Reply-To: <87eeiinq4o.fsf@oldenburg.str.redhat.com>
On 1/18/21 11:53 AM, Florian Weimer wrote:
> * Carlos O'Donell via Libc-alpha:
>
>> Can we create a non-test-container test for this?
>>
>> I think you can use support_become_root to unshare and then try
>> to use support_chroot_create/support_chroot_free and xhcroot to
>> change root, and then try to do an NSS call that will fail?
>
> You need to chroot twice, first to get a defined /etc/nsswitch.conf, and
> another one to make sure things don't ger reloaded after chroot.
That would be a perfect solution.
However, I think you could get away with recording some known uid/gid
from the system that was doing the build and then ensure that value
is not present in the container.
> You probably also have to copy different service modules into the two
> chroots.
Correct.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2021-01-19 14:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 0:59 DJ Delorie
2021-01-16 10:52 ` Florian Weimer
2021-01-18 1:13 ` DJ Delorie
2021-01-18 10:47 ` Florian Weimer
2021-01-18 18:20 ` DJ Delorie
2021-01-19 16:37 ` Florian Weimer
2021-01-22 19:10 ` [v2] " DJ Delorie
2021-01-26 9:58 ` Florian Weimer
2021-01-26 16:19 ` DJ Delorie
2021-01-26 16:30 ` Florian Weimer
2021-01-26 16:47 ` DJ Delorie
2021-01-27 17:28 ` Carlos O'Donell
2021-01-27 18:44 ` DJ Delorie
2021-01-28 0:31 ` Joseph Myers
2021-01-28 0:34 ` DJ Delorie
2021-01-28 0:39 ` Joseph Myers
2021-01-28 1:15 ` DJ Delorie
2021-01-18 12:42 ` Andreas Schwab
2021-01-18 12:53 ` Florian Weimer
2021-01-18 18:27 ` DJ Delorie
2021-01-18 15:59 ` Carlos O'Donell
2021-01-18 16:53 ` Florian Weimer
2021-01-19 14:30 ` Carlos O'Donell [this message]
2021-01-19 14:40 ` Florian Weimer
2021-01-18 18:35 ` DJ Delorie
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=7109c06d-5f0b-99a2-2aad-9c50bb89c0cb@redhat.com \
--to=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).