linux-kernel - Re: DMI: add-type-41

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:	Fri, 8 Feb 2008 19:25:52 +0100
From:	Wim Van Sebroeck <wim@...ana.be>
To:	Matt Domsch <Matt_Domsch@...l.com>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: DMI: add-type-41

Hi Matt,

> >     [PATCH] SMBIOS/DMI - add type 41 = Onboard Devices Extended Information
> 
> Is there something in the kernel that will consume this data, or is it
> being exported in /sys/class/dmi/id somehow?  There will be one table
> entry per device (Dell PowerEdge x9xx servers with recent BIOS do so).
> 
> FWIW, my biosdevname app consumes this data, using dmidecode from
> userspace.

Just like smbios/dmi type 10 we add the the info to the dmi_devices list.
The dmi_find_device function (see drivers/firmware/dmi_scan.c) makes this
info available to other device drivers (like drivers/ata/ata_piix.c,
drivers/misc/thinkpad_acpi.c, drivers/watchdog/ibmasr.c and
drivers/char/ipmi/ipmi_si_intf.c).

The dmi_devices list is a different list then the dmi_ident table that stores
the BIOS, PRODUCT, BOARD and CHASSIS info (and that is exported to /sys/class/dmi/* ).
The dmi_devices list is not exported to sysfs as far as I know.

My opinion: if we have type 10 we will need type 41 in the future. If we don't need
type 10 then we don't need type 41 neither (since we can use dmidecode in userspace).

Greetings,
Wim.

--
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/