linux-kernel - [BUG] kacpi_notify goes into an infinite loop (luckly it calls cond

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-next>] [day] [month] [year] [list]

Date:	Fri, 28 May 2010 21:01:22 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	Thomas Renninger <trenn@...e.de>, clarkt@...p.com,
	Zhang Rui <rui.zhang@...el.com>,
	Len Brown <len.brown@...el.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: [BUG] kacpi_notify goes into an infinite loop (luckly it calls
 cond_resched)

I just replaced Windows with F12 on my wife's computer, to have nothing
but issues. But anyway, one of the issues I had on this box was in
vanilla linux kernel 2.6.34 (all the fedora kernels had other issues),
the kacpi_notify would go into an infinite loop.

I debugged it a bit with ftrace and saw that the kacpi_notify workqueue
was constantly requeuing itself (thanks to the workqueue trace events).

I bisected this, and it came down to this change:

commit fa80945269f312bc609e8384302f58b03c916e12
Author: Thomas Renninger <trenn@...e.de>
Date:   Sat Feb 20 11:44:27 2010 +0100

    ACPI thermal: Don't invalidate thermal zone if critical trip point is bad

I checked out 2.6.34 again, and reverted this patch, and the problem
went away.

The box is an old Compaq Presario that I bought in 2003 or 2004.

-- Steve

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