[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] x86/xen: panic on bad Xen-provided memory map

To: Martin Kelly <martin@xxxxxxxxxxxxxxxx>, <david.vrabel@xxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxxx>, <x86@xxxxxxxxxx>, <linux-kernel@xxxxxxxxxxxxxxx>
From: David Vrabel <david.vrabel@xxxxxxxxxx>
Date: Fri, 17 Oct 2014 13:46:08 +0100
Cc: boris.ostrovsky@xxxxxxxxxx, mingo@xxxxxxxxxx, tglx@xxxxxxxxxxxxx, Martin Kelly <martkell@xxxxxxxxxx>
Delivery-date: Fri, 17 Oct 2014 12:46:15 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 17/10/14 04:48, Martin Kelly wrote:
> Panic if Xen provides a memory map with 0 entries. Although this is
> unlikely, it is better to catch the error at the point of seeing the map
> than later on as a symptom of some other crash.

Applied, thanks.

David

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

References:
- [Xen-devel] [PATCH] x86/xen: panic on bad Xen-provided memory map
  - From: Martin Kelly

Prev by Date: Re: [Xen-devel] [PATCH] xen/time: Fix incorrect per_cpu accessor in xen_clocksource_read()
Next by Date: Re: [Xen-devel] ARM, time: alternative of using udelay() before init time
Previous by thread: [Xen-devel] [PATCH] x86/xen: panic on bad Xen-provided memory map
Next by thread: [Xen-devel] [qemu-mainline test] 30771: regressions - FAIL
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.