From: Davide Libenzi <davidel@xmailserver.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch] signal handler defaulting fix ...
Date: Mon, 28 Jun 2004 15:13:50 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0406281509100.18879@bigblue.dev.mdolabs.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0406281507090.28764@ppc970.osdl.org>
On Mon, 28 Jun 2004, Linus Torvalds wrote:
> 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().
That's what I posted him. Three examples on how to make the thing work
w/out kernel fixes. Then Andries investigated about POSIX compliancy and
noticed that basically it is undefined the behaviour a program will get.
Let's leave as is then.
- Davide
next prev parent reply other threads:[~2004-06-28 22:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-28 21:34 Davide Libenzi
2004-06-28 21:40 ` Andrew Morton
2004-06-28 21:49 ` Linus Torvalds
2004-06-28 21:55 ` Davide Libenzi
2004-06-28 22:08 ` Linus Torvalds
2004-06-28 22:13 ` Davide Libenzi [this message]
2004-06-29 1:24 ` Edgar Toernig
2004-06-29 12:02 ` Jörn Engel
2004-06-28 21:49 ` Jörn Engel
[not found] <2cfBL-6uJ-9@gated-at.bofh.it>
2004-07-03 13:54 ` Kai Henningsen
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=Pine.LNX.4.58.0406281509100.18879@bigblue.dev.mdolabs.com \
--to=davidel@xmailserver.org \
--cc=akpm@osdl.org \
--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 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®