From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "Kilau, Scott" <Scott_Kilau@digi.com>
Cc: "linux-os (Dick Johnson)" <linux-os@analogic.com>,
Linux Kernel Mail List <linux-kernel@vger.kernel.org>
Subject: RE: [BUG?] 2.6.x (2.6.13) - new signals not being delivered to aterminating (PF_EXITING) process.
Date: Wed, 12 Oct 2005 13:55:30 +0100 [thread overview]
Message-ID: <1129121730.4741.4.camel@localhost.localdomain> (raw)
In-Reply-To: <335DD0B75189FB428E5C32680089FB9F36B12E@mtk-sms-mail01.digi.com>
> Do you know if there was any particular reason why it was changed that
> signals can't be delivered to an exiting process in 2.6?
> Was there maybe some sort of race, and this was the best way to resolve
> it?
I have no idea. It may be a change due to the threaded signal support.
Ask whoever hacked up the signal code last I guess.
prev parent reply other threads:[~2005-10-12 12:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-12 0:44 Kilau, Scott
2005-10-12 12:55 ` Alan Cox [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=1129121730.4741.4.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=Scott_Kilau@digi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.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
Powered by JetHome