linux-kernel - Re: unpredictability in scheduler test results -- still present

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, 30 Sep 2008 15:14:07 -0600
From:	"Chris Friesen" <cfriesen@...tel.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	linux-kernel@...r.kernel.org, Steven Rostedt <rostedt@...dmis.org>
Subject: Re: unpredictability in scheduler test results -- still present

Ingo Molnar wrote:
> * Chris Friesen <cfriesen@...tel.com> wrote:
>> Ingo Molnar wrote:

>>> OTOH, what does 'truning on dftrace' exactly mean? Just enabling it in  
>>> the .config, or also activating it via /debug/tracing/current_tracer?

>> Just enabling it in the .config is enough to trigger the behaviour 
>> change.  I'm not explicitly activating any traces.

> ok, that would be a clear ftrace bug i guess?

It's either an ftrace bug or a fragile load balancer bug.  I wonder if 
it's related somehow to the stop_machine() call in ftrace_dynamic_init()?

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