linux-kernel - Re: [perf] overflow/perf_count_sw_cpu

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: <1311820787.3938.1551.camel@minggr.sh.intel.com>
Date:	Thu, 28 Jul 2011 10:39:47 +0800
From:	Lin Ming <ming.m.lin@...el.com>
To:	Vince Weaver <vweaver1@...s.utk.edu>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Paul Mackerras <paulus@...ba.org>, Ingo Molnar <mingo@...e.hu>,
	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
Subject: Re: [perf] overflow/perf_count_sw_cpu_clock crashes recent kernels

On Thu, 2011-07-28 at 09:54 +0800, Lin Ming wrote:
> On Thu, Jul 28, 2011 at 2:51 AM, Vince Weaver <vweaver1@...s.utk.edu> wrote:
> > Hello
> >
> >> With 3.0.0 the PAPI "overflow_allcounters" test reliably locks up my
> >> Nehalem system.
> >
> > I finally managed to narrow this down to a small test, which is attached.
> >
> > Basically measuring overflow on the perf::perf_count_sw_cpu_clock
> > event will potentially *lock up* your system from user-space.
> >
> > This seems to be a long standing bug.  It will quickly lock solid
> > my Nehalem test box on 3.0, 2.6.39 and 2.6.38.
> >
> > On a Core2 2.6.32 box the crash testing program will wedge and become
> > unkillable, but it doesn't actually kill the machine.

Hi, Vince

I re-tested current -tip tree(commit 0931941) and it works OK now.

$ ./oflo_sw_cpu_clock_crash 
Matrix multiply sum: s=27665734022509.746094
Total overflows: 3460

Could you also have a try the current -tip tree?

Lin Ming


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