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: <558D3307.2080801@huawei.com>
Date:	Fri, 26 Jun 2015 19:09:59 +0800
From:	"Wangnan (F)" <wangnan0@...wei.com>
To:	Alexei Starovoitov <ast@...mgrid.com>, <acme@...nel.org>,
	<brendan.d.gregg@...il.com>, <daniel@...earbox.net>,
	<namhyung@...nel.org>, <masami.hiramatsu.pt@...achi.com>,
	<paulus@...ba.org>, <a.p.zijlstra@...llo.nl>, <mingo@...hat.com>,
	<jolsa@...nel.org>, <dsahern@...il.com>
CC:	<linux-kernel@...r.kernel.org>, <lizefan@...wei.com>,
	<hekuang@...wei.com>, <xiakaixu@...wei.com>, <pi3orama@....com>
Subject: Re: [RFC PATCH 3/3] perf tools: Support attach BPF program on uprobe
 events



On 2015/6/26 16:47, Alexei Starovoitov wrote:
> On 6/25/15 3:37 AM, Wang Nan wrote:
>> This patch append new syntax to BPF object section name to support
>> probing at uprobe event. Now we can use BPF program like this:
>>
>>   SEC(
>>   "target:/lib64/libc.so.6\n"
>>   "libcwrite=__write"
>>   )
>>   int libcwrite(void *ctx)
>>   {
>>       return 1;
>>   }
>>
>> Where, in section name of a program, before the main config string,
>> we can use 'key:value' style options. Now the only option key "target"
>> is for uprobe probing.
>>
>> Signed-off-by: Wang Nan<wangnan0@...wei.com>
>
> looks good.
> why use ':' separator? '=' should work as well and will be more
> consistent ?
Will do.

Thank you.

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