From: Oleg Nesterov <oleg@tv-sign.ru>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Roland McGrath <roland@redhat.com>,
Petr Tesarik <ptesarik@suse.cz>, Tony Luck <tony.luck@intel.com>,
Matthew Wilcox <willy@debian.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arch_ptrace_stop
Date: Thu, 13 Dec 2007 20:39:56 +0300 [thread overview]
Message-ID: <20071213173956.GA436@tv-sign.ru> (raw)
In-Reply-To: <20071213173136.GO26334@parisc-linux.org>
On 12/13, Matthew Wilcox wrote:
>
> On Thu, Dec 13, 2007 at 08:29:26PM +0300, Oleg Nesterov wrote:
> > How is it possible that SIGKILL is blocked?
>
> I *think* it's possible that kernel threads may block SIGKILL.
> And I think init (pid 1) gets SIGKILL blocked.
Yes. But this shouldn't matter because we can't ptrace them. /sbin/init
doesn't block SIGKILL, but it can't be ptraced either.
Also, SIGKILL is blocked only if kthread was created by kernel_thread() and
then it does daemonize(). kthread_create()'ed kthreads don't block SIGKILL
but ignore it. The latter behaviour is more correct, but we can't do the same
for kernel_thread() threads.
Oleg.
next prev parent reply other threads:[~2007-12-13 17:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 17:29 [PATCH] arch_ptrace_stop Oleg Nesterov
2007-12-13 17:31 ` Matthew Wilcox
2007-12-13 17:39 ` Oleg Nesterov [this message]
2007-12-13 22:42 ` Roland McGrath
2007-12-16 16:24 ` Oleg Nesterov
-- strict thread matches above, loose matches on Subject: below --
2007-12-06 16:49 [PATCH 0/3] ptrace RSE handling Petr Tesarik
2007-12-08 1:11 ` [PATCH] arch_ptrace_stop Roland McGrath
2007-12-08 1:11 ` Roland McGrath
2007-12-12 5:51 ` Andrew Morton
2007-12-12 5:51 ` Andrew Morton
2007-12-12 22:36 ` Roland McGrath
2007-12-12 22:36 ` Roland McGrath
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=20071213173956.GA436@tv-sign.ru \
--to=oleg@tv-sign.ru \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=ptesarik@suse.cz \
--cc=roland@redhat.com \
--cc=tony.luck@intel.com \
--cc=willy@debian.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.