From: Albert Cahalan <albert@users.sf.net>
To: linux-kernel mailing list <linux-kernel@vger.kernel.org>
Cc: bruce@perens.com, Linus Torvalds <torvalds@osdl.org>
Subject: Re: Never mind. Re: Signal left blocked after signal handler.
Date: 26 Nov 2003 16:53:00 -0500 [thread overview]
Message-ID: <1069883580.723.416.camel@cube> (raw)
> One difference in 2.4.x and 2.6.x is the signal blocking
> wrt blocked signals that are _forced_ (ie anything that
> is thread-synchronous, like a SIGSEGV/SIGTRAP/SIGBUS that
> happens as a result of a fault):
>
> - in 2.4.x they will just punch through the block
> - in 2.6.x they will refuse to punch through a blocked
> signal, but since they can't be delivered they will
> cause the process to be killed.
...
> and in 2.4.x this will cause infinte SIGSEGV's (well,
> they'll be caught by the stack size eventually, but you
> see the problem: do a "strace" to see what's going on).
> In 2.6.x the second SIGSEGV will just kill the program
> immediately.
How about making the process sleep in a killable state?
This is as if the blocking was obeyed, but doesn't
burn CPU time. Only a debugger should be able to
tell the difference.
next reply other threads:[~2003-11-26 22:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 21:53 Albert Cahalan [this message]
2003-11-27 9:11 ` Never mind. Re: Signal left blocked after signal handler Ingo Oeser
2003-11-27 15:45 ` Albert Cahalan
2003-11-27 17:26 ` Jörn Engel
-- strict thread matches above, loose matches on Subject: below --
2003-11-26 17:39 Bruce Perens
2003-11-26 17:55 ` Linus Torvalds
[not found] ` <3FC4ED5F.4090901@perens.com>
[not found] ` <3FC4EF24.9040307@perens.com>
[not found] ` <3FC4F248.8060307@perens.com>
2003-11-26 18:45 ` Never mind. " Linus Torvalds
2003-11-26 19:04 ` Bruce Perens
2003-11-26 19:14 ` Linus Torvalds
2003-11-26 19:52 ` Jamie Lokier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1069883580.723.416.camel@cube \
--to=albert@users.sf.net \
--cc=bruce@perens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.