From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 637 invoked by alias); 30 Oct 2014 22:01:18 -0000 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org Received: (qmail 587 invoked by uid 48); 30 Oct 2014 22:01:13 -0000 From: "rickyz at chromium dot org" To: glibc-bugs@sourceware.org Subject: [Bug nptl/17214] Expose a function to reset the PID cache Date: Thu, 30 Oct 2014 22:01:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: nptl X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: rickyz at chromium dot org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-10/txt/msg00130.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=17214 Ricky Zhou changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rickyz at chromium dot org --- Comment #9 from Ricky Zhou --- For what it's worth, we have a similar use case to what Steven mentioned. We would like to spawn new processes in different pid, mount, fs, etc. namespaces, but the clone wrapper requires specifying a new stack even when CLONE_VM is not specified. We cannot unshare(CLONE_NEWPID); fork(); for each new process because Linux does not support calling unshare(CLONE_NEWPID) multiple times. As Steven said, I think either of the following would solve our problems: - Expose a way to invalidate glibc's PID cache - Allow child_stack to be NULL (leading to fork-like behavior) when CLONE_VM is not set. I'd be happy to write up patches for these if there's interest :-) -- You are receiving this mail because: You are on the CC list for the bug.