linux-kernel - Re: [RFC] Proposal for ptrace improvements

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: <20110302072848.GB19669@htj.dyndns.org>
Date:	Wed, 2 Mar 2011 08:28:48 +0100
From:	Tejun Heo <tj@...nel.org>
To:	Denys Vlasenko <vda.linux@...glemail.com>
Cc:	Jan Kratochvil <jan.kratochvil@...hat.com>,
	Oleg Nesterov <oleg@...hat.com>,
	Roland McGrath <roland@...hat.com>,
	linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org
Subject: Re: [RFC] Proposal for ptrace improvements

Hello,

On Tue, Mar 01, 2011 at 11:14:14PM +0100, Denys Vlasenko wrote:
> There may be reasons to have PTRACE_SEIZE operation split like that.
> For one, this allows debugger to do PTRACE_CONT, and later issue
> PTRACE_INTERRUPT to stop the tracee again. PTRACE_INTERRUPT stop may
> be better for some scenarios where debugger wants to make the stop
> invisible to the parent, or when debugger wants to stop just one
> thread of the process.

PTRACE_SEIZE can be used like PTRACE_INTERRUPT.  It works whether the
tracee is attached or not.

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/