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: <52A4B17F.6050809@gmail.com>
Date:	Sun, 08 Dec 2013 10:50:55 -0700
From:	David Ahern <dsahern@...il.com>
To:	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
CC:	acme@...stprotocols.net, linux-kernel@...r.kernel.org,
	Srikar Dronamraju <srikar@...ux.vnet.ibm.com>,
	Oleg Nesterov <oleg@...hat.com>, namhyung@...nel.org,
	"yrl.pp-manager.tt@...achi.com" <yrl.pp-manager.tt@...achi.com>
Subject: Re: [PATCH 2/2] perf probe: Allow user to specify address within
 executable

On 12/4/13, 12:39 AM, Masami Hiramatsu wrote:
> What would you like to do with perf probe? Direct address accessing for
> userspace is not a good way to do, because userspace is relocatable...

Masami, I am referring to the address within the executable which is
what perf-probe pushes to the kernel.

> 
>> For now I will carry the patch locally. At this point I am 20 patches
>> deep and have probably another 20 to go. What's one more. I'll come back
>> to this when I have more time.
> 
> Would you have any public git repository for that?

https://github.com/dsahern/linux/tree/perf-full-monty


 And could you share
> us what would you like to do before sending patch? We can help you to
> tell the best way.

I want to save myself some time and effort by giving the relative
address with an executable. That allows me to probe any function, and I
want to do it from a consistent user interface -- perf-probe. With the
proposed patch I have that.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ