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: <4A881A27.6090603@s5r6.in-berlin.de>
Date:	Sun, 16 Aug 2009 16:39:35 +0200
From:	Stefan Richter <stefanr@...6.in-berlin.de>
To:	Matthew Garrett <mjg59@...f.ucam.org>
CC:	Markus Trippelsdorf <markus@...ppelsdorf.de>,
	Zeev Tarantov <zeev.tarantov@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [BUG] [hwmon] linux 2.6.31-rc6 regression

Matthew Garrett wrote:
> On Sun, Aug 16, 2009 at 07:37:35AM +0200, Markus Trippelsdorf wrote:
>> On Sun, Aug 16, 2009 at 02:03:03AM +0100, Matthew Garrett wrote:
>>> 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.
> 
> It's not - 2.6.29 had this behaviour, and it got broken in 2.6.30. This 
> restores the status quo.

Then why did my 2.6.29 did _not_ have this behavior?
(here: ASUS M3A78-EM, it87 driver)
-- 
Stefan Richter
-=====-==--= =--- =----
http://arcgraph.de/sr/
--
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/