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
43 lines
1.5 KiB
Diff
43 lines
1.5 KiB
Diff
# Commit 0f4cb23c3ea5b987c49c9a9368e7a0d505ec064f
|
|
# Date 2013-08-30 10:40:48 +0200
|
|
# Author Andrew Cooper <andrew.cooper3@citrix.com>
|
|
# Committer Jan Beulich <jbeulich@suse.com>
|
|
public/hvm_xs_strings.h: Fix ABI regression for OEM SMBios strings
|
|
|
|
The old code for OEM SMBios strings was:
|
|
|
|
char path[20] = "bios-strings/oem-XX";
|
|
path[(sizeof path) - 3] = '0' + ((i < 10) ? i : i / 10);
|
|
path[(sizeof path) - 2] = (i < 10) ? '\0' : '0' + (i % 10);
|
|
|
|
Where oem-1 thru 9 specifically had no leading 0.
|
|
|
|
However, the definition of HVM_XS_OEM_STRINGS specifically requires leading
|
|
0s.
|
|
|
|
This regression was introduced by the combination of c/s 4d23036e709627 and
|
|
e64c3f71ceb662
|
|
|
|
I realise that this patch causes a change to the public headers. However I
|
|
feel it is justified as:
|
|
|
|
* All toolstacks used to have to embed the magic string (and almost certainly
|
|
still do)
|
|
* If by some miriacle a new toolstack has started using the new define will
|
|
continue to work.
|
|
* The only intree consumer of the define is hvmloader itself.
|
|
|
|
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
|
|
Acked-by: Keir Fraser <keir@xen.org>
|
|
|
|
--- a/xen/include/public/hvm/hvm_xs_strings.h
|
|
+++ b/xen/include/public/hvm/hvm_xs_strings.h
|
|
@@ -75,6 +75,6 @@
|
|
/* 1 to 99 OEM strings can be set in xenstore using values of the form
|
|
* below. These strings will be loaded into the SMBIOS type 11 structure.
|
|
*/
|
|
-#define HVM_XS_OEM_STRINGS "bios-strings/oem-%02d"
|
|
+#define HVM_XS_OEM_STRINGS "bios-strings/oem-%d"
|
|
|
|
#endif /* __XEN_PUBLIC_HVM_HVM_XS_STRINGS_H__ */
|