Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265255AbUF1WIe (ORCPT ); Mon, 28 Jun 2004 18:08:34 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262085AbUF1WIe (ORCPT ); Mon, 28 Jun 2004 18:08:34 -0400 Received: from fw.osdl.org ([65.172.181.6]:32425 "EHLO mail.osdl.org") by vger.kernel.org with ESMTP id S265255AbUF1WI2 (ORCPT ); Mon, 28 Jun 2004 18:08:28 -0400 Date: Mon, 28 Jun 2004 15:08:24 -0700 (PDT) From: Linus Torvalds To: Davide Libenzi cc: Andrew Morton , Linux Kernel Mailing List Subject: Re: [patch] signal handler defaulting fix ... In-Reply-To: Message-ID: References: <20040628144003.40c151ff.akpm@osdl.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 832 Lines: 22 On Mon, 28 Jun 2004, Davide Libenzi wrote: > > It's not that the program try to block the signal. It's the kernel that > during the delivery disables the signal. Then when the signal handler > longjmp(), the signal remains disabled. The next time the signal is raised > again, the kernel does not honor the existing handler, but it reset to > SIG_DFL. So? That program is buggy. Setting the signal handler to SIG_DFL causes it to be killed with a nice "killed by SIGFPE" message, and now the bug is visible, and can be fixed. Hint: it should have done a siglongjmp(). Linus - 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/