linux-kernel - Re: [patch] x86, ptrace: in-kernel BTS interface

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:	Wed, 30 Apr 2008 18:06:11 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	"Metzger, Markus T" <markus.t.metzger@...el.com>
Cc:	Andi Kleen <andi@...stfloor.org>, andi-suse@...stfloor.org,
	hpa@...or.com, linux-kernel@...r.kernel.org, mingo@...e.hu,
	tglx@...utronix.de, markus.t.metzger@...il.com,
	"Siddha, Suresh B" <suresh.b.siddha@...el.com>, roland@...hat.com,
	akpm@...ux-foundation.org, mtk.manpages@...il.com,
	eranian@...glemail.com, "Villacis, Juan" <juan.villacis@...el.com>
Subject: Re: [patch] x86, ptrace: in-kernel BTS interface

> 
> >I'm not quite sure on the kernel interface. How would a in kernel
> >subsystem use it for tracing itself for example?
> 
> The task parameter would be current.
> 
> Apart from that, you would use it the same way it is used in
> arch/x86/kernel/ptrace.c.

Hmm, sounds a little too complicated. Surely that could be easier?

> 
> You would want to bts_configure() it to disable tracing before you start
> reading your own BTS buffer.

I would suggest to write a simple example and put it with some overview
into Documentation

-Andi


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