public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rickyz at chromium dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug nptl/15392] Linux, setns, PID namespaces, fork: assert() about pid inequality hit sporadically
Date: Fri, 14 Nov 2014 22:58:00 -0000	[thread overview]
Message-ID: <bug-15392-131-638c52PftC@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15392-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=15392

Ricky Zhou <rickyz at chromium dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rickyz at chromium dot org

--- Comment #2 from Ricky Zhou <rickyz at chromium dot org> ---
Created attachment 7938
  --> https://sourceware.org/bugzilla/attachment.cgi?id=7938&action=edit
Double unshare CLONE_NEWPID example

I've run into this assertion as well. I've attached a small test program that
trips it using unshare(CLONE_NEWPID). In this case, the issue is that the
parent process has pid 1 inside its pid namespace, but since the child is
created in a new pid namespace, it also has pid 1.

Will try to send a patch to get rid of the assert.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-11-14 22:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-23 18:16 [Bug nptl/15392] New: " christian at iwakd dot de
2013-04-23 18:58 ` [Bug nptl/15392] " schwab@linux-m68k.org
2014-06-13 18:18 ` fweimer at redhat dot com
2014-11-14 22:58 ` rickyz at chromium dot org [this message]
2014-11-17 10:38 ` triegel at redhat dot com
2014-12-17 23:51 ` jld at mozilla dot com

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=bug-15392-131-638c52PftC@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).