This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
Re: [PATCH v4] [RFC] tracepoint: Add signal coredump tracepoint
- From: KOSAKI Motohiro <kosaki dot motohiro at jp dot fujitsu dot com>
- To: Masami Hiramatsu <mhiramat at redhat dot com>
- Cc: kosaki dot motohiro at jp dot fujitsu dot com, Ingo Molnar <mingo at elte dot hu>, Andrew Morton<akpm at linux-foundation dot org>, lkml<linux-kernel at vger dot kernel dot org>, systemtap<systemtap at sources dot redhat dot com>, DLE<dle-develop at lists dot sourceforge dot net>, Oleg Nesterov <oleg at redhat dot com>, Roland McGrath <roland at redhat dot com>, Jason Baron <jbaron at redhat dot com>
- Date: Thu, 10 Dec 2009 09:09:31 +0900 (JST)
- Subject: Re: [PATCH v4] [RFC] tracepoint: Add signal coredump tracepoint
- References: <4B1FCD74.8020302@redhat.com> <20091209203835.12767.42778.stgit@dhcp-100-2-132.bos.redhat.com>
> Add signal coredump tracepoint which shows signal number,
> mm->flags, core file size limitation, the result of
> coredump, and core file name.
>
> This tracepoint requirement comes mainly from the viewpoint of
> administrators. Since now we have introduced many coredump
> configurations (e.g. dumpable, coredump_filter, core_pattern,
> etc) and some of them can be modified by users, it will be hard
> to know what was actually dumped (or not dumped) after some
> problem happened on the system. For example, a process didn't
> generated core, coredump doesn't have some sections, etc.
> In those cases, the coredump tracepoint can help us to know
> why the core file is so big or small, or not generated, by
> recording all configurations for all processes on the system.
> That will reduce system-administration cost.
>
> Changes in v4:
> - Rename limit trace-argument to core_size_limit, because
> of user friendly output.
Looks good to me.