linux-kernel - Re: [PATCH] ptrace: make former thread ID available via PTRACE_GETEVENTMSG after PTRACE_EVENT

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: <20110627135252.GB30101@htj.dyndns.org>
Date:	Mon, 27 Jun 2011 15:52:52 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	Denys Vlasenko <vda.linux@...glemail.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ptrace: make former thread ID available via
 PTRACE_GETEVENTMSG after PTRACE_EVENT_EXEC stop (v.2)

Hello, Oleg.

On Mon, Jun 27, 2011 at 03:47:13PM +0200, Oleg Nesterov wrote:
> > Do we want to enable this silently?  Wouldn't it be better to make it
> > dependent on PT_SEIZED?
> 
> Hmm. Not sure I understand. Why can't PTRACE_SEIZE add PT_TRACE_EXEC
> (and PT_TRACESYSGOOD) along with PT_SEIZED during attach?

I'm worrying about !PT_SEIZED case.  If we make it solely depend on
PT_TRACE_EXEC, newer kernels report the old pid while olders ones
don't and the only way to discover would be either comparing kernel
version or actually trying it - both aren't too nice.

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/