linux-kernel - Re: [PATCH 03/10] ptrace: implement PTRACE

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]

Message-ID: <20110601053408.GD23067@mtj.dyndns.org>
Date:	Wed, 1 Jun 2011 14:34:08 +0900
From:	Tejun Heo <tj@...nel.org>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	Denys Vlasenko <vda.linux@...glemail.com>, indan@....nu,
	bdonlan@...il.com, linux-kernel@...r.kernel.org,
	jan.kratochvil@...hat.com, akpm@...ux-foundation.org
Subject: Re: [PATCH 03/10] ptrace: implement PTRACE_SEIZE

Hello, Oleg.

On Tue, May 31, 2011 at 09:08:09PM +0200, Oleg Nesterov wrote:
> Speaking of this particular problem, it is really annoying. The leader
> exits, and it even notifies the tracer. For what? waitpid() returns 0
> or hangs depending on WNOHANG, any ptrace() request fails with ESRCH.

Hmm... can't we just allow PTRACE_DETACH after PTRACE_EVENT_EXIT is
reported?  It doesn't involve changes to any visible behavior (other
than allowing DETACH of course) and we don't lose anything.  Haven't
really thought about the implementation but I don't think this would
be too difficult.

Thanks.

-- 
tejun
--
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/