linux-kernel - Re: ptrace.2: PTRACE_KILL needs a stopped process too

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] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 09 May 2012 20:35:34 +0100
From:	Pedro Alves <palves@...hat.com>
To:	Mike Frysinger <vapier@...too.org>
CC:	Oleg Nesterov <oleg@...hat.com>,
	"Michael Kerrisk (man-pages)" <mtk.manpages@...il.com>,
	pacman@...h.dhis.org, linux-man <linux-man@...r.kernel.org>,
	lkml <linux-kernel@...r.kernel.org>,
	Denys Vlasenko <dvlasenk@...hat.com>,
	Tejun Heo <tj@...nel.org>,
	Jan Kratochvil <jan.kratochvil@...hat.com>
Subject: Re: ptrace.2: PTRACE_KILL needs a stopped process too

On 05/09/2012 04:09 PM, Mike Frysinger wrote:

> probably not that big of a deal, but the reason i like using 
> ptrace(PTRACE_KILL) over a raw kill() is that you are less likely to kill the 
> wrong process by accident.  maybe not that big of a deal in practice though.


And you can do tgkill instead.  It was specifically invented to handle the
reuse case.

-- 
Pedro Alves
--
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/