linux-kernel - Re: [PATCH] apci: dump slit

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080912213053.GR7714@one.firstfloor.org>
Date:	Fri, 12 Sep 2008 23:30:53 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	Andi Kleen <andi@...stfloor.org>,
	Yinghai Lu <yhlu.kernel@...il.com>,
	Andrew Morton <akpm@...ux-foundation.org>, mingo@...e.hu,
	hpa@...or.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] apci: dump slit

> 1.) what guarantees that we reach user space ?

Broken SLITs don't prevent booting.

> 2) If it is _valuable_ information which we can gather via kernel
>    output, then it is much more conveniant than asking the user to type
>    whatevercryptictoolcommandline and provide the output.

Yes excellent point.  Should we dump the complete ACPI tables?
Do you prefer hexdump or do we need a ASL disassembler?
Also complete SMBIOS? Also the legacy mptables of course too.
And all the EFI methods.  Ideally a disassembly of the complete BIOS.
Did I miss anything?

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