linux-kernel - Re: [PATCH v2] hpet: Enable hidden HPET on NVidia motherboards

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: <m3abx744yn.fsf@maximus.localdomain>
Date:	Tue, 17 Apr 2007 13:26:24 +0200
From:	Krzysztof Halasa <khc@...waw.pl>
To:	Mikko Tiihonen <mikko.tiihonen@....fi>
Cc:	clemens@...isch.de, bob.picco@...com, linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH v2] hpet: Enable hidden HPET on NVidia motherboards

Mikko Tiihonen <mikko.tiihonen@....fi> writes:

> Currently the all the code is protected by CONFIG_HPET.
> Are you proposing to use for example CONFIG_HPET_NVIDIA instead?

Something like that. CONFIG_HPET_NFORCE_DETECT maybe?

> I think that the code should be safe even without it's own config option.

Well, who knows. The hardware side (config bits) are probably safe
and easy to verify, but depending on BIOS assigning address to inactive
device seems risky.
-- 
Krzysztof Halasa
-
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/