From: DJ Delorie <dj@redhat.com>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: nsswitch: do not reload if "/" changes
Date: Mon, 18 Jan 2021 13:35:52 -0500 [thread overview]
Message-ID: <xn4kjew0s7.fsf@greed.delorie.com> (raw)
In-Reply-To: <25a79acd-f739-83ec-5dcf-ab2bd771f561@redhat.com> (carlos@redhat.com)
"Carlos O'Donell" <carlos@redhat.com> writes:
> I'm not sure if this is possible though.
The tricky part is you only get *one* opportunity to change "/" so you
can't, for example, setup a pre- and post- testroot, unless - and this
is a maybe - nothing else invokes nsswitch.conf between exec() and
do_test().
And note that we can only test for the st_ino changing case, as creating
an environment where the testroot is "/" in a mounted filesystem (and
thus has st_ino 2 but a different st_dev) is way outside of glibc's
testsuite's scope. Not a big deal IMHO.
Note that inside the testroot we should be able to do a simpler form of
chroot, though. I don't think any test has tried this yet.
prev parent reply other threads:[~2021-01-18 18:35 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
2021-01-19 14:40 ` Florian Weimer
2021-01-18 18:35 ` DJ Delorie [this message]
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=xn4kjew0s7.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=carlos@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).