linux-kernel - Re: [BUG] [hwmon] linux 2.6.31-rc6 regression

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: <20090816143846.5c729d95@lxorguk.ukuu.org.uk>
Date:	Sun, 16 Aug 2009 14:38:46 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Markus Trippelsdorf <markus@...ppelsdorf.de>
Cc:	Matthew Garrett <mjg59@...f.ucam.org>,
	Zeev Tarantov <zeev.tarantov@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [BUG] [hwmon] linux 2.6.31-rc6 regression

> > The hwmon driver is attempting to allocate a region that's also used by 
> > your ACPI firmware. There's no way to synchronise access between the 
> > kernel and the firmware, so allowing both is potentially racy - we've 
> > seen numerous cases where the combination results in the system 
> > incorrectly generating critical temperatuer shutdowns, for instance, 
> > when some other indexed access gets interpreted as the temperature or 
> > when the hwmon chip's state machine is confused. The failure of hwmon to 
> > bind is a feature here, not a bug. You can override it with 
> > acpi_enforce_resources=no on the kernel command line.
> 
> But we don't introduce »features« that break hardware monitoring on
> numerous machines in rc6 normally, IIRC.
> If this so important and critical to you, than just add a »hyperstrict«
> parameter to acpi_enforce_resources or make »lax« the default.

This is a bug fix not a feature - clashing hwmon and ACPI can seriously
screw up a system, cause it to do things like shutdown randomly and the
like.

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