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 for Android: free password hash cracker in your pocket

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

Message-ID: <20110602050120.GA17434@mtj.dyndns.org>
Date:	Thu, 2 Jun 2011 14:01:20 +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

Hey,

On Wed, Jun 01, 2011 at 10:08:07PM +0200, Oleg Nesterov wrote:
> > Hmm... can't we just allow PTRACE_DETACH after PTRACE_EVENT_EXIT is
> > reported?
> 
> Confused. PTRACE_DETACH surely works if the tracee reports EVENT_EXIT...
> Could you explain what you meant?

Right, I briefly forgot it's already a ptrace stop and was thinking
about using PTRACE_EVENT_EXIT as the event notification point.
Anyways, back to the topic.

Maybe I misunderstood the problem but wasn't the problem about not
being able to wait for the exit of a leader thread and detach it?  We
have reliable (sans exec but that's a different story) exit
notification with EVENT_EXIT which even reports the exit_code, so I
don't see what the problem is.  What am I missing?

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/