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>
Cc: Florian Weimer <fweimer@redhat.com>
Subject: Re: resolv/tst-resolv-res_init fails with unshare (CLONE_NEWUTS) failed: Operation not permitted
Date: Tue, 1 Mar 2022 19:40:45 +0000	[thread overview]
Message-ID: <DM5PR06MB3082343451AC8E9AA23AA418A3029@DM5PR06MB3082.namprd06.prod.outlook.com> (raw)
In-Reply-To: <87k0ddlbkv.fsf@oldenburg.str.redhat.com>

Thanks Florian  -

My ooppss  -    the FAIL was actually on
FAIL: resolv/tst-resolv-res_init-multi

But I looked in tst-resolv-res_init.out -    I should have looked in tst-resolv-res_init-multi.out   -    where I see something completely different  - a timeout  (which I think I have seen before)

Sorry for false alarm   (although now I have learned about unshare :-)

Cheers,   John Lumby

From: Florian Weimer <fweimer@redhat.com>
Sent: March 1, 2022 2:25 PM
To: John Lumby via Libc-help <libc-help@sourceware.org>
Cc: John Lumby <johnlumby@hotmail.com>
Subject: Re: resolv/tst-resolv-res_init fails with unshare (CLONE_NEWUTS) failed: Operation not permitted 
 
* John Lumby via Libc-help:

> 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.

It's just a warning, so it shouldn't cause a test failure.

Are there any other messages in the resolv/tst-resolv-res_init.out file?

Thanks,
Florian

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

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01 19:16 John Lumby
2022-03-01 19:25 ` Florian Weimer
2022-03-01 19:40   ` John Lumby [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=DM5PR06MB3082343451AC8E9AA23AA418A3029@DM5PR06MB3082.namprd06.prod.outlook.com \
    --to=johnlumby@hotmail.com \
    --cc=fweimer@redhat.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).