From: Dylan Jeffers <sapientech@openmailbox.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 24108@debbugs.gnu.org
Subject: bug#24108: guix make tests failure
Date: Sat, 30 Jul 2016 17:40:27 -0700 [thread overview]
Message-ID: <20160730174027.0551e855@openmailbox.org> (raw)
In-Reply-To: <87bn1ebynp.fsf@gnu.org>
On Sat, 30 Jul 2016 23:31:54 +0200
ludo@gnu.org (Ludovic Courtès) wrote:
> Dylan Jeffers <sapientech@openmailbox.org> skribis:
>
> > On Sat, 30 Jul 2016 15:07:25 +0200
> > ludo@gnu.org (Ludovic Courtès) wrote:
>
> [...]
>
> >> > test-name: clone
> >> > location: /home/sapientech/Dev/guix/guix_wip/tests/syscalls.scm:109
> >> > source:
> >> > + (test-assert
> >> > + "clone"
> >> > + (match (clone (logior CLONE_NEWUSER SIGCHLD))
> >> > + (0 (primitive-exit 42))
> >> > + (pid (and (not (equal?
> >> > + (readlink (user-namespace pid))
> >> > + (readlink (user-namespace
> >> > (getpid)))))
> >> > + (match (waitpid pid)
> >> > + ((_ . status) (= 42 (status:exit-val
> >> > status)))))))) actual-value: #f
> >> > actual-error:
> >> > + (system-error
> >> > + "clone"
> >> > + "~d: ~A"
> >> > + (268435473 "Operation not permitted")
> >> > + (1))
> >> > result: FAIL
> >>
> >> What does “uname -srv” report on this machine? It seems this
> >> kernel does not support namespaces.
> >>
> >> Thanks,
> >> Ludo’.
> >
> > Hi Ludo,
> >
> > Thanks for getting back so quick.
> > Output of uname -srv: Linux 4.6.4-gnu-201607192040-1-grsec #1 SMP
> > PREEMPT Wed Jul 20 15:37:34 UYT 2016
>
> These tests are skipped when user namespaces are not supported, as per
> this condition:
>
> (define perform-container-tests?
> (and (user-namespace-supported?)
> (unprivileged-user-namespace-supported?)))
>
> … which is true iff (1) /proc/self/ns/user exists, and (2)
> /proc/sys/kernel/unprivileged_userns_clone does not exist, or it
> exists and contains “1”.
>
> Do these files exist on this system?
(1) /proc/self/ns/user exists, and
(2) /proc/sys/kernel/unpriviledged_userns_clone D.N.E
Ideas on the best approach to allow the build to succeed?
I also have had issues with qemu, so it makes sense that vm/container
stuff both have issues. I have a feeling its due to the
grsec kernel.
https://wiki.archlinux.org/index.php/Grsecurity_Patchset talks a
bit about userspace/namespace hardening + issues with xen and
virtbox. Going to reboot with an lts kernel and try again. Will post
update...
Best,
Dylan
Best,
Dylan
next prev parent reply other threads:[~2016-07-31 0:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 23:26 bug#24108: guix make tests failure sapientech
2016-07-30 13:07 ` Ludovic Courtès
2016-07-30 17:43 ` Dylan Jeffers
2016-07-30 21:31 ` Ludovic Courtès
2016-07-31 0:40 ` Dylan Jeffers [this message]
2016-07-31 1:53 ` Dylan Jeffers
2016-07-31 10:53 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160730174027.0551e855@openmailbox.org \
--to=sapientech@openmailbox.org \
--cc=24108@debbugs.gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).