From: Thiago Jung Bauermann via Guix-patches via <guix-patches@gnu.org>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 49933@debbugs.gnu.org
Subject: [bug#49933] [PATCH core-updates-frozen] gnu: util-linux: Disable unreliable ioctl_ns test
Date: Mon, 09 Aug 2021 13:09:39 -0300 [thread overview]
Message-ID: <1671752.noS1iWLZrW@popigai> (raw)
In-Reply-To: <a947525a7232955d6f22f2e6ff9c9b2b7e16d9df.camel@telenet.be>
Hello Maxime,
Thank you for sending a v2. It looks good to me.
Em domingo, 8 de agosto de 2021, às 07:56:23 -03, Maxime Devos escreveu:
> Maxime Devos schreef op zo 08-08-2021 om 11:06 [+0200]:
> > + ;; The lsns tests can fail due to
> > ioctl(_, NS_GET_USERNS) + ;; returning
> > ENOTTY, indicating this kernel does not +
> > ;; support user namespaces. Curiously, this test can fail +
> > ;; on i686 even if the same test passes on x86_64
> > on the + ;; same machine. See
> > <https://issues.guix.gnu.org/49933>;.
> This happend with a 5.10.47 kernel. According to ioctl_ns(2),
> NS_GET_USERNS is available since Linux 4.9. I wonder if this happens on
> i686 kernels as well, and if some extra things needs to be enabled in
> the kernel configuration.
Out of curiosity, I created an i686 KVM guest running Guix System, and the
test passes there, on the core-updates-frozen branch. So it seems to be an
issue with the x86_64 kernel running 32-bit binaries.
I also noticed that the ioctl_ns test is new in util-linux. It was added in
version 2.37.
--
Thanks,
Thiago
next prev parent reply other threads:[~2021-08-09 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 21:54 [bug#49933] [PATCH core-updates-frozen] gnu: util-linux: Disable unreliable ioctl_ns test Maxime Devos
2021-08-08 6:27 ` Thiago Jung Bauermann via Guix-patches via
2021-08-08 9:06 ` Maxime Devos
2021-08-08 10:56 ` Maxime Devos
2021-08-09 16:09 ` Thiago Jung Bauermann via Guix-patches via [this message]
2021-08-15 10:16 ` bug#49933: " Mathieu Othacehe
2021-11-09 9:07 ` [bug#49933] " Brendan Tildesley
2021-11-12 0:29 ` Thiago Jung Bauermann via Guix-patches via
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=1671752.noS1iWLZrW@popigai \
--to=guix-patches@gnu.org \
--cc=49933@debbugs.gnu.org \
--cc=bauermann@kolabnow.com \
--cc=maximedevos@telenet.be \
/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).