From: ebiederm@xmission.com (Eric W. Biederman)
To: "Kir Kolyshkin" <kir@openvz.org>
Cc: <akpm@linux-foundation.org>, <linux-kernel@vger.kernel.org>,
<oleg@tv-sign.ru>, <torvalds@linux-foundation.org>,
<containers@linux-foundation.org>
Subject: Re: [Devel] [PATCH] pidns: Limit kill -1 and cap_set_all
Date: Fri, 26 Oct 2007 16:10:04 -0600 [thread overview]
Message-ID: <m1myu5y1c3.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <CBC546DD07068244AEC110EFEDA58B72358940@excite.int.sw-soft.com> (Kir Kolyshkin's message of "Fri, 26 Oct 2007 17:06:54 -0400")
"Kir Kolyshkin" <kir@swsoft.com> writes:
> Eric, this problem is a known one. Currently Pavel and Sukadev are working on a
> appropriate signal management for namespaces.
I'm fairly certain that the signal issue you they are dealing with
is how to keep children from killing the init of a pid namespace.
At least that is what Suka mentioned when I asked him earlier,
and that is the discussion I have at various times on the containers
list.
This is a totally different issue. This is keeping
kill -1 in a child pid namespace from sending a signal to
every process in the system.
It is a bad bug and this patch is a complete fix for it.
To my knowledge Pavel and Suka just overlooked this case.
> If you'd first sent this patch for discussion/review to containers@, you'd know
> that the patch is very incomplete.
I explicitly asked Suka, Pavel, and Cedric how complete they thought
the pid namespace was before I started sending patches. With
Pavel at a conference it makes sense why he did not reply.
For the most part Suka and Cedric did not know about the issues
that I have been finding and fixing.
So since several of them have been fixable with trivial simple fixes
and because we have passed -rc1 and it is now time for bug fixes
and possibly a few cleanups. I have been making bug fixes.
Kir I am happy from feedback from people who can understand the code
and patches. But I am not going to hold up sending simple obviously
correct fixes for discussion.
Eric
parent reply other threads:[~2007-10-26 22:10 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CBC546DD07068244AEC110EFEDA58B72358940@excite.int.sw-soft.com>]
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=m1myu5y1c3.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=containers@linux-foundation.org \
--cc=kir@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@tv-sign.ru \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®