From: Roland McGrath <roland@redhat.com>
To: Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
linux-kernel@vger.kernel.org, yumiko.sugita.yf@hitachi.com,
satoshi.oshima.fk@hitachi.com
Subject: Re: [PATCH] coredump_filter: enable to change the default filter
Date: Fri, 19 Dec 2008 11:53:11 -0800 (PST) [thread overview]
Message-ID: <20081219195311.81C4AFC351@magilla.sf.frob.com> (raw)
In-Reply-To: Hidehiro Kawai's message of Friday, 19 December 2008 19:05:10 +0900 <494B71D6.3080602@hitachi.com>
> It makes sense. It also enables us to change coredump_filter for
> user mode helpers after the system was booted.
Right.
> However, we would need a special care for PID namespace if we use
> init's coredump_filter as default. For a process with new PID
> namespace and new /proc, writing to /proc/1/coredump_filter doesn't
> mean changing default, although it's not a usual operation.
I'd figured that private PID namespaces with their own init would want
their own private settings for this default too.
> The reason why I suggested the boot parameter way is most users
> can change the default easily. Some users have difficulty to
> change init scripts for various reasons.
I don't object to it deeply or anything.
I just pointed out that we do already have an alternative.
Thanks,
Roland
next prev parent reply other threads:[~2008-12-19 19:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 6:33 Hidehiro Kawai
2008-12-11 6:46 ` KOSAKI Motohiro
2008-12-11 23:10 ` Andrew Morton
2008-12-11 23:22 ` Roland McGrath
2008-12-19 10:05 ` Hidehiro Kawai
2008-12-19 19:53 ` Roland McGrath [this message]
2008-12-26 6:22 ` Hidehiro Kawai
2008-12-26 6:49 ` KOSAKI Motohiro
2008-12-26 9:45 ` Hidehiro Kawai
2008-12-26 11:46 ` KOSAKI Motohiro
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=20081219195311.81C4AFC351@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=satoshi.oshima.fk@hitachi.com \
--cc=yumiko.sugita.yf@hitachi.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 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®