linux-kernel - Re: [PATCH] EDD: Check for correct EDD 3.0 length

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: <20120515150015.5bf17aea@pyramind.ukuu.org.uk>
Date:	Tue, 15 May 2012 15:00:15 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Gleb Natapov <gleb@...hat.com>
Cc:	Hannes Reinecke <hare@...e.de>,
	LKML <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...ux.intel.com>
Subject: Re: [PATCH] EDD: Check for correct EDD 3.0 length

> T13 EDD4.0 actually supply enough information to link edd entry to actual
> device (another spec does not), I do not see support for other spec to
> be important, but you are welcome to write support for it if you need
> it. The only way I see to check what spec edd info corresponds to is to
> calculate checksum according to both specs and see which one succeeds.

I also think you are confused on this: EDD 3.0 provides enough
information to link most types of hardware to the device. It provides the
PCI or Legacy path to the interface and the device LUN, or for 1394 etc
the WWID which can be used to cross match. It doesn't address port
multipliers.

EDD 1.1 provides sufficient information for old systems too via the FDPT
as they only have to deal with MFM/IDE/ATA controllers at the legacy
mappings and these are described by the FDPT.

Prior to that it gets a bit more interesting and you have to go poking in
BIOS magic and have the required spellbooks to hand. However right back
to the original 386 era PCs the data is available.

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