linux-kernel - Re: rb tree hrtimer lockup bug (found by 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.10.1403201045560.21603@vincent-weaver-1.um.maine.edu>
Date:	Thu, 20 Mar 2014 10:47:31 -0400 (EDT)
From:	Vince Weaver <vincent.weaver@...ne.edu>
To:	Thomas Gleixner <tglx@...utronix.de>
cc:	Vince Weaver <vincent.weaver@...ne.edu>,
	linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...hat.com>
Subject: Re: rb tree hrtimer lockup bug (found by perf_fuzzer)

On Thu, 20 Mar 2014, Thomas Gleixner wrote:

> Do you have DEBUG_OBJECTS_WORK and DEBUG_OBJECTS_FREE enabled?

yes.

> Find a more brute force method to get this decoded below. Full patch
> this time, please zap the old one. That should spill out the recent
> debug object calls and we can just hope, that we get enough history to
> find this horror.

The patch didn't compile, as "addr" was not known.  I guessed and changed 
it to "oaddr", but if that's not what you meant then the trace results 
might be useless.

> Btw, can you send me your .config file, so I might try to reproduce.

attached is the log (compressed as it was long this time) as well as the 
config I am using.

Vince
Download attachment "hrtimer_boot.log.bz2" of type "APPLICATION/octet-stream" (30570 bytes)

Download attachment "haswell.config.bz2" of type "APPLICATION/octet-stream" (33879 bytes)