From: Andrew Cooper <andrew.cooper3@citrix.com>
To: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: Keir Fraser <keir@xen.org>, Jan Beulich <JBeulich@suse.com>
Subject: kexec: Clear notes during setup
Date: Fri, 4 May 2012 12:42:29 +0100 [thread overview]
Message-ID: <4FA3C0A5.7030309@citrix.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 839 bytes --]
I know that xen-unstable is on a feature freeze, and this is not
strictly a bugfix (yet; see below), but as it is safe and designed to
help clarity in the case of a crash, so I request that it be considered
for inclusion.
I have constructed an artificial case where the information reported in
1 per-cpu crash note was stale by using low_crashinfo mode, crashing
Xen, allowing it to reboot, offlining a CPU then re-crashing Xen. This
leaves stale register state written into the offlined CPU crash
information. In this case, the information was stale but correct, due
to the predictable nature of the Xen crash path from the 'C' debug key,
but there is no guarantee that in the case of a real crash, the same
will still be true.
--
Andrew Cooper - Dom0 Kernel Engineer, Citrix XenServer
T: +44 (0)1223 225 900, http://www.citrix.com
[-- Attachment #2: kexec-clear-notes.patch --]
[-- Type: text/x-patch, Size: 1502 bytes --]
# HG changeset patch
# Parent 98fe3b2a572d4ffe704124e75c7aa8d94dbb51bc
kexec: clear notes during setup
Explicity zero the memory backing the crash notes during setup.
This allows the crash environment to be rather more certain whether the crash
notes were actually written, rather than trusting that the memory was clear
beforehand.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
diff -r 98fe3b2a572d xen/common/kexec.c
--- a/xen/common/kexec.c
+++ b/xen/common/kexec.c
@@ -401,7 +401,7 @@ static int kexec_init_cpu_notes(const un
/* If we dont care about the position of allocation, malloc. */
if ( low_crashinfo_mode == LOW_CRASHINFO_NONE )
- note = xmalloc_bytes(nr_bytes);
+ note = xzalloc_bytes(nr_bytes);
/* Protect the write into crash_notes[] with a spinlock, as this function
* is on a hotplug path and a hypercall path. */
@@ -505,7 +505,7 @@ static int __init kexec_init(void)
if ( low_crashinfo_mode > LOW_CRASHINFO_NONE )
{
- size_t crash_heap_size;
+ size_t crash_heap_size, i;
/* This calculation is safe even if the machine is booted in
* uniprocessor mode. */
@@ -520,6 +520,9 @@ static int __init kexec_init(void)
if ( ! crash_heap_current )
return -ENOMEM;
+ for ( i=0; i< (crash_heap_size >> PAGE_SHIFT); ++i )
+ clear_page(crash_heap_current + (i << PAGE_SHIFT));
+
crash_heap_end = crash_heap_current + crash_heap_size;
}
[-- Attachment #3: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2012-05-04 11:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 11:42 Andrew Cooper [this message]
2012-05-04 12:51 ` kexec: Clear notes during setup Jan Beulich
2012-05-04 15:19 ` Andrew Cooper
2012-05-04 15:25 ` Jan Beulich
2012-05-04 15:39 ` Andrew Cooper
2012-05-04 16:01 ` 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=4FA3C0A5.7030309@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).