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.1403261731390.26530@vincent-weaver-1.um.maine.edu>
Date:	Wed, 26 Mar 2014 17:33:14 -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 Tue, 25 Mar 2014, Thomas Gleixner wrote:
> debugobjects init call. Patch for that below.
> 
> What's clear from the trace is that the timer gets set up correctly,
> but when it expires the function callback is NULL. The timer is set up
> to 1sec and it's started in the context of init-1. So it's probably an
> initcall of some sort.
> 
> Do you happen to have the full bootlog up to the crash handy?

attached is the full bootlog followed by the tracedump.

> Adding "initcall_debug" to the kernel command line might give us a
> further hint what is adding the delayed_work, but I guess once we see
> the function in the trace we have a good chance to find the place
> right away. Then we have to figure out what scribbles over it .....

I haven't tried the initcall_debug yet but can if needed.

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