From: Roland McGrath <roland@redhat.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Ingo Molnar <mingo@redhat.com>, <linux-kernel@vger.kernel.org>
Subject: Re: another subtle signals issue
Date: Wed, 12 Feb 2003 14:04:27 -0800 [thread overview]
Message-ID: <200302122204.h1CM4RZ24628@magilla.sf.frob.com> (raw)
In-Reply-To: Linus Torvalds's message of Wednesday, 12 February 2003 13:42:58 -0800 <Pine.LNX.4.44.0302121341270.1096-100000@penguin.transmeta.com>
> Hmm.. We could move the blocking test down, and only consider that for the
> "SIG_DFL" case.
That is the same resultant behavior as my last patch, though your patch
changed only as you've just described would leave the signal in the queue
though not wake anyone. That differs in practice only if someone calls
recalc_sigpending_tsk on some blocked threads for some reason.
> The function I did matches what the old signal code did, but the more
> signals we can truly ignore, the better. I dunno.
Once modified to work in the MT case the same as in the no-thread-groups case,
either way is fine by the spec and by me. Your call.
prev parent reply other threads:[~2003-02-12 21:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0302111356550.1405-100000@penguin.transmeta.com>
2003-02-12 2:06 ` Roland McGrath
2003-02-12 2:45 ` Linus Torvalds
2003-02-12 3:05 ` Daniel Jacobowitz
2003-02-12 3:10 ` Linus Torvalds
2003-02-12 3:23 ` Roland McGrath
2003-02-12 3:38 ` Linus Torvalds
2003-02-12 3:13 ` Roland McGrath
2003-02-12 3:18 ` Linus Torvalds
2003-02-12 3:50 ` Roland McGrath
2003-02-12 4:21 ` Linus Torvalds
2003-02-12 20:12 ` Linus Torvalds
2003-02-12 21:11 ` Roland McGrath
2003-02-12 21:19 ` Linus Torvalds
2003-02-12 21:58 ` Roland McGrath
2003-02-12 21:42 ` Linus Torvalds
2003-02-12 22:04 ` Roland McGrath [this message]
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=200302122204.h1CM4RZ24628@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=torvalds@transmeta.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®