linux-kernel - Re: [PATCH] Early boot debugging via FireWire (ohci1394

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] [day] [month] [year] [list]

Date:	Mon, 17 Dec 2007 14:49:30 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Bernhard Kaindl <bk@...e.de>
Cc:	Stefan Richter <stefanr@...6.in-berlin.de>,
	Andi Kleen <ak@...e.de>, Bernhard Kaindl <bkaindl@...i.org>,
	linux-kernel@...r.kernel.org,
	linux1394-devel@...ts.sourceforge.net,
	Thomas Renninger <trenn@...e.de>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [PATCH] Early boot debugging via FireWire (ohci1394_dma=early)


* Bernhard Kaindl <bk@...e.de> wrote:

> Subject of this patch:
> 
> This patch adds a new configuration option, which adds support for a 
> new early_param which gets checked in 
> arch/x86/kernel/setup_{32,64}.c:setup_arch() to decide wether 
> OHCI-1394 FireWire controllers should be initialized and enabled for 
> physical DMA access to allow remote debugging of early problems like 
> issues ACPI or other subsystems which are executed very early.
> 
> If the config option is not enabled, no code is changed, and if the 
> boot paramenter is not given, no new code is executed, and independent 
> of that, all new code is freed after boot, so the config option can be 
> even enabled in standard, non-debug kernels.
> 
> With specialized tools, it is then possible to get debugging 
> information from machines which have no serial ports (notebooks) such 
> as the printk buffer contents, or any data which can be referenced 
> from global pointers, if it is stored below the 4GB limit and even 
> memory dumps of of the physical RAM region below the 4GB limit can be 
> taken without any cooperation from the CPU of the host, so the machine 
> can be crashed early, it does not matter.

cool stuff! I've tentatively added your patch to x86.git (pending more 
review feedback from others), but it already looks quite nice to me.

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