Script 'mail_helper' called by obssrc
Hello community,

here is the log from the commit of package xen for openSUSE:Factory checked in 
at 2023-05-09 13:08:08
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Comparing /work/SRC/openSUSE:Factory/xen (Old)
 and      /work/SRC/openSUSE:Factory/.xen.new.1533 (New)
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Package is "xen"

Tue May  9 13:08:08 2023 rev:331 rq:1085553 version:4.17.1_02

Changes:
--------
--- /work/SRC/openSUSE:Factory/xen/xen.changes  2023-04-01 23:26:56.439318701 
+0200
+++ /work/SRC/openSUSE:Factory/.xen.new.1533/xen.changes        2023-05-09 
13:08:17.165359616 +0200
@@ -1,0 +2,57 @@
+Thu May  4 11:22:27 MDT 2023 - [email protected]
+
+- bsc#1210570 - gcc-13 realloc use-after-free analysis error
+  64525c61-tools-libs-guest-assist-gcc13s-realloc-analyzer.patch
+
+-------------------------------------------------------------------
+Fri Apr 28 14:53:15 MDT 2023 - [email protected]
+
+- bsc#1209237 - xen-syms doesn't contain debug-info
+  643e3810-CONFIG_DEBUG_INFO-no-EXPERT.patch
+  643e387f-xen-update-CONFIG_DEBUG_INFO-help-text.patch
+  6447a8fd-x86-EFI-permit-crash-dump-analysis.patch
+
+-------------------------------------------------------------------
+Thu Apr 27 11:40:25 MDT 2023 - [email protected]
+
+- Update to Xen 4.17.1 bug fix release (bsc#1027519)
+  xen-4.17.1-testing-src.tar.bz2
+  * No upstream changelog found in sources or webpage
+- Dropped patches contained in new tarball
+  63a03b73-VMX-VMExit-based-BusLock-detection.patch
+  63a03ba6-VMX-INTR_SHADOW_NMI-helper.patch
+  63a03bce-VMX-Notify-VMExit.patch
+  63a03e28-x86-high-freq-TSC-overflow.patch
+  63c05478-VMX-calculate-model-specific-LBRs-once.patch
+  63c05478-VMX-support-CPUs-without-model-specific-LBR.patch
+  63d24e91-tools-xenstore-revert-simplify-loop-handling.patch
+  63e53ac9-x86-CPUID-leaves-7-1-ecx-edx.patch
+  63e53ac9-x86-disable-CET-SS-when-fractured-updates.patch
+  63ebca9c-x86-spec-ctrl-Mitigate-Cross-Thread-Return-Address-Predictions.patch
+  63f4d045-x86-ucode-AMD-apply-early-on-all-threads.patch
+  63fe06e0-x86-ucode-AMD-apply-late-on-all-threads.patch
+  640f3035-x86-altp2m-help-gcc13.patch
+  641041e8-VT-d-constrain-IGD-check.patch
+  64104238-bunzip-gcc13.patch
+  6419697d-AMD-IOMMU-no-XT-x2APIC-phys.patch
+  64199e0c-x86-shadow-account-for-log-dirty-mode.patch
+  64199e0d-x86-HVM-bound-number-of-pca-regions.patch
+  64199e0e-x86-HVM-serialize-pca-list-manipulation.patch
+  64199e0f-x86-spec-ctrl-defer-CR4_PV32_RESTORE-for-CSTAR.patch
+  libxl.fix-guest-kexec-skip-cpuid-policy.patch
+  xsa430.patch
+
+-------------------------------------------------------------------
+Tue Apr 11 09:36:33 MDT 2023 - [email protected]
+
+- bsc#1210315 - VUL-0: CVE-2022-42335: xen: x86 shadow paging
+  arbitrary pointer dereference (XSA-430)
+  xsa430.patch
+
+-------------------------------------------------------------------
+Fri Mar 31 11:02:49 MDT 2023 - [email protected]
+
+- Not building the shim is correctly handled by --disable-pvshim
+  Drop disable-building-pv-shim.patch
+
+-------------------------------------------------------------------

Old:
----
  63a03b73-VMX-VMExit-based-BusLock-detection.patch
  63a03ba6-VMX-INTR_SHADOW_NMI-helper.patch
  63a03bce-VMX-Notify-VMExit.patch
  63a03e28-x86-high-freq-TSC-overflow.patch
  63c05478-VMX-calculate-model-specific-LBRs-once.patch
  63c05478-VMX-support-CPUs-without-model-specific-LBR.patch
  63d24e91-tools-xenstore-revert-simplify-loop-handling.patch
  63e53ac9-x86-CPUID-leaves-7-1-ecx-edx.patch
  63e53ac9-x86-disable-CET-SS-when-fractured-updates.patch
  63ebca9c-x86-spec-ctrl-Mitigate-Cross-Thread-Return-Address-Predictions.patch
  63f4d045-x86-ucode-AMD-apply-early-on-all-threads.patch
  63fe06e0-x86-ucode-AMD-apply-late-on-all-threads.patch
  640f3035-x86-altp2m-help-gcc13.patch
  641041e8-VT-d-constrain-IGD-check.patch
  64104238-bunzip-gcc13.patch
  6419697d-AMD-IOMMU-no-XT-x2APIC-phys.patch
  64199e0c-x86-shadow-account-for-log-dirty-mode.patch
  64199e0d-x86-HVM-bound-number-of-pca-regions.patch
  64199e0e-x86-HVM-serialize-pca-list-manipulation.patch
  64199e0f-x86-spec-ctrl-defer-CR4_PV32_RESTORE-for-CSTAR.patch
  disable-building-pv-shim.patch
  libxl.fix-guest-kexec-skip-cpuid-policy.patch
  xen-4.17.0-testing-src.tar.bz2

New:
----
  643e3810-CONFIG_DEBUG_INFO-no-EXPERT.patch
  643e387f-xen-update-CONFIG_DEBUG_INFO-help-text.patch
  6447a8fd-x86-EFI-permit-crash-dump-analysis.patch
  64525c61-tools-libs-guest-assist-gcc13s-realloc-analyzer.patch
  xen-4.17.1-testing-src.tar.bz2

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Other differences:
------------------
++++++ xen.spec ++++++
--- /var/tmp/diff_new_pack.U87ehu/_old  2023-05-09 13:08:19.381372805 +0200
+++ /var/tmp/diff_new_pack.U87ehu/_new  2023-05-09 13:08:19.385372829 +0200
@@ -28,7 +28,7 @@
 
 Name:           xen
 ExclusiveArch:  %ix86 x86_64 aarch64
-%define xen_build_dir xen-4.17.0-testing
+%define xen_build_dir xen-4.17.1-testing
 #
 %define with_gdbsx 0
 %define with_dom0_support 0
@@ -119,12 +119,12 @@
 %endif
 Provides:       installhint(reboot-needed)
 
-Version:        4.17.0_06
+Version:        4.17.1_02
 Release:        0
 Summary:        Xen Virtualization: Hypervisor (aka VMM aka Microkernel)
 License:        GPL-2.0-only
 Group:          System/Kernel
-Source0:        xen-4.17.0-testing-src.tar.bz2
+Source0:        xen-4.17.1-testing-src.tar.bz2
 Source1:        stubdom.tar.bz2
 Source2:        mini-os.tar.bz2
 Source3:        xen-utils-0.1.tar.bz2
@@ -155,27 +155,11 @@
 # For xen-libs
 Source99:       baselibs.conf
 # Upstream patches
-Patch1:         63a03b73-VMX-VMExit-based-BusLock-detection.patch
-Patch2:         63a03ba6-VMX-INTR_SHADOW_NMI-helper.patch
-Patch3:         63a03bce-VMX-Notify-VMExit.patch
-Patch4:         63a03e28-x86-high-freq-TSC-overflow.patch
-Patch5:         63c05478-VMX-calculate-model-specific-LBRs-once.patch
-Patch6:         63c05478-VMX-support-CPUs-without-model-specific-LBR.patch
-Patch7:         63d24e91-tools-xenstore-revert-simplify-loop-handling.patch
-Patch8:         
63e4da00-dont-log-errors-when-trying-to-load-PVH-xenstore-stubdom.patch
-Patch9:         63e53ac9-x86-CPUID-leaves-7-1-ecx-edx.patch
-Patch10:        63e53ac9-x86-disable-CET-SS-when-fractured-updates.patch
-Patch11:        
63ebca9c-x86-spec-ctrl-Mitigate-Cross-Thread-Return-Address-Predictions.patch
-Patch12:        63f4d045-x86-ucode-AMD-apply-early-on-all-threads.patch
-Patch13:        63fe06e0-x86-ucode-AMD-apply-late-on-all-threads.patch
-Patch14:        640f3035-x86-altp2m-help-gcc13.patch
-Patch15:        641041e8-VT-d-constrain-IGD-check.patch
-Patch16:        64104238-bunzip-gcc13.patch
-Patch17:        6419697d-AMD-IOMMU-no-XT-x2APIC-phys.patch
-Patch18:        64199e0c-x86-shadow-account-for-log-dirty-mode.patch
-Patch19:        64199e0d-x86-HVM-bound-number-of-pca-regions.patch
-Patch20:        64199e0e-x86-HVM-serialize-pca-list-manipulation.patch
-Patch21:        64199e0f-x86-spec-ctrl-defer-CR4_PV32_RESTORE-for-CSTAR.patch
+Patch1:         
63e4da00-dont-log-errors-when-trying-to-load-PVH-xenstore-stubdom.patch
+Patch2:         643e3810-CONFIG_DEBUG_INFO-no-EXPERT.patch
+Patch3:         643e387f-xen-update-CONFIG_DEBUG_INFO-help-text.patch
+Patch4:         6447a8fd-x86-EFI-permit-crash-dump-analysis.patch
+Patch5:         64525c61-tools-libs-guest-assist-gcc13s-realloc-analyzer.patch
 # EMBARGOED security fixes
 # libxc
 Patch301:       libxc-bitmap-long.patch
@@ -217,8 +201,7 @@
 Patch405:       xen-arch-kconfig-nr_cpus.patch
 Patch406:       suse-xendomains-service.patch
 Patch407:       replace-obsolete-network-configuration-commands-in-s.patch
-Patch408:       disable-building-pv-shim.patch
-Patch409:       ignore-ip-command-script-errors.patch
+Patch408:       ignore-ip-command-script-errors.patch
 # Needs to go upstream
 Patch420:       suspend_evtchn_lock.patch
 Patch421:       vif-route.patch
@@ -231,7 +214,6 @@
 Patch455:       pygrub-boot-legacy-sles.patch
 Patch456:       pygrub-handle-one-line-menu-entries.patch
 Patch457:       aarch64-rename-PSR_MODE_ELxx-to-match-linux-headers.patch
-Patch460:       libxl.fix-guest-kexec-skip-cpuid-policy.patch
 Patch461:       libxl.max_event_channels.patch
 Patch463:       libxl.add-option-to-disable-disk-cache-flushes-in-qdisk.patch
 Patch464:       libxl.pvscsi.patch
@@ -929,7 +911,6 @@
        -name qemu-img-xen -o \
        -name qemu-nbd-xen -o \
        -name palcode-clipper -o \
-       -name xen-shim-syms -o \
        -name "*.dtb" -o \
        -name "openbios-*" -o \
        -name "petalogix*" -o \

++++++ 643e3810-CONFIG_DEBUG_INFO-no-EXPERT.patch ++++++
Subject: xen: move CONFIG_DEBUG_INFO out of EXPERT section
From: Juergen Gross [email protected] Tue Apr 18 08:26:24 2023 +0200
Date: Tue Apr 18 08:26:24 2023 +0200:
Git: 14a9f07d99f314a86fc4e94d5e5577fbf3f8a3ef

In order to support hypervisor analysis of crash dumps, xen-syms needs
to contain debug_info. It should be allowed to configure the hypervisor
to be built with CONFIG_DEBUG_INFO in non-debug builds without having
to enable EXPERT.

Using a rather oldish gcc (7.5) it was verified that code generation
doesn't really differ between CONFIG_DEBUG_INFO on or off without
CONFIG_DEBUG being set (only observed differences were slightly
different symbol addresses, verified via "objdump -d", resulting from
the different config.gz in the binary). The old gcc version selection
was based on the assumption, that newer gcc won't regress in this
regard.

So move CONFIG_DEBUG_INFO out of the section guarded by EXPERT.

It should be mentioned that there have been reports that the linking
of the xen.efi might take considerably longer with CONFIG_DEBUG_INFO
selected when using newer binutils.

Signed-off-by: Juergen Gross <[email protected]>
Tested-by: Dietmar Hahn <[email protected]>
Acked-by: Jan Beulich <[email protected]>

diff --git a/xen/Kconfig.debug b/xen/Kconfig.debug
index fad3050d4f..279dbe8274 100644
--- a/xen/Kconfig.debug
+++ b/xen/Kconfig.debug
@@ -28,13 +28,6 @@ config GDBSX
          If you want to enable support for debugging guests from dom0 via
          gdbsx then say Y.
 
-config DEBUG_INFO
-       bool "Compile Xen with debug info"
-       default y
-       ---help---
-         If you say Y here the resulting Xen will include debugging info
-         resulting in a larger binary image.
-
 config FRAME_POINTER
        bool "Compile Xen with frame pointers"
        default DEBUG
@@ -132,4 +125,11 @@ source "arch/$(SRCARCH)/Kconfig.debug"
 
 endif # DEBUG || EXPERT
 
+config DEBUG_INFO
+       bool "Compile Xen with debug info"
+       default DEBUG
+       help
+         If you say Y here the resulting Xen will include debugging info
+         resulting in a larger binary image.
+
 endmenu

++++++ 643e387f-xen-update-CONFIG_DEBUG_INFO-help-text.patch ++++++
Subject: xen: update CONFIG_DEBUG_INFO help text
From: Juergen Gross [email protected] Tue Apr 18 08:28:15 2023 +0200
Date: Tue Apr 18 08:28:15 2023 +0200:
Git: cbe828581b4a1717a4331b754c25a27a41d1bc58

Update the help text of the CONFIG_DEBUG_INFO option to be a little
bit more specific.

Signed-off-by: Juergen Gross <[email protected]>
Acked-by: Jan Beulich <[email protected]>

diff --git a/xen/Kconfig.debug b/xen/Kconfig.debug
index 279dbe8274..94e818ee09 100644
--- a/xen/Kconfig.debug
+++ b/xen/Kconfig.debug
@@ -129,7 +129,15 @@ config DEBUG_INFO
        bool "Compile Xen with debug info"
        default DEBUG
        help
-         If you say Y here the resulting Xen will include debugging info
-         resulting in a larger binary image.
+         Say Y here if you want to build Xen with debug information. This
+         information is needed e.g. for doing crash dump analysis of the
+         hypervisor via the "crash" tool.
+         Saying Y will increase the size of the xen-syms and xen.efi
+         binaries. In case the space on the EFI boot partition is rather
+         limited, you may want to install a stripped variant of xen.efi in
+         the EFI boot partition (look for "INSTALL_EFI_STRIP" in
+         docs/misc/efi.pandoc for more information - when not using
+         "make install-xen" for installing xen.efi, stripping needs to be
+         done outside the Xen build environment).
 
 endmenu

++++++ 6447a8fd-x86-EFI-permit-crash-dump-analysis.patch ++++++
Subject: x86: add support for crash dump analysis with xen.efi
From: Juergen Gross [email protected] Tue Apr 25 12:18:37 2023 +0200
Date: Tue Apr 25 12:18:37 2023 +0200:
Git: f514bab30ef8d4ade77a27c926e283c9bbbf9ffd

Today it is not possible to analyse crash dumps of a system in
hypervisor mode when it had been booted via EFI, as the crash utility
doesn't understand the file format of xen.efi.

This can easily be solved by creating an ELF file from xen.efi via
objcopy. Using that file as name list for crash enables the user to
analyse the dump in hypervisor mode. Note that crash isn't happy with
a file containing no text and data, so using --only-keep-debug is not
an option.

Signed-off-by: Juergen Gross <[email protected]>
Reviewed-by: Jan Beulich <[email protected]>

--- a/xen/Makefile
+++ b/xen/Makefile
@@ -502,9 +502,11 @@ _install: $(TARGET)$(CONFIG_XEN_INSTALL_
        if [ -r $(TARGET).efi -a -n '$(EFI_DIR)' ]; then \
                [ -d $(D)$(EFI_DIR) ] || $(INSTALL_DIR) $(D)$(EFI_DIR); \
                $(INSTALL_DATA) $(TARGET).efi 
$(D)$(EFI_DIR)/$(T)-$(XEN_FULLVERSION).efi; \
-               if [ -e $(TARGET).efi.map ]; then \
-                       $(INSTALL_DATA) $(TARGET).efi.map 
$(D)$(DEBUG_DIR)/$(T)-$(XEN_FULLVERSION).efi.map; \
-               fi; \
+               for x in map elf; do \
+                       if [ -e $(TARGET).efi.$$x ]; then \
+                               $(INSTALL_DATA) $(TARGET).efi.$$x 
$(D)$(DEBUG_DIR)/$(T)-$(XEN_FULLVERSION).efi.$$x; \
+                       fi; \
+               done; \
                ln -sf $(T)-$(XEN_FULLVERSION).efi 
$(D)$(EFI_DIR)/$(T)-$(XEN_VERSION).$(XEN_SUBVERSION).efi; \
                ln -sf $(T)-$(XEN_FULLVERSION).efi 
$(D)$(EFI_DIR)/$(T)-$(XEN_VERSION).efi; \
                ln -sf $(T)-$(XEN_FULLVERSION).efi $(D)$(EFI_DIR)/$(T).efi; \
@@ -539,6 +541,7 @@ _uninstall:
        rm -f $(D)$(DEBUG_DIR)/$(T)-syms-$(XEN_FULLVERSION).map
        rm -f $(D)$(EFI_DIR)/$(T)-$(XEN_FULLVERSION).efi
        rm -f $(D)$(EFI_DIR)/$(T)-$(XEN_VERSION).$(XEN_SUBVERSION).efi
+       rm -f $(D)$(DEBUG_DIR)/$(T)-$(XEN_FULLVERSION).efi.elf
        rm -f $(D)$(DEBUG_DIR)/$(T)-$(XEN_FULLVERSION).efi.map
        rm -f $(D)$(EFI_DIR)/$(T)-$(XEN_VERSION).efi
        rm -f $(D)$(EFI_DIR)/$(T).efi
@@ -569,7 +572,7 @@ _clean:
                -o -name '*.lex.c' -o -name '*.tab.[ch]' -o -name 
'*.c.cppcheck' \
                -o -name "*.gcno" -o -name ".*.cmd" -o -name "lib.a" \) -exec 
rm -f {} \;
        rm -f include/asm $(TARGET) $(TARGET).gz $(TARGET)-syms 
$(TARGET)-syms.map
-       rm -f $(TARGET).efi $(TARGET).efi.map $(TARGET).efi.stripped
+       rm -f $(TARGET).efi $(TARGET).efi.map $(TARGET).efi.elf 
$(TARGET).efi.stripped
        rm -f asm-offsets.s arch/*/include/asm/asm-offsets.h
        rm -f .banner .allconfig.tmp include/xen/compile.h
        rm -f cppcheck-misra.* xen-cppcheck.xml
--- a/xen/arch/x86/Makefile
+++ b/xen/arch/x86/Makefile
@@ -224,6 +224,9 @@ endif
              $(@D)/.$(@F).1r.o $(@D)/.$(@F).1s.o $(orphan-handling-y) 
$(note_file_option) -o $@
        $(NM) -pa --format=sysv $(@D)/$(@F) \
                | $(objtree)/tools/symbols --all-symbols --xensyms --sysv 
--sort >$(@D)/$(@F).map
+ifeq ($(CONFIG_DEBUG_INFO),y)
+       $(if $(filter --strip-debug,$(EFI_LDFLAGS)),:$(space))$(OBJCOPY) -O 
elf64-x86-64 $@ [email protected]
+endif
        rm -f $(@D)/.$(@F).[0-9]* $(@D)/..$(@F).[0-9]*
 ifeq ($(CONFIG_XEN_IBT),y)
        $(SHELL) $(srctree)/tools/check-endbr.sh $@

++++++ 64525c61-tools-libs-guest-assist-gcc13s-realloc-analyzer.patch ++++++
Subject: tools/libs/guest: assist gcc13's realloc analyzer
From: Olaf Hering [email protected] Wed May 3 15:06:41 2023 +0200
Date: Wed May 3 15:06:41 2023 +0200:
Git: 99a9c3d7141063ae3f357892c6181cfa3be8a280

gcc13 fails to track the allocated memory in backup_ptes:

xg_offline_page.c: In function 'backup_ptes':
xg_offline_page.c:191:13: error: pointer 'orig' may be used after 'realloc' 
[-Werror=use-after-free]
  191 |             free(orig);

Assist the analyzer by slightly rearranging the code:
In case realloc succeeds, the previous allocation is either extended
or released internally. In case realloc fails, the previous allocation
is left unchanged. Return an error in this case, the caller will
release the currently allocated memory in its error path.

http://bugzilla.suse.com/show_bug.cgi?id=1210570

Signed-off-by: Olaf Hering <[email protected]>
Reviewed-by: Juergen Gross <[email protected]>
Compile-tested-by: Jason Andryuk <[email protected]>
Acked-by: Jan Beulich <[email protected]>

diff --git a/tools/libs/guest/xg_offline_page.c 
b/tools/libs/guest/xg_offline_page.c
index ccd0299f0f..8f0a252417 100644
--- a/tools/libs/guest/xg_offline_page.c
+++ b/tools/libs/guest/xg_offline_page.c
@@ -181,18 +181,14 @@ static int backup_ptes(xen_pfn_t table_mfn, int offset,
 
     if (backup->max == backup->cur)
     {
-        void *orig = backup->entries;
+        void *entries = realloc(backup->entries, backup->max * 2 *
+                                sizeof(struct pte_backup_entry));
 
-        backup->entries = realloc(
-            orig, backup->max * 2 * sizeof(struct pte_backup_entry));
-
-        if (backup->entries == NULL)
-        {
-            free(orig);
+        if (entries == NULL)
             return -1;
-        }
-        else
-            backup->max *= 2;
+
+        backup->entries = entries;
+        backup->max *= 2;
     }
 
     backup->entries[backup->cur].table_mfn = table_mfn;

++++++ libxc-sr-abort_if_busy.patch ++++++
--- /var/tmp/diff_new_pack.U87ehu/_old  2023-05-09 13:08:19.585374019 +0200
+++ /var/tmp/diff_new_pack.U87ehu/_new  2023-05-09 13:08:19.589374043 +0200
@@ -93,7 +93,7 @@
      dss->checkpointed_stream = LIBXL_CHECKPOINTED_STREAM_NONE;
 --- a/tools/libs/light/libxl_internal.h
 +++ b/tools/libs/light/libxl_internal.h
-@@ -3653,9 +3653,11 @@ struct libxl__domain_save_state {
+@@ -3654,9 +3654,11 @@ struct libxl__domain_save_state {
      libxl_domain_type type;
      int live;
      int debug;

++++++ libxc-sr-max_iters.patch ++++++
--- /var/tmp/diff_new_pack.U87ehu/_old  2023-05-09 13:08:19.601374115 +0200
+++ /var/tmp/diff_new_pack.U87ehu/_new  2023-05-09 13:08:19.605374139 +0200
@@ -77,7 +77,7 @@
      dss->checkpointed_stream = LIBXL_CHECKPOINTED_STREAM_NONE;
 --- a/tools/libs/light/libxl_internal.h
 +++ b/tools/libs/light/libxl_internal.h
-@@ -3654,6 +3654,7 @@ struct libxl__domain_save_state {
+@@ -3655,6 +3655,7 @@ struct libxl__domain_save_state {
      int live;
      int debug;
      int checkpointed_stream;

++++++ libxc-sr-min_remaining.patch ++++++
--- /var/tmp/diff_new_pack.U87ehu/_old  2023-05-09 13:08:19.613374186 +0200
+++ /var/tmp/diff_new_pack.U87ehu/_new  2023-05-09 13:08:19.617374211 +0200
@@ -82,7 +82,7 @@
      dss->checkpointed_stream = LIBXL_CHECKPOINTED_STREAM_NONE;
 --- a/tools/libs/light/libxl_internal.h
 +++ b/tools/libs/light/libxl_internal.h
-@@ -3655,6 +3655,7 @@ struct libxl__domain_save_state {
+@@ -3656,6 +3656,7 @@ struct libxl__domain_save_state {
      int debug;
      int checkpointed_stream;
      uint32_t max_iters;

++++++ libxl.LIBXL_HOTPLUG_TIMEOUT.patch ++++++
--- /var/tmp/diff_new_pack.U87ehu/_old  2023-05-09 13:08:19.685374614 +0200
+++ /var/tmp/diff_new_pack.U87ehu/_new  2023-05-09 13:08:19.689374638 +0200
@@ -290,7 +290,7 @@
  
  #include <xenevtchn.h>
  #include <xenstore.h>
-@@ -1627,6 +1628,7 @@ struct libxl__xswait_state {
+@@ -1628,6 +1629,7 @@ struct libxl__xswait_state {
      const char *what; /* for error msgs: noun phrase, what we're waiting for 
*/
      const char *path;
      int timeout_ms; /* as for poll(2) */
@@ -298,7 +298,7 @@
      libxl__xswait_callback *callback;
      /* remaining fields are private to xswait */
      libxl__ev_time time_ev;
-@@ -2705,6 +2707,7 @@ struct libxl__async_exec_state {
+@@ -2706,6 +2708,7 @@ struct libxl__async_exec_state {
      char **args; /* execution arguments */
      char **env; /* execution environment */
  
@@ -306,7 +306,7 @@
      /* private */
      libxl__ev_time time;
      libxl__ev_child child;
-@@ -4880,6 +4883,9 @@ _hidden int libxl__domain_set_paging_mem
+@@ -4881,6 +4884,9 @@ _hidden int libxl__domain_set_paging_mem
  
  #endif
  

++++++ libxl.pvscsi.patch ++++++
--- /var/tmp/diff_new_pack.U87ehu/_old  2023-05-09 13:08:19.709374757 +0200
+++ /var/tmp/diff_new_pack.U87ehu/_new  2023-05-09 13:08:19.713374781 +0200
@@ -230,7 +230,7 @@
 ===================================================================
 --- xen-4.17.0-testing.orig/tools/libs/light/libxl_internal.h
 +++ xen-4.17.0-testing/tools/libs/light/libxl_internal.h
-@@ -4012,6 +4012,7 @@ extern const libxl__device_type libxl__v
+@@ -4013,6 +4013,7 @@ extern const libxl__device_type libxl__v
  extern const libxl__device_type libxl__disk_devtype;
  extern const libxl__device_type libxl__nic_devtype;
  extern const libxl__device_type libxl__vtpm_devtype;

++++++ xen-4.17.0-testing-src.tar.bz2 -> xen-4.17.1-testing-src.tar.bz2 ++++++
++++ 5467 lines of diff (skipped)

++++++ xen.libxl.dmmd.patch ++++++
--- /var/tmp/diff_new_pack.U87ehu/_old  2023-05-09 13:08:22.809393209 +0200
+++ /var/tmp/diff_new_pack.U87ehu/_new  2023-05-09 13:08:22.813393233 +0200
@@ -110,7 +110,7 @@
 ===================================================================
 --- xen-4.17.0-testing.orig/tools/libs/light/libxl_internal.h
 +++ xen-4.17.0-testing/tools/libs/light/libxl_internal.h
-@@ -2071,6 +2071,10 @@ _hidden char *libxl__object_to_json(libx
+@@ -2072,6 +2072,10 @@ _hidden char *libxl__object_to_json(libx
  _hidden int libxl__cpuid_legacy(libxl_ctx *ctx, uint32_t domid, bool retore,
                                  libxl_domain_build_info *info);
  

Reply via email to