linux-kernel - Re: [PATCH] tracing, powerpc: Add data parameter to powerpc-specific tracepoints

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]

Date:	Mon, 24 May 2010 23:17:46 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Paul Mackerras <paulus@...ba.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] tracing, powerpc: Add data parameter to
 powerpc-specific tracepoints

On Mon, 2010-05-24 at 15:27 +1000, Paul Mackerras wrote:
> Commit 38516ab5 ("tracing: Let tracepoints have data passed to
> tracepoint callbacks") added a void *data parameter to tracing
> callbacks and to the {un,}register_trace_* functions, requiring all
> tracepoint callback functions to have the extra void * parameter.
> 
> This adds the void *data parameter to the tracepoints in the pSeries
> hypervisor call code.  Without this, hvCall_inst.c fails to compile
> with tracing enabled.
> 

Acked-by: Steven Rostedt <rostedt@...dmis.org>

Thanks!

-- Steve

> Signed-off-by: Paul Mackerras <paulus@...ba.org>
> ---
>  arch/powerpc/platforms/pseries/hvCall_inst.c |   13 +++++++------
>  1 file changed, 7 insertions(+), 6 deletions(-)
> 
> diff --git a/arch/powerpc/platforms/pseries/hvCall_inst.c b/arch/powerpc/platforms/pseries/hvCall_inst.c
> index 1fefae7..9d03ef5 100644
> --- a/arch/powerpc/platforms/pseries/hvCall_inst.c
> +++ b/arch/powerpc/platforms/pseries/hvCall_inst.c
> @@ -102,7 +102,8 @@ static const struct file_operations hcall_inst_seq_fops = {
>  #define CPU_NAME_BUF_SIZE	32
>  


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