From: Oleg Nesterov <oleg@redhat.com>
To: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
Cc: ebiederm@xmission.com, roland@redhat.com, bastian@waldi.eu.org,
daniel@hozac.com, xemul@openvz.org, containers@lists.osdl.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH 7/7][v4] SI_TKILL: Masquerade si_pid when crossing pid ns boundary
Date: Wed, 24 Dec 2008 16:55:29 +0100 [thread overview]
Message-ID: <20081224155529.GB11593@redhat.com> (raw)
In-Reply-To: <20081224115331.GG8020@us.ibm.com>
On 12/24, Sukadev Bhattiprolu wrote:
>
> --- a/kernel/signal.c
> +++ b/kernel/signal.c
> @@ -2385,17 +2385,22 @@ static int do_tkill(pid_t tgid, pid_t pid, int sig)
> struct siginfo info;
> struct task_struct *p;
> unsigned long flags;
> + struct pid_namespace *ns;
>
> error = -ESRCH;
> info.si_signo = sig;
> info.si_errno = 0;
> info.si_code = SI_TKILL;
> - info.si_pid = task_tgid_vnr(current);
> info.si_uid = current_uid();
>
> rcu_read_lock();
> p = find_task_by_vpid(pid);
> if (p && (tgid <= 0 || task_tgid_vnr(p) == tgid)) {
> + ns = task_active_pid_ns(p);
> + if (ns)
> + info.si_pid = task_tgid_nr_ns(current, ns);
> + else
> + info.si_pid = task_tgid_vnr(current);
if ns == 0, "p" won't see the signal anyway, so all we need is
- info.si_pid = task_tgid_vnr(current);
+ info.si_pid = task_tgid_nr_ns(current, task_active_ns(p));
like we do in __do_notify().
But. this of course doesn't work for sys_kill(). Can't we change the helpers
which send SI_FROMUSER() signals so that they do not fill .si_pid at all?
Then send_signal() can do:
default:
copy_siginfo(&q->info, info);
info.si_pid = 0;
if (!from_ancestot_ns)
info.si_pid = task_tgid_nr_ns(current, ...);
?
Yes, we use "current". But we already used it in siginfo_from_ancestor_ns().
Oleg.
next prev parent reply other threads:[~2008-12-24 15:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-24 11:44 [PATCH 0/7][v4] Container-init signal semantics Sukadev Bhattiprolu
2008-12-24 11:50 ` [RFC][PATCH 1/7][v4] Remove 'handler' parameter to tracehook functions Sukadev Bhattiprolu
2008-12-24 11:50 ` [RFC][PATCH 2/7][v4] Protect init from unwanted signals more Sukadev Bhattiprolu
2008-12-24 16:35 ` Oleg Nesterov
2008-12-24 21:11 ` Sukadev Bhattiprolu
2008-12-24 11:51 ` [RFC][PATCH 3/7][v4] Define siginfo_from_ancestor_ns() Sukadev Bhattiprolu
2008-12-24 16:28 ` Oleg Nesterov
2008-12-24 21:24 ` Sukadev Bhattiprolu
2008-12-24 22:03 ` Oleg Nesterov
2008-12-27 20:38 ` Sukadev Bhattiprolu
2008-12-24 11:51 ` [RFC][PATCH 4/7][v4] Protect cinit from unblocked SIG_DFL signals Sukadev Bhattiprolu
2008-12-24 11:52 ` [RFC][PATCH 5/7][v4] Protect cinit from blocked fatal signals Sukadev Bhattiprolu
2008-12-24 16:09 ` Oleg Nesterov
2008-12-24 21:25 ` Sukadev Bhattiprolu
2008-12-31 0:04 ` Roland McGrath
2009-01-05 12:24 ` Oleg Nesterov
2008-12-24 11:53 ` [RFC][PATCH 6/7][v4] SI_USER: Masquerade si_pid when crossing pid ns boundary Sukadev Bhattiprolu
2008-12-24 15:43 ` Oleg Nesterov
2008-12-24 16:18 ` Oleg Nesterov
2008-12-24 21:08 ` Sukadev Bhattiprolu
2008-12-24 11:53 ` [RFC][PATCH 7/7][v4] SI_TKILL: " Sukadev Bhattiprolu
2008-12-24 15:55 ` Oleg Nesterov [this message]
2008-12-24 21:04 ` Sukadev Bhattiprolu
2008-12-24 21:34 ` Oleg Nesterov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081224155529.GB11593@redhat.com \
--to=oleg@redhat.com \
--cc=bastian@waldi.eu.org \
--cc=containers@lists.osdl.org \
--cc=daniel@hozac.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=sukadev@linux.vnet.ibm.com \
--cc=xemul@openvz.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox