linux-kernel - Re: another perf

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:	Wed, 29 Jan 2014 08:17:32 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Vince Weaver <vincent.weaver@...ne.edu>
Cc:	linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Paul Mackerras <paulus@...ba.org>,
	Ingo Molnar <mingo@...hat.com>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
Subject: Re: another perf_fuzzer soft lockup


* Vince Weaver <vincent.weaver@...ne.edu> wrote:

> After some idle time I've started running the perf_fuzzer again.
> 
> It quickly found this lockup on a core2 system running 3.13 (yes, I 
> should probably be running 3.14-git but I'd rather wait for rc1 
> first).

JFYI, if -git looks too dangerous to you (and I cannot blame you for 
that view in the middle of a merge window) then tip:master is usually 
a pretty safe substitute for testing, it's the v3.14 perf code on a 
v3.13 base.

> It looks like it's stuck in a lock in generic_exec_single() while 
> calling perf_event_task_output()?
> 
> I'll try to see if I can come up with a test case.

Thanks, those testcases are always very useful!

	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/