a4d1d9fe03
bnc#828623 - bnc#839596 - VUL-0: CVE-2013-1442: XSA-62: xen: Information leak on AVX and/or LWP capable CPUs 5242a1b5-x86-xsave-initialize-extended-register-state-when-guests-enable-it.patch - bnc#840592 - VUL-0: CVE-2013-4355: XSA-63: xen: Information leaks through I/O instruction emulation CVE-2013-4355-xsa63.patch - bnc#840593 - VUL-0: CVE-2013-4356: XSA-64: xen: Memory accessible by 64-bit PV guests under live migration CVE-2013-4356-xsa64.patch - bnc#841766 - VUL-1: CVE-2013-4361: XSA-66: xen: Information leak through fbld instruction emulation CVE-2013-4361-xsa66.patch - bnc#833796 - L3: Xen: migration broken from xsave-capable to xsave-incapable host 52205e27-x86-xsave-initialization-improvements.patch 522dc0e6-x86-xsave-fix-migration-from-xsave-capable-to-xsave-incapable-host.patch - bnc#839600 - [HP BCS SLES11 Bug]: In HP’s UEFI x86_64 platform and sles11sp3 with xen environment, xen hypervisor will panic on multiple blades nPar. 523172d5-x86-fix-memory-cut-off-when-using-PFN-compression.patch - bnc#833251 - [HP BCS SLES11 Bug]: In HP’s UEFI x86_64 platform and with xen environment, in booting stage ,xen hypervisor will panic. 522d896b-x86-EFI-properly-handle-run-time-memory-regions-outside-the-1-1-map.patch - bnc#834751 - [HP BCS SLES11 Bug]: In xen, “shutdown –y 0 –h” cannot power off system 522d896b-x86-EFI-properly-handle-run-time-memory-regions-outside-the-1-1-map.patch OBS-URL: https://build.opensuse.org/package/show/Virtualization/xen?expand=0&rev=274
41 lines
1.4 KiB
Diff
41 lines
1.4 KiB
Diff
# Commit 66450c1d1ab3c4480bbba949113b95d1ab6a943a
|
|
# Date 2013-08-06 17:45:00 +0200
|
|
# Author Andrew Cooper <andrew.cooper3@citrix.com>
|
|
# Committer Jan Beulich <jbeulich@suse.com>
|
|
xen/conring: Write to console ring even if console lock is busted
|
|
|
|
console_lock_busted gets set when an NMI/MCE/Double Fault handler decides to
|
|
bring Xen down in an emergency. conring_puts() cannot block and does
|
|
not have problematic interactions with the console_lock.
|
|
|
|
Therefore, choosing to not put the string into the console ring simply means
|
|
that the kexec environment cant find any panic() message caused by an IST
|
|
interrupt, which is unhelpful for debugging purposes.
|
|
|
|
In the case that two pcpus fight with console_force_unlock(), having slightly
|
|
garbled strings in the console ring is far more useful than having nothing at
|
|
all.
|
|
|
|
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
|
|
Acked-by: Matt Wilson <msw@amazon.com>
|
|
Acked-by: Keir Fraser <keir@xen.org>
|
|
|
|
--- a/xen/drivers/char/console.c
|
|
+++ b/xen/drivers/char/console.c
|
|
@@ -463,12 +463,11 @@ static void __putstr(const char *str)
|
|
sercon_puts(str);
|
|
video_puts(str);
|
|
|
|
+ while ( (c = *str++) != '\0' )
|
|
+ putchar_console_ring(c);
|
|
+
|
|
if ( !console_locks_busted )
|
|
- {
|
|
- while ( (c = *str++) != '\0' )
|
|
- putchar_console_ring(c);
|
|
tasklet_schedule(¬ify_dom0_con_ring_tasklet);
|
|
- }
|
|
}
|
|
|
|
static int printk_prefix_check(char *p, char **pp)
|