From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29294 invoked by alias); 10 Dec 2009 00:09:40 -0000 Received: (qmail 29287 invoked by uid 22791); 10 Dec 2009 00:09:39 -0000 X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,SPF_PASS X-Spam-Check-By: sourceware.org Received: from fgwmail5.fujitsu.co.jp (HELO fgwmail5.fujitsu.co.jp) (192.51.44.35) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 10 Dec 2009 00:09:35 +0000 Received: from m1.gw.fujitsu.co.jp ([10.0.50.71]) by fgwmail5.fujitsu.co.jp (Fujitsu Gateway) with ESMTP id nBA09WHI031821 for (envelope-from kosaki.motohiro@jp.fujitsu.com); Thu, 10 Dec 2009 09:09:32 +0900 Received: from smail (m1 [127.0.0.1]) by outgoing.m1.gw.fujitsu.co.jp (Postfix) with ESMTP id 846EA45DE55 for ; Thu, 10 Dec 2009 09:09:32 +0900 (JST) Received: from s1.gw.fujitsu.co.jp (s1.gw.fujitsu.co.jp [10.0.50.91]) by m1.gw.fujitsu.co.jp (Postfix) with ESMTP id 5DBC845DE54 for ; Thu, 10 Dec 2009 09:09:32 +0900 (JST) Received: from s1.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s1.gw.fujitsu.co.jp (Postfix) with ESMTP id 36BF31DB8040 for ; Thu, 10 Dec 2009 09:09:32 +0900 (JST) Received: from ml13.s.css.fujitsu.com (ml13.s.css.fujitsu.com [10.249.87.103]) by s1.gw.fujitsu.co.jp (Postfix) with ESMTP id D61B51DB803C for ; Thu, 10 Dec 2009 09:09:31 +0900 (JST) Received: from ml13.css.fujitsu.com (ml13 [127.0.0.1]) by ml13.s.css.fujitsu.com (Postfix) with ESMTP id A10BBFD0009; Thu, 10 Dec 2009 09:09:31 +0900 (JST) Received: from [127.0.0.1] (unknown [10.124.100.179]) by ml13.s.css.fujitsu.com (Postfix) with ESMTP id 33F53FD0015; Thu, 10 Dec 2009 09:09:31 +0900 (JST) X-SecurityPolicyCheck-FJ: OK by FujitsuOutboundMailChecker v1.3.1 Received: from KOSANOTE2[10.124.100.179] by KOSANOTE2 (FujitsuOutboundMailChecker v1.3.1/9992[10.124.100.179]); Thu, 10 Dec 2009 09:09:36 +0900 (JST) From: KOSAKI Motohiro To: Masami Hiramatsu Subject: Re: [PATCH v4] [RFC] tracepoint: Add signal coredump tracepoint Cc: kosaki.motohiro@jp.fujitsu.com, Ingo Molnar , Andrew Morton, lkml, systemtap, DLE, Oleg Nesterov , Roland McGrath , Jason Baron In-Reply-To: <20091209203835.12767.42778.stgit@dhcp-100-2-132.bos.redhat.com> References: <4B1FCD74.8020302@redhat.com> <20091209203835.12767.42778.stgit@dhcp-100-2-132.bos.redhat.com> Message-Id: <20091210090852.F4F1.A69D9226@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit Date: Thu, 10 Dec 2009 00:09:00 -0000 Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2009-q4/txt/msg00874.txt.bz2 > 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.