From: Andrew Morton <akpm@linux-foundation.org>
To: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Cc: hidehiro.kawai.ez@hitachi.com, kosaki.motohiro@jp.fujitsu.com,
linux-kernel@vger.kernel.org, roland@redhat.com,
yumiko.sugita.yf@hitachi.com, satoshi.oshima.fk@hitachi.com
Subject: Re: [PATCH] coredump_filter: enable to change the default filter
Date: Thu, 11 Dec 2008 15:10:03 -0800 [thread overview]
Message-ID: <20081211151003.00572e04.akpm@linux-foundation.org> (raw)
In-Reply-To: <20081211154349.5000.KOSAKI.MOTOHIRO@jp.fujitsu.com>
On Thu, 11 Dec 2008 15:46:49 +0900 (JST)
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com> wrote:
> Hi
>
> > This patch introduces new kernel parameter `coredump_filter'.
> > Setting a value to this parameter causes the default bitmask
> > of coredump_filter to be changed.
> >
> > It is useful for users to change coredump_filter settings for
> > the whole system at boot time. Without this parameter, users
> > have to change coredump_filter settings for each /proc/<pid>/
> > in an initializing script.
>
> I think this patch only useful on following situation, right?
>
> - Administrator can't change rc script.
> - Administrator can change boot parameter.
>
>
> When happen above situation?
> or, you intent to init process debugging?
Yes, this can be implemented in userspace by setting init's filter
before init forks any other processes.
I can understand the practical problems with that form of implementation
however :(
Or does the patch change other behaviour? Say, when mm_init() is
called by a kernel thread (current->mm==NULL)? call_usermodehelper(),
for example?
If so, then setting init's filter doesn't cover that case.
next prev parent reply other threads:[~2008-12-11 23:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 6:33 [PATCH] coredump_filter: enable to change the default filter Hidehiro Kawai
2008-12-11 6:46 ` KOSAKI Motohiro
2008-12-11 23:10 ` Andrew Morton [this message]
2008-12-11 23:22 ` Roland McGrath
2008-12-19 10:05 ` Hidehiro Kawai
2008-12-19 19:53 ` Roland McGrath
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=20081211151003.00572e04.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--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 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.