linux-kernel - Re: [ptrace] Problem with ptrace cleanup logic.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 23 Feb 2012 16:17:54 +0100
From:	Oleg Nesterov <oleg@...hat.com>
To:	Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
Cc:	tj@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [ptrace] Problem with ptrace cleanup logic.

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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/