Re: [PATCH] Introduce ActivePid: in /proc/self/status (v2, wasVpid:)

From: Oleg Nesterov
Date: Thu Jun 16 2011 - 09:09:41 EST

On 06/16, Cedric Le Goater wrote:
> We have a case where a task in a parent pid namespace needs to kill
> another task in a sub pid namespace only knowing its internal pid.
> the latter has been communicated to the parent task through a file or
> a unix socket.

OK, thanks, this partly answers my question... But if they communicate
anyway, it is not clear why the signal is needed.

> This 'ActivePid' information in /proc is not sufficient to identity
> the task, you also need the list of the tasks which are living in
> the pid namespace.

Yes, I see.

> a new kill syscall could be the solution:
> int pidns_kill(pid_t init_pid, pid_t some_pid);
> where 'init_pid' identifies the namespace and 'some_pid' identifies
> a task in this namespace. this is very specific but why not.

Yes, I also thought about this. Should be trivial.

Or int sys_tell_me_its_pid(pid_t init_pid, pid_t some_pid).

Just in case.... This is hack, yes, but in fact you do not need the
kernel changes to send a signal inside the namespace. You could
ptrace sub_init, and execute the necessary code "inside" the namespace.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at