From: DJ Delorie <dj@redhat.com>
To: Vineet Gupta <Vineet.Gupta1@synopsys.com>
Cc: linux-snps-arc@lists.infradead.org, libc-alpha@sourceware.org,
ahajkova@redhat.com
Subject: Re: How to elf/tst-ldconfig-* in cross test setup
Date: Wed, 11 Mar 2020 18:23:37 -0400 [thread overview]
Message-ID: <xnwo7q4jkm.fsf@greed.delorie.com> (raw)
In-Reply-To: <59f54822-4b8e-fefb-045d-cbd447e0e72d@synopsys.com> (message from Vineet Gupta on Wed, 11 Mar 2020 22:14:26 +0000)
Vineet Gupta <Vineet.Gupta1@synopsys.com> writes:
> When you say containers is this linux cgroups or something at a higher
> level: does it need any specific distro container package. Please
> remember this is a constrained system built off of buildroot.
It should not require anything beyond what kernel/glibc provides - we
even build our own /bin/sh for in-container use. All the
containerization code is in support/test-container.c. However, some
kernels and/or OSs are *configured* (i.e. for security reasons) to
disallow certain types of namespace unsharing - those should be detected
by test-container and flagged as unsupported tests.
By "container" I mean a simple filesystem/pid namespace using unshare,
sort of a fancy chroot() but it changes your UID and PID also.
See https://developers.redhat.com/blog/2018/11/16/microcontainers-for-unit-testing/
for some background info.
_______________________________________________
linux-snps-arc mailing list
linux-snps-arc@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-snps-arc
prev parent reply other threads:[~2020-03-11 22:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 19:56 How to elf/tst-ldconfig-* in cross test setup Vineet Gupta
2020-03-11 21:36 ` DJ Delorie
2020-03-11 21:50 ` Vineet Gupta
2020-03-11 22:07 ` DJ Delorie
2020-03-11 22:14 ` Vineet Gupta
2020-03-11 22:21 ` Vineet Gupta
2020-03-11 22:28 ` DJ Delorie
2020-03-11 22:38 ` Vineet Gupta
2020-03-11 22:56 ` Vineet Gupta
2020-03-12 0:53 ` Vineet Gupta
2020-03-11 22:23 ` 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=xnwo7q4jkm.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=Vineet.Gupta1@synopsys.com \
--cc=ahajkova@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-snps-arc@lists.infradead.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