Re: [v12][PATCH 8/9] Define eclone() syscall

["Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>]

Quoting Sukadev Bhattiprolu (sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org):
> (Trimmed Cc to Containers list).
> 
> Updated patch to ignore ->child_stack_size on architectures that don't
> need it.

I'm trying to figure out if this is somehow my fault on my s390x system,
though it seems like something that would've resulted from the conversion
to using last/nr/max args to specify the pid as Eric suggested.  But
if I pick a pid that is already in use, I get a massive set of oopses
from free_pid.  Though the oops imply it's free_pid() called as a result
of wait4 on the cloned task.

So, do you get errors on x86 when you try to eclone() a process with a
pid that is in use?  i.e.
	# nsexecwp -z 999 /bin/bash
		# id $$
			9999
		# nsexeccwp -z 999 /bin/bash
		(oops)

-serge