[Bug nptl/17214] Expose a function to reset the PID cache

[rickyz at chromium dot org]

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

Ricky Zhou <rickyz at chromium dot org> changed:

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

--- Comment #9 from Ricky Zhou <rickyz at chromium dot org> ---
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.