public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Michael Hudson-Doyle via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH v2] linux: return UNSUPPORTED in tst-mount if !support_can_chroot
Date: Fri, 15 Jul 2022 09:07:17 +0200	[thread overview]
Message-ID: <8735f2onve.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20220715000657.1712606-1-michael.hudson@canonical.com> (Michael Hudson-Doyle via Libc-alpha's message of "Fri, 15 Jul 2022 12:06:57 +1200")

* Michael Hudson-Doyle via Libc-alpha:

> Otherwise the test fails if run in a chroot by a non-root user:
>
> warning: could not become root outside namespace (Operation not permitted)
> ../sysdeps/unix/sysv/linux/tst-mount.c:36: numeric comparison failure
>    left: 1 (0x1); from: errno
>   right: 19 (0x13); from: ENODEV
> error: ../sysdeps/unix/sysv/linux/tst-mount.c:39: not true: fd != -1
> error: ../sysdeps/unix/sysv/linux/tst-mount.c:46: not true: r != -1
> error: ../sysdeps/unix/sysv/linux/tst-mount.c:48: not true: r != -1
> ../sysdeps/unix/sysv/linux/tst-mount.c:52: numeric comparison failure
>    left: 1 (0x1); from: errno
>   right: 9 (0x9); from: EBADF
> error: ../sysdeps/unix/sysv/linux/tst-mount.c:55: not true: mfd != -1
> ../sysdeps/unix/sysv/linux/tst-mount.c:58: numeric comparison failure
>    left: 1 (0x1); from: errno
>   right: 2 (0x2); from: ENOENT
> error: ../sysdeps/unix/sysv/linux/tst-mount.c:61: not true: r != -1
> ../sysdeps/unix/sysv/linux/tst-mount.c:65: numeric comparison failure
>    left: 1 (0x1); from: errno
>   right: 2 (0x2); from: ENOENT
> error: ../sysdeps/unix/sysv/linux/tst-mount.c:68: not true: pfd != -1
> error: ../sysdeps/unix/sysv/linux/tst-mount.c:75: not true: fd_tree != -1
> ../sysdeps/unix/sysv/linux/tst-mount.c:88: numeric comparison failure
>    left: 1 (0x1); from: errno
>   right: 38 (0x26); from: ENOSYS
> error: 12 test failures
> ---
> v2: check support_can_chroot() rather than support_become_root return
> value
> ---
>  sysdeps/unix/sysv/linux/tst-mount.c | 3 +++
>  1 file changed, 3 insertions(+)
>
> diff --git a/sysdeps/unix/sysv/linux/tst-mount.c b/sysdeps/unix/sysv/linux/tst-mount.c
> index 502d7e3433..a0b367d9df 100644
> --- a/sysdeps/unix/sysv/linux/tst-mount.c
> +++ b/sysdeps/unix/sysv/linux/tst-mount.c
> @@ -20,6 +20,7 @@
>  #include <support/check.h>
>  #include <support/xunistd.h>
>  #include <support/namespace.h>
> +#include <support/test-driver.h>
>  #include <sys/wait.h>
>  #include <sys/mount.h>
>  
> @@ -104,6 +105,8 @@ static int
>  do_test (void)
>  {
>    support_become_root ();
> +  if (!support_can_chroot ())
> +    return EXIT_UNSUPPORTED;
>  
>    pid_t pid = xfork ();
>    if (pid == 0)

This test still hoses the system if run as root on a system without user
namespaces.

I think you should call and check support_enter_mount_namespace instead,
to make sure that the test does not modify the original mount namespace.

Thanks,
Florian


  reply	other threads:[~2022-07-15  7:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-14  3:23 [PATCH] linux: return UNSUPPORTED in tst-mount if support_become_root fails Michael Hudson-Doyle
2022-07-14 11:24 ` Adhemerval Zanella Netto
2022-07-14 19:03   ` Carlos O'Donell
2022-07-14 19:18 ` DJ Delorie
2022-07-14 22:50   ` Michael Hudson-Doyle
2022-07-14 23:16     ` DJ Delorie
2022-07-15  0:06 ` [PATCH v2] linux: return UNSUPPORTED in tst-mount if !support_can_chroot Michael Hudson-Doyle
2022-07-15  7:07   ` Florian Weimer [this message]
2022-07-15 15:35     ` Carlos O'Donell
2022-07-15 15:44       ` Florian Weimer
2022-07-17 21:44         ` Michael Hudson-Doyle
2022-07-15 21:01       ` Michael Hudson-Doyle
2022-07-16  0:26         ` Carlos O'Donell
2022-07-17 23:16   ` [PATCH v3] linux: return UNSUPPORTED from tst-mount if entering mount namespace fails Michael Hudson-Doyle
2022-07-18 12:59     ` Carlos O'Donell
2022-07-18 18:59       ` Michael Hudson-Doyle
2022-07-19  2:51         ` Carlos O'Donell
2022-07-18 13:13     ` Mark Wielaard
2022-07-18 13:45       ` Carlos O'Donell

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=8735f2onve.fsf@oldenburg.str.redhat.com \
    --to=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).