From: Oleg Nesterov <oleg@redhat.com>
To: Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>
Cc: tj@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ptrace] Problem with ptrace cleanup logic.
Date: Thu, 23 Feb 2012 16:17:54 +0100 [thread overview]
Message-ID: <20120223151754.GA1065@redhat.com> (raw)
In-Reply-To: <201202230526.q1N5QdUc035041@www262.sakura.ne.jp>
On 02/23, Tetsuo Handa wrote:
>
> I noticed that ptrace(PTRACE_ATTACH, 1) makes the global init process remain
> killable even after a process that called ptrace(PTRACE_ATTACH, 1) exits.
Yes, known problem. We should cleanup the usage of signal->flags.
This also allows to kill the new bitfields in signal_struct.
But firstly we should cleanup force_sig_info(), I sent the initial
patches.
The problem is: init loses SIGNAL_UNKILLABLE.
Oleg.
prev parent reply other threads:[~2012-02-23 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 5:26 [ptrace] Problem with ptrace cleanup logic Tetsuo Handa
2012-02-23 15:17 ` Oleg Nesterov [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=20120223151754.GA1065@redhat.com \
--to=oleg@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=tj@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).