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: <20101025155541.GA2884@redhat.com>
Date:	Mon, 25 Oct 2010 11:55:42 -0400
From:	Jason Baron <jbaron@...hat.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	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>,
	masami.hiramatsu.pt@...achi.com
Subject: Re: [PATCH][GIT PULL] tracing: Fix compile issue for
	trace_sched_wakeup.c

On Sat, Oct 23, 2010 at 10:02:16PM +0200, Ingo Molnar wrote:
> 
> > > Not the same config, and it's very spurious - i.e. a slightly different -tip 
> > > version with the same config will boot fine. (this suggests some race)
> > 
> > if possible, can you post that .config?
> 
> I just reproduced it again with tip-1128a72 - config and full bootlog attached.
> 
> The crash picture tends to vary - sometimes it crashes in fork, sometimes in the 
> timer interrupt. Here's the current one:
> 

thanks. I've been able to re-produce both the fork, and the timer
interrupt crashes.

It looks to me like we are patching the correct addresses with the
correct instructions, based on looking at the disassembly and tracing
what is getting patched when before the crash.

That's not say we aren't missing a cache flush somewhere...but I don't see
any code in a bad state so far...

I'm also wondering if the self tests arent' enabled. If we run them
after the system is up, if that works. perhaps, during boot things
aren't quite set up right for some reason?

Another variable here is of course the compiler version. I know that
'asm goto' was backported to the fedora 4.4 gcc...but it would be
interesting to test a 4.5 version in the failure cases - I will look at
that shortly.

thanks,

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