From: ebiederm@xmission.com (Eric W. Biederman)
To: Neil Horman <nhorman@tuxdriver.com>
Cc: Oleg Nesterov <oleg@redhat.com>,
Pavel Emelyanov <xemul@parallels.com>,
Daniel Berrange <berrange@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Serge Hallyn <serge.hallyn@canonical.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: + core_pattern-set-core-helpers-root-and-namespace-to-crashing-process .patch added to -mm tree
Date: Tue, 18 Dec 2012 20:43:37 -0800 [thread overview]
Message-ID: <87obhq1wjq.fsf@xmission.com> (raw)
In-Reply-To: <20121218215316.GA4329@neilslaptop.think-freely.org> (Neil Horman's message of "Tue, 18 Dec 2012 16:53:16 -0500")
Neil Horman <nhorman@tuxdriver.com> writes:
> On Tue, Dec 18, 2012 at 12:45:18PM -0800, Eric W. Biederman wrote:
>> The code for setns to change the pid namespace just merged.
>>
> Can you post a link to the merge commit for reference so I can take a look at
> it?
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=6a2b60b17b3e48a418695a94bd2420f6ab32e519
>> If we just want one pattern we should be able to to robustly implement
>> this in userspace with the existing functionality. With the caveat that
>> we need to get some pid namespace and user namespace bugs in the core
>> pattern generation fixed. But we need to fix those bugs anyway.
>>
> Then perhaps the right thing to do here is in fact just make core_pattern a
> per-namespace sysctl. I only took a brief look, but I was unable to find an
> example of such a per-namespace systctl. Do we already have the infrastructure
> to do such a thing? I didn't think we did.
We do have the infrastructure for a per namespace sysctls. Right now we
only have per network namespace sysctls. It is on my wish list to use
the infrastructure a little more extensively and convert /proc/sys into
a symlink to /proc/<pid>/sys and reduce the amount of magic in /proc for
sysctls.
We also have per namespace sysctls that do magic based upon current.
Since that pattern is has more magic I don't recommend it over the long
term.
Of course there is the question which namespace the sysctl should be
tied to, and what the other namespaces should be set to. Shrug.
Eric
next prev parent reply other threads:[~2012-12-19 4:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 12:34 + core_pattern-set-core-helpers-root-and-namespace-to-crashing-process .patch added to -mm tree Oleg Nesterov
2012-12-17 15:05 ` Neil Horman
2012-12-17 16:04 ` Oleg Nesterov
2012-12-17 18:39 ` Neil Horman
2012-12-18 20:06 ` Oleg Nesterov
2012-12-18 20:19 ` Neil Horman
2012-12-18 20:45 ` Eric W. Biederman
2012-12-18 21:53 ` Neil Horman
2012-12-19 4:43 ` Eric W. Biederman [this message]
2012-12-19 16:34 ` Oleg Nesterov
2012-12-19 16:22 ` Oleg Nesterov
2012-12-19 20:42 ` Neil Horman
2012-12-20 13:02 ` 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=87obhq1wjq.fsf@xmission.com \
--to=ebiederm@xmission.com \
--cc=akpm@linux-foundation.org \
--cc=berrange@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=oleg@redhat.com \
--cc=serge.hallyn@canonical.com \
--cc=viro@zeniv.linux.org.uk \
--cc=xemul@parallels.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.