linux-kernel - Re: [bisected] 2.6.31 regression: fails to boot as xen guest

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, 25 Aug 2009 12:31:52 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Pekka Enberg <penberg@...helsinki.fi>
CC:	Arnd Hannemann <hannemann@...s.rwth-aachen.de>,
	Ingo Molnar <mingo@...e.hu>,
	Arnd Hannemann <Arnd.Hannemann@...s.rwth-aachen.de>,
	LKML <linux-kernel@...r.kernel.org>,
	"hannes@...xchg.org" <hannes@...xchg.org>,
	"torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
	"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Subject: Re: [bisected] 2.6.31 regression: fails to boot as xen guest

On 08/25/09 11:43, Pekka Enberg wrote:
> Aha, the previous patch worked because I #ifdef the WP test completely.
> Jeremy, the root cause here is that we do the WP test much earlier than
> before. Even with the test moved to trap_init(), we do it early compared
> to what we did before.
>
> I guess Xen is not prepared to handle traps this early in the boot
> sequence? Can we fix that?
>   

The crash is in the event (interrupt) path, which shouldn't be involved
in trap handling at all.  I'm wondering if interrupts are getting
enabled as a side-effect of handling the trap.

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