linux-kernel - Re: Querying the bios from booted linux kernel?

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: <20080105021449.2af7a429@lxorguk.ukuu.org.uk>
Date:	Sat, 5 Jan 2008 02:14:49 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Gene Heskett <gene.heskett@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Querying the bios from booted linux kernel?

> Unfortunately, it is not trivial to produce a mapping from EDD data to 
> real-life disks.  Your best bet is if the disks have an MBR signature, 

Untrue for all but the very earliest EDD. True for our kernel support
which wants improving some day

> in which case the EDD code will capture those; you can then correlate 
> them to real disks.

EDD 1 provides the I/O base of each BIOS device so you can cross corelate
at least each IDE device with the BIOS identifier. EDD 3 provides paths
in multiple forms including PCI identifiers which serve the same purpose.

Unfortunately our EDD boot code doesn't capture the right bits in all
these cases.
--
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/