Currently we have a few instances where we are generating signals setting si_code to SI_USER and si_pid to the task id. However in the case of SI_USER we are using a posix defined interface, and posix defines si_pid as the sending process id. Which in linux is equivalent to the task group id. So fix SI_USER to fill in the proper si_pid value. Signed-off-by: Eric W. Biederman <ebiederm@xxxxxxxxxxxx> --- kernel/signal.c | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/kernel/signal.c b/kernel/signal.c index 280bccb..694a643 100644 --- a/kernel/signal.c +++ b/kernel/signal.c @@ -694,7 +694,7 @@ static int send_signal(int sig, struct siginfo *info, struct task_struct *t, q->info.si_signo = sig; q->info.si_errno = 0; q->info.si_code = SI_USER; - q->info.si_pid = task_pid_vnr(current); + q->info.si_pid = task_tgid_vnr(current); q->info.si_uid = current->uid; break; case (unsigned long) SEND_SIG_PRIV: @@ -1794,7 +1794,7 @@ relock: info->si_signo = signr; info->si_errno = 0; info->si_code = SI_USER; - info->si_pid = task_pid_vnr(current->parent); + info->si_pid = task_tgid_vnr(current->parent); info->si_uid = current->parent->uid; } -- 1.5.3.rc6.17.g1911 _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers