Date: Sun, 9 Mar 2008 12:05:11 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Roland McGrath <roland@redhat.com>
Cc: Oleg Nesterov <oleg@tv-sign.ru>, Andrew Morton <akpm@linux-foundation.org>,
       Arjan van de Ven <arjan@infradead.org>, linux-kernel@vger.kernel.org
Subject: Re: [RFC, PATCH] signals: print_fatal_signal: fix the signr
	"calculation"
Message-ID: <20080309110511.GA18128@elte.hu>
References: <20080308172453.GA28323@tv-sign.ru> <20080308190311.779B326F990@magilla.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080308190311.779B326F990@magilla.localdomain>
User-Agent: Mutt/1.5.17 (2007-11-01)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 747
Lines: 18


* Roland McGrath <roland@redhat.com> wrote:

> I'm not sure print-fatal-signals was really ever intended for 
> non-coredump signals.  It doesn't seem like it would be all that 
> useful.  It's probably even undesireable for every normal C-c killing 
> something to cause a printk.

correct. We used to have them for SIGKILL but even that was confusing to 
users - so the intent very much is to only have them for truly 
unexpected, non-user generated and 'fatal', coredump-generating signals.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/