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] [day] [month] [year] [list]
Date:	Sun, 5 Aug 2007 17:18:01 -0300
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Adrian Bunk <bunk@...sta.de>
Cc:	Len Brown <len.brown@...el.com>, linux-kernel@...r.kernel.org,
	ibm-acpi-devel@...ts.sourceforge.net,
	René Treffer <treffer@...tum.de>,
	Michal Piotrowski <michal.k.k.piotrowski@...il.com>
Subject: Re: [2.6.23 regression fix] fix thinkpad_acpi without hardware

On Sun, 05 Aug 2007, Adrian Bunk wrote:
> René Treffer reported that booting a CONFIG_THINKPAD_ACPI=y kernel on a 
> machine without the hardware results in an Oops.
> 
> The trace is thinkpad_acpi_module_init -> thinkpad_acpi_module_exit -> 
> driver_remove_file -> sysfs_hash_and_remove.
> 
> The error handling if thinkpad_acpi_module_init() fails generally looks 
> suspicious, but this patch at least fixes the common case if no hardware 
> was found, and it seems in this case there isn't any cleanup 
> actually required.
> 
> Broken by commit d5a2f2f1d68e2da538ac28540cddd9ccc733b001.
> 
> Signed-off-by: Adrian Bunk <bunk@...sta.de>

NAK

Proper fix already sent to Len Brown, and already queued to be pulled by
Linus.

Len, that'd be "ACPI: thinkpad-acpi: fix the module init failure path",
http://thread.gmane.org/gmane.linux.acpi.devel/24413

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ