| 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
| ||
|
Date: Thu, 30 Sep 2010 19:34:57 +0200 From: Andi Kleen <andi@...stfloor.org> To: Alan Cox <alan@...rguk.ukuu.org.uk> Cc: Jean Delvare <khali@...ux-fr.org>, Olof Johansson <olof@...om.net>, Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, Tejun Heo <tj@...nel.org> Subject: Re: [PATCH] dmi: export dmi data through debugfs Alan Cox <alan@...rguk.ukuu.org.uk> writes: >> Now if you really insist on exposing the whole DMI table through sysfs, >> I can't prevent you from doing that. After all, ACPI already exposes >> its tables under /sys/firmware/acpi/tables (mode 0400). But then you'd >> rather expose the DMI entry point and tables >> under /sys/firmware/dmi/tables for consistency, rather than using >> debugfs. But again, I don't think it is adding any value over what we >> already have. > > If you really the DMI data generally available run dmidecode in the boot > scripts directed to a file. It even has a dump mode for this. FWIW i have been pondering to put DMI into sysfs too. One of the reasons mcelog has to start up as root is that it needs to get these tables out of /dev/mem. Just having a binary file to read would be fine though, no need to do decoding. -andi -- ak@...ux.intel.com -- Speaking for myself only. -- 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