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]

Date:	Tue, 15 May 2012 15:53:56 +0300
From:	Gleb Natapov <gleb@...hat.com>
To:	Hannes Reinecke <hare@...e.de>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...ux.intel.com>
Subject: Re: [PATCH] EDD: Check for correct EDD 3.0 length

On Tue, May 15, 2012 at 02:59:17PM +0300, Gleb Natapov wrote:
> > So why do you claim we can't display it anymore?
> > 
> Before commit 0c61227094b3ddaca2f847ee287c4a2e3762b5a2 the code didn't
> calculate checksum correctly. The check always succeed, so when bios
> provided information according to T13 EDD4.0 spec interface_type contained
Correction. If BIOS provided information _not_ according to T13 EDD4.0 spec
interface_type contained garbage since the reset of the code assumes the
EDD4.0 information.

Looked like that:
# cat /sys/firmware/edd/int13_dev80/interface 
SCSI            id: 0  lun: 1224979098644774912

> garbage. After the commit checksum is calculated correctly, but according
> to T13 EDD4.0 spec, so for BIOSes that supply info according to another
> spec check fails. Since T13 EDD4.0 spec support modern interfaces (RAID,
> SATA, SAS) which another spec omits, and for interfaces they both support
> 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.
> 
> --
> 			Gleb.
> --
> 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/

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