linux-kernel - Re: Merging ptrace branch into mainline

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]

Date:	Fri, 22 Jul 2011 15:39:07 +0200
From:	Tejun Heo <tj@...nel.org>
To:	Denys Vlasenko <vda.linux@...glemail.com>
Cc:	Oleg Nesterov <oleg@...hat.com>,
	Jan Kratochvil <jan.kratochvil@...hat.com>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: Merging ptrace branch into mainline

On Fri, Jul 22, 2011 at 01:40:36PM +0200, Denys Vlasenko wrote:
> On Fri, Jul 22, 2011 at 12:30 PM, Tejun Heo <tj@...nel.org> wrote:
> To what cases of ptrace stops is this applicable?
> 
> I thought with PTRACE_O_TRACESYSGOOD the problem with SIGTRAP
> being special under strace is dealt with: now both user-sent
> SIGTRAPs and ones generated by int3 instruction are handled correctly
> in current strace git.
> 
> Is it about single-stepping? Strace doesn't use PTRACE_SIGLESTEP,
> and I didn't have the need yet to familiarize myself with it.
> Does it generate SIGTRAP?

Single step and breakpoints use SIGTRAP and there are some variances
on the information being reported depending on archs and IIRC it isn't
always possible to discern those debug traps from kill(SIGTRAP)'s from
userland.  I think cleaning up what information is reported via
siginfo on debug traps should resolve this too.

Thansk.

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