| 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
| ||
|
Message-ID: <20150226104134.178e8c35@endymion.delvare> Date: Thu, 26 Feb 2015 10:41:34 +0100 From: Jean Delvare <jdelvare@...e.de> To: dmidecode-devel@...gnu.org, Ivan Khoronzhuk <ivan.khoronzhuk@...aro.org> Cc: matt.fleming@...el.com, ard.biesheuvel@...aro.org, linux-kernel@...r.kernel.org, leif.lindholm@...aro.org, Mark Salter <msalter@...hat.com>, grant.likely@...aro.org Subject: Re: [dmidecode] [Patch v3] firmware: dmi-sysfs: add SMBIOS entry point area raw attribute Replying to myself... On Thu, 26 Feb 2015 09:50:42 +0100, Jean Delvare wrote: > Please also note that the recently released version 3.0.0 of the SMBIOS > specification introduces a new entry point format, and the firmware is > allowed to implement both the old and the new format. It may be > desirable to expose both to user-space under different names. Having read the kernel code meanwhile, I see we will call either dmi_smbios3_present or dmi_present successfully, not both, so presenting both entry points to user-space would be non-trivial. So I'm fine with presenting only one entry point in sysfs for the time being. We can always revisit later if it turns out that dmidecode really needs both in some cases. -- Jean Delvare SUSE L3 Support -- 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