linux-kernel - Re: [PATCH][GIT PULL] tracing: Fix compile issue for trace_sched

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: <20101020184032.GB12666@elte.hu>
Date:	Wed, 20 Oct 2010 20:40:32 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Jason Baron <jbaron@...hat.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Arnaldo Carvalho de Melo <acme@...hat.com>
Subject: Re: [PATCH][GIT PULL] tracing: Fix compile issue for
 trace_sched_wakeup.c


* Steven Rostedt <rostedt@...dmis.org> wrote:

> jump_label_update uses stop_machine to enable each tracepoint. Thus this is 
> stressing stop machine.
> 
> Does this only happen on i386, or do we get this on x86_64 too?

I've only seen it on 32-bit - and this testbox is booting both random 64-bit and 
32-bit kernels, so the test proportion is 50%.

The failures started at around the time Thomas did the big irq/core changes a couple 
of days ago. I first blamed it on him. I.e. it's around:

  12ef49d: Merge branch 'irq/core'

That's right after jump labels and some other tracing changes went in. The compiler 
i'm using is:

  gcc version 4.4.4 20100514 (Red Hat 4.4.4-3) (GCC) 

which doesnt support jump labels.

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