From: Davide Libenzi <davidel@xmailserver.org>
To: "Zach, Yoav" <yoav.zach@intel.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Yoav Zach <yoav_zach@yahoo.com>, Andrew Morton <akpm@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: RE: force_sig_info
Date: Sun, 5 Sep 2004 06:35:44 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0409050630280.11784@bigblue.dev.mdolabs.com> (raw)
In-Reply-To: <2C83850C013A2540861D03054B478C06048FFA9D@hasmsx403.ger.corp.intel.com>
On Sun, 5 Sep 2004, Zach, Yoav wrote:
> >-----Original Message-----
> >From: Linus Torvalds [mailto:torvalds@osdl.org]
> >Sent: Friday, September 03, 2004 21:12
> >To: Yoav Zach
> >Cc: akpm@osdl.org; linux-kernel@vger.kernel.org; Zach, Yoav
> >Subject: Re: force_sig_info
> >
> >
> >Why are you blocking signals that you want to get? Sounds like
> >a bug in
> >your program.
>
> It's a translator - it emulates the behavior of the translated
> 'process', which is the one that sets the signal mask. On the
> other hand, it has its own logic, which requires handling of
> certain HW exceptions. In 2.4, signals that were raised due to
> HW exceptions could be handled by the translator regardless of
> the mask that was set by the translated process. We lost this
> ability in 2.6. It will be very good for our product, and I
> believe any similar product where a native process emulates
> behavior of another process, if we could have this ability
> back.
Below is the latest patch I posted (applies on some Jun 2004 2.6.x) to
bring 2.6 back to the 2.4 behaviour, but then it has been decided to leave
2.6 as is.
- Davide
--- a/kernel/signal.c 2004-06-28 14:28:51.000000000 -0700
+++ b/kernel/signal.c 2004-06-28 14:29:31.000000000 -0700
@@ -820,8 +820,9 @@
int ret;
spin_lock_irqsave(&t->sighand->siglock, flags);
- if (sigismember(&t->blocked, sig) || t->sighand->action[sig-1].sa.sa_handler == SIG_IGN) {
+ if (t->sighand->action[sig-1].sa.sa_handler == SIG_IGN)
t->sighand->action[sig-1].sa.sa_handler = SIG_DFL;
+ if (sigismember(&t->blocked, sig)) {
sigdelset(&t->blocked, sig);
recalc_sigpending_tsk(t);
}
next prev parent reply other threads:[~2004-09-05 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-05 6:44 force_sig_info Zach, Yoav
2004-09-05 13:35 ` Davide Libenzi [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-03 13:58 force_sig_info Yoav Zach
2004-09-03 18:12 ` force_sig_info Linus Torvalds
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.0409050630280.11784@bigblue.dev.mdolabs.com \
--to=davidel@xmailserver.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
--cc=yoav.zach@intel.com \
--cc=yoav_zach@yahoo.com \
/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®