public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: John Lumby <johnlumby@hotmail.com>
To: libc help <libc-help@sourceware.org>
Subject: resolv/tst-resolv-res_init fails with unshare (CLONE_NEWUTS) failed: Operation not permitted
Date: Tue, 1 Mar 2022 19:16:20 +0000	[thread overview]
Message-ID: <DM5PR06MB3082B77DAEC2123077A037FDA3029@DM5PR06MB3082.namprd06.prod.outlook.com> (raw)

Apologies if this has been answered elsewhere.

under linux-5.16.9 I am building and testing glibc-2.35 and get one FAIL in the test suite :   glibc-build/resolv/tst-resolv-res_init.out contains :

warning: could not become root outside namespace (Operation not permitted)
warning: unshare (CLONE_NEWUTS) failed: Operation not permitted
warning: could not enter network namespace

I think the cause if that is this code in support/support_become_root.c

       unshare (CLONE_NEWUSER | CLONE_NEWNS)

is getting EPERM.

After reading the man page for unshare() I am none the wiser about whether  :
    .   the userid running the test is missing some capability that is needed in order to run the test  -  if so ,   what?
    .   there is some environmental problem   -  if so ,   how can I find out what?
    .  or is this test supposed to be run by root? (I think not but unclear)

I am sure the answer is buried somewhere in some doc but if anyone can help me get there I would be grateful.

Cheers,   John Lumby

             reply	other threads:[~2022-03-01 19:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 19:16 John Lumby [this message]
2022-03-01 19:25 ` Florian Weimer
2022-03-01 19:40   ` John Lumby

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=DM5PR06MB3082B77DAEC2123077A037FDA3029@DM5PR06MB3082.namprd06.prod.outlook.com \
    --to=johnlumby@hotmail.com \
    --cc=libc-help@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).