From: David Woodhouse <dwmw2@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Signals and kernel threads.
Date: Sat, 11 Oct 2003 13:01:05 +0100 [thread overview]
Message-ID: <1065873664.30987.431.camel@imladris.demon.co.uk> (raw)
Once upon a time, kernel threads could make use of signals for receiving
control from userspace. Now, the NPTL code looks at the recipient
thread's userspace handlers for signals, even in the case of a kernel
thread, and if there's not a handler installed will either discard the
signal or convert it to SIGKILL.
Could we disable this behaviour in the case where the recipient is a
kernel thread please? Or at least make allow_signal() set sa_handler to
some non-zero dummy value so that the signal is delivered as intended.
--
dwmw2
reply other threads:[~2003-10-11 12:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1065873664.30987.431.camel@imladris.demon.co.uk \
--to=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®