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] [day] [month] [year] [list]

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

On 07/22, Tejun Heo wrote:
>
> 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.

Yes, we should audit the arch/ code.

On x86 the tracer can discern step/breakpoints traps afaics, still probably
it makes sense to change do_int3() to use fill_sigtrap_info(). Currently we
report si_code = SI_KERNEL.

Oleg.

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