From: David Vrabel <david.vrabel@citrix.com>
To: Martin Kelly <martin@martingkelly.com>, <david.vrabel@citrix.com>,
<xen-devel@lists.xenproject.org>, <x86@kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <mingo@redhat.com>, Martin Kelly <martkell@amazon.com>,
<boris.ostrovsky@oracle.com>, <tglx@linutronix.de>
Subject: Re: [Xen-devel] [PATCH] x86/xen: panic on bad Xen-provided memory map
Date: Fri, 17 Oct 2014 13:46:08 +0100 [thread overview]
Message-ID: <54410F90.3070206@citrix.com> (raw)
In-Reply-To: <1413517692-17727-1-git-send-email-martin@martingkelly.com>
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
next prev parent reply other threads:[~2014-10-17 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-17 3:48 [PATCH] x86/xen: panic on bad Xen-provided memory map Martin Kelly
2014-10-17 12:46 ` David Vrabel [this message]
2014-10-17 12:46 ` David Vrabel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54410F90.3070206@citrix.com \
--to=david.vrabel@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin@martingkelly.com \
--cc=martkell@amazon.com \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.