public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: DJ Delorie <dj@redhat.com>, <libc-alpha@sourceware.org>
Subject: Re: [patch v6] Allow for unpriviledged nested containers
Date: Tue, 5 Apr 2022 15:57:40 +0000	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2204051556090.377353@digraph.polyomino.org.uk> (raw)
In-Reply-To: <b50438bb-df00-da9c-a7d2-3fbf9a99566b@redhat.com>

On Mon, 4 Apr 2022, Carlos O'Donell via Libc-alpha wrote:

> > @@ -726,6 +755,9 @@ main (int argc, char **argv)
> >    gid_t original_gid;
> >    /* If set, the test runs as root instead of the user running the testsuite.  */
> >    int be_su = 0;
> > +  int require_pidns = 0;
> > +  const char *pidns_comment = NULL;
> > +  int do_proc_mounts = 0;

I'm seeing build failures for i686-gnu:

test-container.c: In function 'main':
test-container.c:759:15: error: variable 'pidns_comment' set but not used [-Werror=unused-but-set-variable]
  759 |   const char *pidns_comment = NULL;
      |               ^~~~~~~~~~~~~
cc1: all warnings being treated as errors

https://sourceware.org/pipermail/libc-testresults/2022q2/009529.html

-- 
Joseph S. Myers
joseph@codesourcery.com

  parent reply	other threads:[~2022-04-05 15:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11  3:38 [patch v5] " DJ Delorie
2022-03-28 20:41 ` Carlos O'Donell
2022-03-29  3:53   ` [patch v6] " DJ Delorie
2022-04-04 14:17     ` Carlos O'Donell
2022-04-04 18:34       ` DJ Delorie
2022-04-05 15:57       ` Joseph Myers [this message]
2022-04-05 18:20         ` DJ Delorie
2022-04-11 14:33           ` Florian Weimer

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=alpine.DEB.2.22.394.2204051556090.377353@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=carlos@redhat.com \
    --cc=dj@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).