* [PATCH] SIGURG incorrectly delivered to process
@ 2002-04-18 5:52 Christopher Yeoh
2002-04-23 20:53 ` Marcelo Tosatti
2002-04-25 18:59 ` David Mosberger
0 siblings, 2 replies; 3+ messages in thread
From: Christopher Yeoh @ 2002-04-18 5:52 UTC (permalink / raw)
To: Linus Torvalds, Marcelo Tosatti; +Cc: linux-kernel, anton, paulus, davidm
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.
Chris
--
cyeoh@au.ibm.com
IBM OzLabs Linux Development Group
Canberra, Australia
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [PATCH] SIGURG incorrectly delivered to process
2002-04-18 5:52 [PATCH] SIGURG incorrectly delivered to process Christopher Yeoh
@ 2002-04-23 20:53 ` Marcelo Tosatti
2002-04-25 18:59 ` David Mosberger
1 sibling, 0 replies; 3+ messages in thread
From: Marcelo Tosatti @ 2002-04-23 20:53 UTC (permalink / raw)
To: Christopher Yeoh; +Cc: Linus Torvalds, linux-kernel, anton, paulus, davidm
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 ?
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [PATCH] SIGURG incorrectly delivered to process
2002-04-18 5:52 [PATCH] SIGURG incorrectly delivered to process Christopher Yeoh
2002-04-23 20:53 ` Marcelo Tosatti
@ 2002-04-25 18:59 ` David Mosberger
1 sibling, 0 replies; 3+ messages in thread
From: David Mosberger @ 2002-04-25 18:59 UTC (permalink / raw)
To: Christopher Yeoh
Cc: Linus Torvalds, Marcelo Tosatti, linux-kernel, anton, paulus
>>>>> On Thu, 18 Apr 2002 15:52:32 +1000, Christopher Yeoh <cyeoh@samba.org> said:
Christopher> If a process is sent a SIGURG signal and it is blocking
Christopher> SIGURG signals, when the process subsequently unblocks
Christopher> SIGURG signals it will be terminated even if it is set
Christopher> to the default action (SIG_DFL) which is specified by
Christopher> SUSv3 to ignore that signal.
Looks like a correct fix to me. I made this change to the ia64 tree.
Thanks,
--david
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2002-04-25 18:59 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-04-18 5:52 [PATCH] SIGURG incorrectly delivered to process Christopher Yeoh
2002-04-23 20:53 ` Marcelo Tosatti
2002-04-25 18:59 ` David Mosberger
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®