linux-kernel - RE: [perf probe] How to ask what variables can be collected at function return?

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: <50399556C9727B4D88A595C8584AAB3752571D8D@GSjpTKYDCembx32.service.hitachi.net>
Date:	Wed, 30 Sep 2015 16:48:50 +0000
From:	平松雅巳 / HIRAMATU，MASAMI 
	<masami.hiramatsu.pt@...achi.com>
To:	"'Arnaldo Carvalho de Melo'" <acme@...nel.org>
CC:	David Ahern <dsahern@...il.com>, Jiri Olsa <jolsa@...nel.org>,
	Wang Nan <wangnan0@...wei.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: RE: [perf probe] How to ask what variables can be collected at
 function return?

From: Arnaldo Carvalho de Melo [mailto:acme@...nel.org]
>
>Em Wed, Sep 30, 2015 at 08:05:09AM +0000, 平松雅巳 / HIRAMATU，MASAMI escreveu:
>> From: Arnaldo Carvalho de Melo [mailto:acme@...nel.org]
>> >
>> >How to figure out which variables can I collect at function return?
>> >None?
>>
>> At first, it seems the below pattern failed to get the probe point
>> itself, because you're specifying the return point of an inlined
>> function, which is nowhere.
>
>Would be really nice to have this warning emitted to the user, as well as bits and pieces of the following explanations.

OK, I'll include this to the other bugfixes.

Thanks!