linux-kernel - Re: [libtraceevent] hrtimer_expire

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:	Tue, 5 Nov 2013 08:15:22 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Cc:	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Namhyung Kim <namhyung@...nel.org>,
	Jon Stanley <jonstanley@...il.com>,
	Sasha Levin <sasha.levin@...cle.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [libtraceevent] hrtimer_expire_entry unknown op '{'

On Tue, 5 Nov 2013 12:37:55 +0300
Sergey Senozhatsky <sergey.senozhatsky@...il.com> wrote:

> Hello,
> 
> libtraceevent reports ` unknown op '{' ' while processing hrtimer_expire_entry event

Yes, we need to port the plugin code from trace-cmd to handle this and
other cases. It's a known issue.

-- Steve

> 
> cat /sys/kernel/debug/tracing/events/timer/hrtimer_expire_entry/format
> 
> name: hrtimer_expire_entry
> ID: 91
> format:
> 	field:unsigned short common_type;	offset:0;	size:2;	signed:0;
> 	field:unsigned char common_flags;	offset:2;	size:1;	signed:0;
> 	field:unsigned char common_preempt_count;	offset:3;	size:1;	signed:0;
> 	field:int common_pid;	offset:4;	size:4;	signed:1;
> 
> 	field:void * hrtimer;	offset:8;	size:8;	signed:0;
> 	field:s64 now;	offset:16;	size:8;	signed:1;
> 	field:void * function;	offset:24;	size:8;	signed:0;
> 
> print fmt: "hrtimer=%p function=%pf now=%llu", REC->hrtimer, REC->function, (unsigned long long)(((ktime_t) { .tv64 = REC->now }).tv64)
> 
> 
> 	-ss

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