Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 23 Apr 2002 17:55:35 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 23 Apr 2002 17:55:34 -0400 Received: from perninha.conectiva.com.br ([200.250.58.156]:30730 "HELO perninha.conectiva.com.br") by vger.kernel.org with SMTP id ; Tue, 23 Apr 2002 17:55:30 -0400 Date: Tue, 23 Apr 2002 17:53:48 -0300 (BRT) From: Marcelo Tosatti To: Christopher Yeoh Cc: Linus Torvalds , linux-kernel@vger.kernel.org, anton@samba.org, paulus@samba.org, davidm@hpl.hp.com Subject: Re: [PATCH] SIGURG incorrectly delivered to process In-Reply-To: <15550.24352.446276.774799@gargle.gargle.HOWL> Message-ID: 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 On Thu, 18 Apr 2002, Christopher Yeoh wrote: > > If a process is sent a SIGURG signal and it is blocking SIGURG > signals, when the process subsequently unblocks SIGURG signals it will > be terminated even if it is set to the default action (SIG_DFL) which > is specified by SUSv3 to ignore that signal. > > The following patch fixes the problem: > > --- linux-2.4.18/arch/i386/kernel/signal.c~ Thu Mar 21 16:04:30 2002 > +++ linux-2.4.18/arch/i386/kernel/signal.c Thu Apr 18 12:19:37 2002 > @@ -658,7 +658,7 @@ > continue; > > switch (signr) { > - case SIGCONT: case SIGCHLD: case SIGWINCH: > + case SIGCONT: case SIGCHLD: case SIGWINCH: case SIGURG: > continue; > > case SIGTSTP: case SIGTTIN: case SIGTTOU: > > A quick browse of the other architectures indicates that most (if not > all) of them also need the same fix applied to their arch specific > signal.c files. Christopher, Could you please fixup (and test ;)) and other archs too ? - 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/