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: <20110304161441.GA12987@host1.jankratochvil.net>
Date:	Fri, 4 Mar 2011 17:14:41 +0100
From:	Jan Kratochvil <jan.kratochvil@...hat.com>
To:	Denys Vlasenko <vda.linux@...glemail.com>
Cc:	Tejun Heo <tj@...nel.org>, 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

On Tue, 01 Mar 2011 23:14:14 +0100, Denys Vlasenko wrote:
> On Tue, Mar 1, 2011 at 8:06 PM, Jan Kratochvil <jan.kratochvil@...hat.com> wrote:
> > Currently it is already a problem that apps did not / do not expect the first
> > waitpid after PTRACE_ATTACH may not be SIGSTOP.
> 
> That's exactly why we want to add a better alternative, which doesn't
> insert that blasted SIGSTOP.

But it insteads blasted SIGTRAP (or some other signal) instead.

It would be best if such PTRACE_SEIZE (similar to PTRACE_INTERRUPT) would
guarantee the first waitpid afterwards returns the artificial signal from
PTRACE_SEIZE.


Thanks,
Jan
--
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/