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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <1221255716.11711.42.camel@bazbox>
Date:	Fri, 12 Sep 2008 22:41:56 +0100
From:	Matt Keenan <tank.en.mate@...il.com>
To:	Andi Kleen <andi@...stfloor.org>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	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

On Fri, 2008-09-12 at 23:30 +0200, Andi Kleen wrote:
> > 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?
> 

Harsh... but harsh.

Matt


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