[RFC PATCH 3/5] use next syscall data to predefine process ids

Eric W. Biederman ebiederm at xmission.com
Wed Jul 9 17:27:09 PDT 2008

Nadia.Derbey at bull.net writes:

> [PATCH 03/05]
> This patch uses the value written into the next_syscall_data proc file
> as a target upid nr for the next process to be created.
> The following syscalls have a new behavior if next_syscall_data is set:
> . fork()
> . vfork()
> . clone()
> In the current version, if the process belongs to nested namespaces, only
> the upper namespace level upid nr is allowed to be predefined, since there
> is not yet a way to take a snapshot of upid nrs at all namespaces levels.
> But this can easily be extended in the future.

This patch is unnecessary.  The and a mess.   The existing limits on the pid range should
be enough.  We may need to export it via /proc/sys.


More information about the Containers mailing list