Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265727AbUF2MCv (ORCPT ); Tue, 29 Jun 2004 08:02:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265729AbUF2MCv (ORCPT ); Tue, 29 Jun 2004 08:02:51 -0400 Received: from mail.fh-wedel.de ([213.39.232.194]:24200 "EHLO mail.fh-wedel.de") by vger.kernel.org with ESMTP id S265727AbUF2MCt (ORCPT ); Tue, 29 Jun 2004 08:02:49 -0400 Date: Tue, 29 Jun 2004 14:02:01 +0200 From: =?iso-8859-1?Q?J=F6rn?= Engel To: Edgar Toernig Cc: Linus Torvalds , Davide Libenzi , Andrew Morton , Linux Kernel Mailing List Subject: Re: [patch] signal handler defaulting fix ... Message-ID: <20040629120201.GA24075@wohnheim.fh-wedel.de> References: <20040628144003.40c151ff.akpm@osdl.org> <20040629032441.403163dd.froese@gmx.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20040629032441.403163dd.froese@gmx.de> User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1122 Lines: 29 On Tue, 29 June 2004 03:24:41 +0200, Edgar Toernig wrote: > Linus Torvalds wrote: > > > > So? That program is buggy. > > Not the signal part. It was written for libc5. There, signals set > with signal(2) were reset when raised (SysV-style). Leaving such a > signal handler with longjmp was perfectly valid. But has a very distinct problem. A segmentation fault is usually a bug and deserves a core dump. Sane default behaviour. If the program tells the kernel, it can handle segmentation faults on it's own, fine. But if - while handling the fault - it creates a second one, the claim was obviously false. Coredump, done. Now, how can the kernel tell, whether a second segmentation fault happened inside the handler or after successfully handling the first one? Right, with longjmp it can't. Coredump, done. J?rn -- Victory in war is not repetitious. -- Sun Tzu - 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/