[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1413253817-6943-2-git-send-email-martin@martingkelly.com>
Date: Mon, 13 Oct 2014 19:30:17 -0700
From: Martin Kelly <martin@...tingkelly.com>
To: linux-kernel@...r.kernel.org, xen-devel@...ts.xenproject.org,
x86@...nel.org
Cc: david.vrabel@...rix.com, boris.ostrovsky@...cle.com,
konrad.wilk@...cle.com, hpa@...or.com, tglx@...utronix.de,
mingo@...hat.com, Martin Kelly <martin@...tingkelly.com>,
Martin Kelly <martkell@...zon.com>
Subject: [PATCH 2/2] xen/setup: warn on bad Xen-supplied memory map
Currently, we don't check the return code of sanitize_e820_map. However,
if the Xen-supplied memory map is invalid, then sanitize_e820_map will
return without doing anything, potentially leading to errors later on.
Add a WARN_ON in case sanitize_e820_map detects an invalid memory map.
Signed-off-by: Martin Kelly <martkell@...zon.com>
---
arch/x86/xen/setup.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/arch/x86/xen/setup.c b/arch/x86/xen/setup.c
index af72161..48c7072 100644
--- a/arch/x86/xen/setup.c
+++ b/arch/x86/xen/setup.c
@@ -608,7 +608,8 @@ char * __init xen_memory_setup(void)
xen_ignore_unusable(map, memmap.nr_entries);
/* Make sure the Xen-supplied memory map is well-ordered. */
- sanitize_e820_map(map, memmap.nr_entries, &memmap.nr_entries);
+ rc = sanitize_e820_map(map, memmap.nr_entries, &memmap.nr_entries);
+ WARN_ON(rc == E820_RC_BAD_MAP);
max_pages = xen_get_max_pages();
if (max_pages > max_pfn)
--
2.1.1
--
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/
Powered by blists - more mailing lists