From: ebiederm@xmission.com (Eric W. Biederman)
To: sukadev@us.ibm.com
Cc: Daniel Hokka Zakrisson <daniel@hozac.com>,
linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org, xemul@openvz.org,
oleg@tv-sign.ru, akpm@linux-foundation.org,
ebiederm@xmission.com
Subject: Re: [PATCH 1/2] signals: kill(-1) should only signal processes in the same namespace
Date: Thu, 17 Jul 2008 11:46:23 -0700 [thread overview]
Message-ID: <m1mykgtklc.fsf@frodo.ebiederm.org> (raw)
In-Reply-To: <20080717181313.GA2289@us.ibm.com> (sukadev@us.ibm.com's message of "Thu, 17 Jul 2008 11:13:13 -0700")
sukadev@us.ibm.com writes:
>
> Like Pavel said, we had couple of attempts to fix the larger problem of
> signal semantics in containers but did not have a consensus on handling
> blocked/unhandled signals to container-init.
Oh. I thought we were pretty close then I or somebody ran out of steam.
> It would still be good to fix this "kill -1" problem.
>
> Eric had a slightly optimized interface, 'pid_in_pid_ns()' in following
> patchset. Maybe we could use that ?
>
> https://lists.linux-foundation.org/pipermail/containers/2007-December/009174.html
Eric
next prev parent reply other threads:[~2008-07-17 18:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 14:55 [PATCH 1/2] signals: kill(-1) should only signal processes in the same namespace Daniel Hokka Zakrisson
2008-07-17 15:01 ` Pavel Emelyanov
2008-07-17 15:24 ` Daniel Hokka Zakrisson
2008-07-17 15:54 ` Pavel Emelyanov
2008-07-17 17:32 ` Oleg Nesterov
2008-07-17 17:50 ` Eric W. Biederman
2008-07-17 17:45 ` Eric W. Biederman
2008-07-17 18:39 ` Daniel Hokka Zakrisson
2008-07-17 18:45 ` Eric W. Biederman
2008-07-17 18:13 ` sukadev
2008-07-17 18:44 ` Daniel Hokka Zakrisson
2008-07-17 18:46 ` Eric W. Biederman [this message]
2008-07-23 14:34 ` Oleg Nesterov
2008-07-23 16:09 ` Daniel Hokka Zakrisson
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=m1mykgtklc.fsf@frodo.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=containers@lists.linux-foundation.org \
--cc=daniel@hozac.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=sukadev@us.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