This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [PATCH] Unified shutdown code

To: "Cihula, Joseph" <joseph.cihula@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] Unified shutdown code
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 11 Sep 2007 07:17:23 +0100
Cc: "Wang, Shane" <shane.wang@xxxxxxxxx>, "Wei, Gang" <gang.wei@xxxxxxxxx>
Delivery-date: Mon, 10 Sep 2007 23:13:18 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <D936D925018D154694D8A362EEB08920025E5745@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcfxsZEip0g/k3RSRdWVCnLdnRf+DgCHIfGIAAaqfEAAFKnpuQ==
Thread-topic: [Xen-devel] [PATCH] Unified shutdown code
User-agent: Microsoft-Entourage/
On 10/9/07 22:22, "Cihula, Joseph" <joseph.cihula@xxxxxxxxx> wrote:

> But the purpose of centralizing it was so that the hook into sboot's
> shutdown wouldn't need to be in multiple place.  And the reason to hook
> into sboot's shutdown (which also supports the halt action) even though
> the system is being halt'ed is so that we don't leave some path that
> allows the system to be subverted or misused while still having
> privileged access to the TPM, etc.

Why is Xen running a halt loop on every CPU any more exploitable than Xen
running normal Xen code on every CPU? If every CPU is spinning on HLT with
interrupts disabled then the only signals that will change state are things
like NMI, INIT, reset?

 -- Keir

> That said, I'm not aware of any exploitable conditions/paths/environment
> when Xen is placed in a halt loop (at least none that JTAG users
> wouldn't already have without waiting for the system to halt), so I
> suppose that this extra bit of caution is not really necessary.  But if
> the EARLY_FAIL behavior gets changed back to halt, is there any harm?

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>