public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dongsheng Yang <yangds.fnst@cn.fujitsu.com>
To: <containers@lists.linux-foundation.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Cc: LKML <linux-kernel@vger.kernel.org>, <cgroups@vger.kernel.org>
Subject: Re: [Propose] Isolate core_pattern in mnt namespace.
Date: Sun, 20 Dec 2015 10:14:29 +0800	[thread overview]
Message-ID: <56760F05.3020308@cn.fujitsu.com> (raw)
In-Reply-To: <56729B3D.1040502@cn.fujitsu.com>

On 12/17/2015 07:23 PM, Dongsheng Yang wrote:
> Hi guys,
>      We are working on making core dump behaviour isolated in
> container. But the problem is, the /proc/sys/kernel/core_pattern
> is a kernel wide setting, not belongs to a container.
>
>      So we want to add core_pattern into mnt namespace. What
> do you think about it?

Hi Eric,
	I found your patch about "net: Implement the per network namespace 
sysctl infrastructure", I want to do the similar thing
in mnt namespace. Is that suggested way?

Thanx
Yang
>
> Yang
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe cgroups" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>




  reply	other threads:[~2015-12-20  2:22 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
2015-12-20  2:14 ` Dongsheng Yang [this message]
2015-12-20  2:37   ` Al Viro
2015-12-20  2:47     ` Dongsheng Yang
2015-12-20  9:47       ` Eric W. Biederman
2015-12-20 23:58         ` Kamezawa Hiroyuki
2015-12-21  6:15         ` Dongsheng Yang
2015-12-21 21:52           ` Eric W. Biederman
2015-12-22  3:12             ` Kamezawa Hiroyuki
2015-12-23  3:13               ` Dongsheng Yang
2015-12-23  3:12             ` Dongsheng Yang
2015-12-23 16:36               ` Eric W. Biederman
2016-01-05  6:28                 ` Dongsheng Yang
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=56760F05.3020308@cn.fujitsu.com \
    --to=yangds.fnst@cn.fujitsu.com \
    --cc=cgroups@vger.kernel.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.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