linux-kernel - Re: [PATCH 0/8] [GIT PULL] simplify the print fmt in the event format files

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:	Tue, 9 Jun 2009 19:37:32 -0400 (EDT)
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Ingo Molnar <mingo@...e.hu>
cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Minchan Kim <minchan.kim@...il.com>,
	Mel Gorman <mel@....ul.ie>,
	Christoph Hellwig <hch@...radead.org>,
	Rik van Riel <riel@...hat.com>,
	Pekka Enberg <penberg@...helsinki.fi>,
	Peter Zijlstra <peterz@...radead.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Theodore Tso <tytso@....edu>,
	Mathieu Desnoyers <compudj@...stal.dyndns.org>,
	Lai Jiangshan <laijs@...fujitsu.com>,
	Zhaolei <zhaolei@...fujitsu.com>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Jason Baron <jbaron@...hat.com>,
	Jiaying Zhang <jiayingz@...gle.com>,
	Tom Zanussi <tzanussi@...il.com>
Subject: Re: [PATCH 0/8] [GIT PULL] simplify the print fmt in the event format
 files


On Wed, 10 Jun 2009, Ingo Molnar wrote:

> 
> there's one test failure:
> 
> [    0.723000] calling  event_trace_init+0x0/0x13d @ 1
> [    0.725000] ------------[ cut here ]------------
> [    0.726000] WARNING: at kernel/trace/trace_read_binary.c:547 ftrace_initialize_print+0x673/0x690()
> [    0.727000] Hardware name: System Product Name
> [    0.728000] error in format type: 'sting:name> (<uint:wait_usec>.<printf:wait_nsec_rem:03lu> us)'
> [    0.729000] Modules linked in:
> [    0.730000] Pid: 1, comm: swapper Not tainted 2.6.30-rc8-tip-02137-g9d24ef9-dirty #51704
> [    0.731000] Call Trace:
> [    0.732000]  [<c10470aa>] warn_slowpath_common+0x65/0x95
> [    0.733000]  [<c1047118>] warn_slowpath_fmt+0x29/0x2c
> [    0.734000]  [<c10a14ef>] ftrace_initialize_print+0x673/0x690
> [    0.735000]  [<c10afa33>] ? kstrdup+0x2b/0x46
> [    0.736000]  [<c109cabc>] ? trace_define_field+0xa1/0xf5
> [    0.737000]  [<c106c0d5>] ftrace_define_fields_lock_acquired+0x132/0x13b
> [    0.738000]  [<c109cdbe>] event_create_dir+0x2ae/0x307
> [    0.739000]  [<c1973bf3>] ? event_trace_init+0x0/0x13d
> [    0.740000]  [<c1973d00>] event_trace_init+0x10d/0x13d
> [    0.741000]  [<c1001074>] do_one_initcall+0x6a/0x177
> [    0.742000]  [<c103329c>] ? kernel_map_pages+0xd2/0xe3
> [    0.743000]  [<c10690d2>] ? trace_hardirqs_on+0xb/0xd
> [    0.744000]  [<c1067855>] ? put_lock_stats+0xd/0x21
> [    0.745000]  [<c106795f>] ? lock_release_holdtime+0xf6/0xfb
> [    0.746000]  [<c10fc97c>] ? proc_register+0x14b/0x15c
> [    0.747000]  [<c15f05db>] ? _spin_unlock+0x2c/0x41
> [    0.748000]  [<c10fc97c>] ? proc_register+0x14b/0x15c
> [    0.749000]  [<c10fcaaf>] ? create_proc_entry+0x80/0x96
> [    0.750000]  [<c1086004>] ? register_irq_proc+0x91/0xad
> [    0.751000]  [<c1086078>] ? init_irq_proc+0x58/0x65
> [    0.752000]  [<c195f2d1>] kernel_init+0x100/0x151
> [    0.753000]  [<c195f1d1>] ? kernel_init+0x0/0x151
> [    0.754000]  [<c101b7e3>] kernel_thread_helper+0x7/0x10
> [    0.755000] ---[ end trace a7919e7f17c0a725 ]---
> [    0.758000] initcall event_trace_init+0x0/0x13d returned 0 after 33203 usecs
> [    0.759000] calling  ksym_tracer_stat_init+0x0/0x27 @ 1
> 
> config below.

I hit it too when I turned on lockstat. I have it fixed in my next 
release.

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