linux-kernel - Re: [PATCH 00/16] [GIT PULL] tracing: fixes/cleanups, no stop-machine, update stack tracer

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: <20120107121959.GA28462@elte.hu>
Date:	Sat, 7 Jan 2012 13:20:00 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 00/16] [GIT PULL] tracing: fixes/cleanups, no
 stop-machine, update stack tracer


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

> On Fri, 2012-01-06 at 09:51 +0100, Ingo Molnar wrote:
> > * Steven Rostedt <rostedt@...dmis.org> wrote:
> > 
> > > Not sure what else to do. Have you been able to trigger 
> > > these bugs without my patches? All the bugs I've been 
> > > hitting after merging my patches, I've been able to hit 
> > > with tip/master as well.
> > 
> > No, as i described to you the tree(s) without your patches 
> > all did 50+ series of bootups.
> > 
> 
> Is it only with this config that it fails? Is there another 
> config that doesn't? Also is it only failing on one box, or 
> can you reproduce the failure on different hardware? What 
> version of fedora are you running? Could this be something 
> that requires systemd?

I've now established a 500 successful randconfig tests run 
baseline, and will merge in your trees and see whether they 
start producing failures.

If they don't then i think we can chalk up the allyesconfig 
failures to some other factor.

Thanks,

	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/