linux-kernel - Re: Regression in module wmi since 2.6.32 (bisected to commit 1caab3c)

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:	Wed, 6 Jan 2010 15:27:24 +0000
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Larry Finger <Larry.Finger@...inger.net>
Cc:	Carlos Corbacho <carlos@...angeworlds.co.uk>,
	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux ACPI <linux-acpi@...r.kernel.org>
Subject: Re: Regression in module wmi since 2.6.32 (bisected to commit
	1caab3c)

Hm. I think this is an artifact of the way we're treating WMI right now. 
The assumption is that the interfaces are defined in namespace by their 
GUID, whereas in fact they're defined by their ACPI namespace. Can we 
avoid this by just setting the parent to the ACPI device's corresponding 
Linux device (if present) and including the WMI device's name in the 
dev_set_name call?

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/