similar to: [xen-unstable test] 9061: regressions - FAIL

From: Lasse Collin <lasse.collin@tukaani.org> Return value of rc->fill() is checked in rc_read() and error() is called when needed, but then the code continues as if nothing had happened. rc_read() is a void function and it''s on the top of performance critical call stacks, so propagating the error code via return values doesn''t sound like the best fix. It seems better

From: Lasse Collin <lasse.collin@tukaani.org> The code assumes that the input is valid and not truncated. Add checks to avoid reading past the end of the input buffer. Change the type of "skip" from u8 to int to fix a possible integer overflow. Signed-off-by: Lasse Collin <lasse.collin@tukaani.org> Signed-off-by: Jan Beulich <jbeulich@suse.com> ---

The IRQ handling code requires pcidevs_lock to be held only for MSI interrupts. As the handling of which was now fully moved into msi.c (i.e. while applying fine without, the patch needs to be applied after the one titled "x86: split MSI IRQ chip"), io_apic.c now also doesn''t need to include PCI headers anymore. Signed-off-by: Jan Beulich <jbeulich@suse.com> ---

Hello, the included XZ Utils source code contains an incorrect use of the restrict keyword. This leads to data corruption under certain circumstances. For a short discussion of the problem see http://sourceforge.net/projects/lzmautils/forums/forum/708858/topic/3306733 This was fixed in the XZ Utils git repository in commit commit 49cfc8d392cf535f8dd10233225b1fc726fec9ef Author: Lasse

Under the assumption that in these cases recurring faults aren''t a security issue and it can be expected that the drivers there are going to try to take care of the problem. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/drivers/passthrough/amd/iommu_init.c +++ b/xen/drivers/passthrough/amd/iommu_init.c @@ -625,6 +625,18 @@ static void parse_event_log_entry(struct

flight 10504 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/10504/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-amd64-xl-sedf 14 guest-localmigrate/x10 fail REGR. vs. 10491 test-amd64-i386-win 7 windows-install fail REGR. vs. 10491 test-amd64-amd64-xl-winxpsp3 7 windows-install fail REGR. vs. 10491

flight 10511 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/10511/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-amd64-xl-sedf 14 guest-localmigrate/x10 fail in 10504 REGR. vs. 10491 Tests which are failing intermittently (not blocking): test-amd64-amd64-xl-sedf 13 guest-localmigrate.2 fail pass in 10504 test-i386-i386-win

flight 6714 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/6714/ Regressions :-( Tests which did not succeed and are blocking: build-amd64-oldkern 4 xen-build fail REGR. vs. 6658 build-amd64 4 xen-build fail REGR. vs. 6658 build-i386-oldkern 4 xen-build fail REGR. vs. 6658

flight 12252 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12252/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-oldkern 4 xen-build fail REGR. vs. 12249 build-i386 4 xen-build fail REGR. vs. 12249 Tests which are failing intermittently

flight 9800 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/9800/ Regressions :-( Tests which did not succeed and are blocking: test-amd64-amd64-xl-sedf 14 guest-localmigrate/x10 fail REGR. vs. 9789 Tests which are failing intermittently (not blocking): test-amd64-i386-xl-win-vcpus1 12 guest-localmigrate/x10 fail pass in 9799 test-amd64-i386-win

On 18.02.20 22:03, Thomas Gleixner wrote: > Juergen Gross <jgross at suse.com> writes: >> Commit 111e7b15cf10f6 ("x86/ioperm: Extend IOPL config to control >> ioperm() as well") reworked the iopl syscall to use I/O bitmaps. >> >> Unfortunately this broke Xen PV domains using that syscall as there >> is currently no I/O bitmap support in PV domains.

On 18.02.20 22:03, Thomas Gleixner wrote: > Juergen Gross <jgross at suse.com> writes: >> Commit 111e7b15cf10f6 ("x86/ioperm: Extend IOPL config to control >> ioperm() as well") reworked the iopl syscall to use I/O bitmaps. >> >> Unfortunately this broke Xen PV domains using that syscall as there >> is currently no I/O bitmap support in PV domains.

flight 13925 xen-4.2-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/13925/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-qemuu-rhel6hvm-amd 9 guest-start.2 fail REGR. vs. 13922 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-sedf-pin 10 guest-saverestore fail

Juergen Gross <jgross at suse.com> writes: > Commit 111e7b15cf10f6 ("x86/ioperm: Extend IOPL config to control > ioperm() as well") reworked the iopl syscall to use I/O bitmaps. > > Unfortunately this broke Xen PV domains using that syscall as there > is currently no I/O bitmap support in PV domains. > > Add I/O bitmap support via a new paravirt function

Commit 111e7b15cf10f6 ("x86/ioperm: Extend IOPL config to control ioperm() as well") reworked the iopl syscall to use I/O bitmaps. Unfortunately this broke Xen PV domains using that syscall as there is currently no I/O bitmap support in PV domains. Add I/O bitmap support via a new paravirt function update_io_bitmap which Xen PV domains can use to update their I/O bitmaps via a

Commit 111e7b15cf10f6 ("x86/ioperm: Extend IOPL config to control ioperm() as well") reworked the iopl syscall to use I/O bitmaps. Unfortunately this broke Xen PV domains using that syscall as there is currently no I/O bitmap support in PV domains. Add I/O bitmap support via a new paravirt function update_io_bitmap which Xen PV domains can use to update their I/O bitmaps via a

Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/docs/misc/xen-command-line.markdown +++ b/docs/misc/xen-command-line.markdown @@ -785,6 +785,19 @@ Specify the per-cpu trace buffer size in > `= unstable | skewed` ### ucode +> `= <integer>` + +Specify the CPU microcode update blob module index. When positive, this +specifies the n-th module (in the GrUB entry, zero based)

flight 12413 xen-4.0-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/12413/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 4 xen-build fail REGR. vs. 12202 build-amd64-pvops 4 kernel-build fail REGR. vs. 12202 build-amd64-oldkern 4

flight 13383 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/13383/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-pair 16 guest-start fail REGR. vs. 13379 Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl-qemuu-win7-amd64 12

flight 10626 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/10626/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-multivcpu 16 guest-start.2 fail in 10623 REGR. vs. 10621 Tests which are failing intermittently (not blocking): test-amd64-i386-rhel6hvm-intel 4 xen-install fail