From: Steve G <linux_4ever@yahoo.com>
To: Davide Libenzi <davidel@xmailserver.org>,
Andries Brouwer <aebr@win.tue.nl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.x signal handler bug
Date: Sun, 27 Jun 2004 19:01:08 -0700 (PDT) [thread overview]
Message-ID: <20040628020108.85755.qmail@web50609.mail.yahoo.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0406271551000.19865@bigblue.dev.mdolabs.com>
> > So, maybe the restoring to SIG_DFL was not required, but it doesn't seem
> > incorrect either. It may be a bit surprising.
Right. Thanks for looking deeper Andries. I understood Davide's explanation and
then immediately wondered why the program worked under 2.4. I want to think 2.4
was emulating the unreliable signal from the past when signal() was used.
My main concern is that the behavior change may have broken some applications
that used to work. For example, valgrind caught & reported a problem under 2.4,
but valgrind never had a chance to catch it under 2.6.
> I think so. Maybe the attached patch?
I've applied the second patch to my kernel & started recompiling. I'll re-test it
tomrrow.
Thanks,
-Steve Grubb
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
next prev parent reply other threads:[~2004-06-28 2:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-26 14:33 2.6.x signal handler bug Steve G
2004-06-26 16:05 ` Davide Libenzi
2004-06-27 22:16 ` Andries Brouwer
2004-06-27 22:45 ` Davide Libenzi
2004-06-27 22:51 ` Davide Libenzi
2004-06-28 2:01 ` Steve G [this message]
2004-06-28 11:26 ` Steve G
2004-06-28 14:56 ` Davide Libenzi
-- strict thread matches above, loose matches on Subject: below --
2004-06-25 23:56 Paul Maurides
2004-06-26 0:07 ` Andrew Morton
2004-06-26 1:33 ` David Wagner
2004-06-28 21:56 ` Jörn Engel
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=20040628020108.85755.qmail@web50609.mail.yahoo.com \
--to=linux_4ever@yahoo.com \
--cc=aebr@win.tue.nl \
--cc=davidel@xmailserver.org \
--cc=linux-kernel@vger.kernel.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.