From: Dongsheng Yang <yangds.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
To: "Eric W. Biederman" <ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Cc: Al Viro <viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>,
containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
LKML <linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Kamezawa Hiroyuki
<kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
Subject: Re: [Propose] Isolate core_pattern in mnt namespace.
Date: Tue, 5 Jan 2016 14:28:46 +0800 [thread overview]
Message-ID: <568B629E.5010806@cn.fujitsu.com> (raw)
In-Reply-To: <8760zpxgte.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
On 12/24/2015 12:36 AM, Eric W. Biederman wrote:
> Dongsheng Yang <yangds.fnst-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org> writes:
[...]
Hi Eric,
Happy new year and sorry for the late reply.
>
> Given the other constraints on an implementation the pid namespace looks
> by far the one best suited to host such a sysctl if it is possible to
> implement safely.
So you think it's better to isolate the core_pattern in pid_namespace,
am I right?
But, core_file_path and user_mode_helper_path in core_pattern are much
more related with mnt_namespace IMO.
Could you help to explain it more?
Thanx
Yang
>
> Eric
>
>
> .
>
next prev parent reply other threads:[~2016-01-05 6:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 11:23 [Propose] Isolate core_pattern in mnt namespace Dongsheng Yang
[not found] ` <56729B3D.1040502-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-12-20 2:14 ` Dongsheng Yang
[not found] ` <56760F05.3020308-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-12-20 2:37 ` Al Viro
[not found] ` <20151220023712.GT20997-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
2015-12-20 2:47 ` Dongsheng Yang
[not found] ` <567616D6.6060202-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-12-20 9:47 ` Eric W. Biederman
[not found] ` <87fuyx1mfn.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2015-12-20 23:58 ` Kamezawa Hiroyuki
2015-12-21 6:15 ` Dongsheng Yang
[not found] ` <567798EC.1040304-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-12-21 21:52 ` Eric W. Biederman
2015-12-22 3:12 ` Kamezawa Hiroyuki
[not found] ` <5678BFA3.9090608-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2015-12-23 3:13 ` Dongsheng Yang
[not found] ` <87twnbzcz8.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2015-12-23 3:12 ` Dongsheng Yang
[not found] ` <567A1120.3070204-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2015-12-23 16:36 ` Eric W. Biederman
[not found] ` <8760zpxgte.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2016-01-05 6:28 ` Dongsheng Yang [this message]
[not found] ` <568B629E.5010806-BthXqXjhjHXQFUHtdCDX3A@public.gmane.org>
2016-01-05 7:58 ` Eric W. Biederman
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=568B629E.5010806@cn.fujitsu.com \
--to=yangds.fnst-bthxqxjhjhxqfuhtdcdx3a@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org \
--cc=kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=viro-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.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;
as well as URLs for NNTP newsgroup(s).