[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-commits] [qemu/qemu] b115ea: gitlab-ci.yml: Add openSUSE Leap 15.2
|
From: |
Peter Maydell |
|
Subject: |
[Qemu-commits] [qemu/qemu] b115ea: gitlab-ci.yml: Add openSUSE Leap 15.2 for gitlab C... |
|
Date: |
Mon, 11 Jan 2021 10:02:05 -0800 |
Branch: refs/heads/master
Home: https://github.com/qemu/qemu
Commit: b115ea3a0d24e12da9025faef5b695d44a552228
https://github.com/qemu/qemu/commit/b115ea3a0d24e12da9025faef5b695d44a552228
Author: Cho, Yu-Chen <acho@suse.com>
Date: 2021-01-11 (Mon, 11 Jan 2021)
Changed paths:
M .gitlab-ci.d/containers.yml
M .gitlab-ci.yml
A tests/docker/dockerfiles/opensuse-leap.docker
Log Message:
-----------
gitlab-ci.yml: Add openSUSE Leap 15.2 for gitlab CI/CD
Add build-system-opensuse jobs and opensuse-leap.docker dockerfile.
Use openSUSE Leap 15.2 container image in the gitlab-CI.
Signed-off-by: Cho, Yu-Chen <acho@suse.com>
Tested-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
Reviewed-by: Wainer dos Santos Moschetta <wainersm@redhat.com>
Message-Id: <20201229085046.8536-1-acho@suse.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: 661465c2e0977f2af995c92eb25ea47c4e9bed3f
https://github.com/qemu/qemu/commit/661465c2e0977f2af995c92eb25ea47c4e9bed3f
Author: Gan Qixin <ganqixin@huawei.com>
Date: 2021-01-11 (Mon, 11 Jan 2021)
Changed paths:
M tests/qtest/libqtest.c
Log Message:
-----------
qtest/libqtest: fix heap-buffer-overflow in qtest_cb_for_every_machine()
When the length of mname is less than 5, memcpy("xenfv", mname, 5) will cause
heap buffer overflow. Therefore, use strncmp to avoid this problem.
The asan showed stack:
ERROR: AddressSanitizer: heap-buffer-overflow on address 0x60200000f2f4 at
pc 0x7f65d8cc2225 bp 0x7ffe93cc5a60 sp 0x7ffe93cc5208 READ of size 5 at
0x60200000f2f4 thread T0
#0 0x7f65d8cc2224 in memcmp (/lib64/libasan.so.5+0xdf224)
#1 0x5632c20be95b in qtest_cb_for_every_machine tests/qtest/libqtest.c:1282
#2 0x5632c20b7995 in main tests/qtest/test-hmp.c:160
#3 0x7f65d88fed42 in __libc_start_main (/lib64/libc.so.6+0x26d42)
#4 0x5632c20b72cd in _start (build/tests/qtest/test-hmp+0x542cd)
Reported-by: Euler Robot <euler.robot@huawei.com>
Signed-off-by: Gan Qixin <ganqixin@huawei.com>
Reviewed-by: Laurent Vivier <lvivier@redhat.com>
Message-Id: <20210106050625.518041-1-ganqixin@huawei.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: 124bd3e0a894b5f18ba743084895c081ab93fc86
https://github.com/qemu/qemu/commit/124bd3e0a894b5f18ba743084895c081ab93fc86
Author: Philippe Mathieu-Daudé <f4bug@amsat.org>
Date: 2021-01-11 (Mon, 11 Jan 2021)
Changed paths:
M util/oslib-win32.c
Log Message:
-----------
util/oslib-win32: Fix _aligned_malloc() arguments order
Commit dfbd0b873a8 inadvertently swapped the arguments
of _aligned_malloc(), correct it to fix [*]:
G_TEST_SRCDIR=C:/Users/ContainerAdministrator/AppData/Local/Temp/cirrus-ci-build/tests
G_TEST_BUILDDIR=C:/Users/ContainerAdministrator/AppData/Local/Temp/cirrus-ci-build/build/tests
tests/test-qht.exe --tap -k
ERROR test-qht - too few tests run (expected 2, got 0)
make: *** [Makefile.mtest:256: run-test-30] Error 1
[*] https://cirrus-ci.com/task/6055645751279616?command=test#L593
Fixes: dfbd0b873a8 ("util/oslib-win32: Use _aligned_malloc for
qemu_try_memalign")
Reported-by: Yonggang Luo <luoyonggang@gmail.com>
Reported-by: Volker Rümelin <vr_qemu@t-online.de>
Suggested-by: Volker Rümelin <vr_qemu@t-online.de>
Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
Reviewed-by: Yonggang Luo <luoyonggang@gmail.com>
Message-Id: <20210111001606.1122983-1-f4bug@amsat.org>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: 22ec0c696fd28e8978d0d64dd038eed33b974366
https://github.com/qemu/qemu/commit/22ec0c696fd28e8978d0d64dd038eed33b974366
Author: Qiuhao Li <Qiuhao.Li@outlook.com>
Date: 2021-01-11 (Mon, 11 Jan 2021)
Changed paths:
M scripts/oss-fuzz/minimize_qtest_trace.py
Log Message:
-----------
fuzz: accelerate non-crash detection
We spend much time waiting for the timeout program during the minimization
process until it passes a time limit. This patch hacks the CLOSED (indicates
the redirection file closed) notification in QTest's output if it doesn't
crash.
Test with quadrupled trace input at:
https://bugs.launchpad.net/qemu/+bug/1890333/comments/1
Original version:
real 1m37.246s
user 0m13.069s
sys 0m8.399s
Refined version:
real 0m45.904s
user 0m16.874s
sys 0m10.042s
Note:
Sometimes the mutated or the same trace may trigger a different crash
summary (second-to-last line) but indicates the same bug. For example, Bug
1910826 [1], which will trigger a stack overflow, may output summaries
like:
SUMMARY: AddressSanitizer: stack-overflow
/home/qiuhao/hack/qemu/build/../softmmu/physmem.c:488 in
flatview_do_translate
or
SUMMARY: AddressSanitizer: stack-overflow
(/home/qiuhao/hack/qemu/build/qemu-system-i386+0x27ca049) in __asan_memcpy
Etc.
If we use the whole summary line as the token, we may be prevented from
further minimization. So in this patch, we only use the first three words
which indicate the type of crash:
SUMMARY: AddressSanitizer: stack-overflow
[1] https://bugs.launchpad.net/qemu/+bug/1910826
Signed-off-by: Qiuhao Li <Qiuhao.Li@outlook.com>
Reviewed-by: Alexander Bulekov <alxndr@bu.edu>
Tested-by: Alexander Bulekov <alxndr@bu.edu>
Message-Id:
<SYCPR01MB350251DC04003450348FAF68FCAB0@SYCPR01MB3502.ausprd01.prod.outlook.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: 7b339f287fb73a628f0862823b880a6145faa6ec
https://github.com/qemu/qemu/commit/7b339f287fb73a628f0862823b880a6145faa6ec
Author: Qiuhao Li <Qiuhao.Li@outlook.com>
Date: 2021-01-11 (Mon, 11 Jan 2021)
Changed paths:
M scripts/oss-fuzz/minimize_qtest_trace.py
Log Message:
-----------
fuzz: double the IOs to remove for every loop
Instead of removing IO instructions one by one, we can try deleting multiple
instructions at once. According to the locality of reference, we double the
number of instructions to remove for the next round and recover it to one
once we fail.
This patch is usually significant for large input.
Test with quadrupled trace input at:
https://bugs.launchpad.net/qemu/+bug/1890333/comments/1
Patched 1/6 version:
real 0m45.904s
user 0m16.874s
sys 0m10.042s
Refined version:
real 0m11.412s
user 0m6.888s
sys 0m3.325s
Signed-off-by: Qiuhao Li <Qiuhao.Li@outlook.com>
Reviewed-by: Alexander Bulekov <alxndr@bu.edu>
Tested-by: Alexander Bulekov <alxndr@bu.edu>
Message-Id:
<SYCPR01MB350280A67BB55C3FADF173E3FCAB0@SYCPR01MB3502.ausprd01.prod.outlook.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: e72203abec8f15bb187c239256e7c991cb21601f
https://github.com/qemu/qemu/commit/e72203abec8f15bb187c239256e7c991cb21601f
Author: Qiuhao Li <Qiuhao.Li@outlook.com>
Date: 2021-01-11 (Mon, 11 Jan 2021)
Changed paths:
M scripts/oss-fuzz/minimize_qtest_trace.py
Log Message:
-----------
fuzz: split write operand using binary approach
Currently, we split the write commands' data from the middle. If it does not
work, try to move the pivot left by one byte and retry until there is no
space.
But, this method has two flaws:
1. It may fail to trim all unnecessary bytes on the right side.
For example, there is an IO write command:
write addr uuxxxxuu
u is the unnecessary byte for the crash. Unlike ram write commands, in most
case, a split IO write won't trigger the same crash, So if we split from the
middle, we will get:
write addr uu (will be removed in next round)
write addr xxxxuu
For xxxxuu, since split it from the middle and retry to the leftmost byte
won't get the same crash, we will be stopped from removing the last two
bytes.
2. The algorithm complexity is O(n) since we move the pivot byte by byte.
To solve the first issue, we can try a symmetrical position on the right if
we fail on the left. As for the second issue, instead moving by one byte, we
can approach the boundary exponentially, achieving O(log(n)).
Give an example:
xxxxuu len=6
+
|
+
xxx,xuu 6/2=3 fail
+
+--------------+-------------+
| |
+ +
xx,xxuu 6/2^2=1 fail xxxxu,u 6-1=5 success
+ +
+------------------+----+ |
| | +-------------+ u removed
+ +
xx,xxu 5/2=2 fail xxxx,u 6-2=4 success
+
|
+-----------+ u removed
In some rare cases, this algorithm will fail to trim all unnecessary bytes:
xxxxxxxxxuxxxxxx
xxxxxxxx-xuxxxxxx Fail
xxxx-xxxxxuxxxxxx Fail
xxxxxxxxxuxx-xxxx Fail
...
I think the trade-off is worth it.
Signed-off-by: Qiuhao Li <Qiuhao.Li@outlook.com>
Reviewed-by: Alexander Bulekov <alxndr@bu.edu>
Tested-by: Alexander Bulekov <alxndr@bu.edu>
Message-Id:
<SYCPR01MB3502D26F1BEB680CBBC169E5FCAB0@SYCPR01MB3502.ausprd01.prod.outlook.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: 247ab240c2aa391c611a5cf7b79226b89722d53e
https://github.com/qemu/qemu/commit/247ab240c2aa391c611a5cf7b79226b89722d53e
Author: Qiuhao Li <Qiuhao.Li@outlook.com>
Date: 2021-01-11 (Mon, 11 Jan 2021)
Changed paths:
M scripts/oss-fuzz/minimize_qtest_trace.py
Log Message:
-----------
fuzz: remove IO commands iteratively
Now we use a one-time scan and remove strategy in the minimizer,
which is not suitable for timing dependent instructions.
For example, instruction A will indicate an address where the config
chunk locates, and instruction B will make the configuration active.
If we have the following instruction sequence:
...
A1
B1
A2
B2
...
A2 and B2 are the actual instructions that trigger the bug.
If we scan from top to bottom, after we remove A1, the behavior of B1
might be unknowable, including not to crash the program. But we will
successfully remove B1 later cause A2 and B2 will crash the process
anyway:
...
A1
A2
B2
...
Now one more trimming will remove A1.
In the perfect case, we would need to be able to remove A and B (or C!) at
the same time. But for now, let's just add a loop around the minimizer.
Since we only remove instructions, this iterative algorithm is converging.
Tested with Bug 1908062.
Signed-off-by: Qiuhao Li <Qiuhao.Li@outlook.com>
Reviewed-by: Alexander Bulekov <alxndr@bu.edu>
Tested-by: Alexander Bulekov <alxndr@bu.edu>
Message-Id:
<SYCPR01MB350263004448040ACCB9A9F1FCAB0@SYCPR01MB3502.ausprd01.prod.outlook.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: 9d20f2af535a928a20eb4e5fcb782f9d43dae5ac
https://github.com/qemu/qemu/commit/9d20f2af535a928a20eb4e5fcb782f9d43dae5ac
Author: Qiuhao Li <Qiuhao.Li@outlook.com>
Date: 2021-01-11 (Mon, 11 Jan 2021)
Changed paths:
M scripts/oss-fuzz/minimize_qtest_trace.py
Log Message:
-----------
fuzz: set bits in operand of write/out to zero
Simplifying the crash cases by opportunistically setting bits in operands of
out/write to zero may help to debug, since usually bit one means turn on or
trigger a function while zero is the default turn-off setting.
Tested bug https://bugs.launchpad.net/qemu/+bug/1908062
Signed-off-by: Qiuhao Li <Qiuhao.Li@outlook.com>
Reviewed-by: Alexander Bulekov <alxndr@bu.edu>
Tested-by: Alexander Bulekov <alxndr@bu.edu>
Message-Id:
<SYCPR01MB3502C84B6346A3E3DE708C7BFCAB0@SYCPR01MB3502.ausprd01.prod.outlook.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: dd21ed0edfe3e70aed3d672728198d2825963796
https://github.com/qemu/qemu/commit/dd21ed0edfe3e70aed3d672728198d2825963796
Author: Qiuhao Li <Qiuhao.Li@outlook.com>
Date: 2021-01-11 (Mon, 11 Jan 2021)
Changed paths:
M scripts/oss-fuzz/minimize_qtest_trace.py
Log Message:
-----------
fuzz: add minimization options
-M1: remove IO commands iteratively
-M2: try setting bits in operand of write/out to zero
Signed-off-by: Qiuhao Li <Qiuhao.Li@outlook.com>
Reviewed-by: Alexander Bulekov <alxndr@bu.edu>
Tested-by: Alexander Bulekov <alxndr@bu.edu>
Message-Id:
<SYCPR01MB350204C52E7A39E6B0EEC870FCAB0@SYCPR01MB3502.ausprd01.prod.outlook.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: 4cc5752303c83b55e56961d91b7cf83c4e73f393
https://github.com/qemu/qemu/commit/4cc5752303c83b55e56961d91b7cf83c4e73f393
Author: Qiuhao Li <Qiuhao.Li@outlook.com>
Date: 2021-01-11 (Mon, 11 Jan 2021)
Changed paths:
M scripts/oss-fuzz/minimize_qtest_trace.py
Log Message:
-----------
fuzz: heuristic split write based on past IOs
If previous write commands write the same length of data with the same step,
we view it as a hint.
Signed-off-by: Qiuhao Li <Qiuhao.Li@outlook.com>
Reviewed-by: Alexander Bulekov <alxndr@bu.edu>
Tested-by: Alexander Bulekov <alxndr@bu.edu>
Message-Id:
<SYCPR01MB3502480AD07811A6A49B8FEAFCAB0@SYCPR01MB3502.ausprd01.prod.outlook.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: 4d306e59cbc0ea8539bbb6732a30f113cdf0bf2d
https://github.com/qemu/qemu/commit/4d306e59cbc0ea8539bbb6732a30f113cdf0bf2d
Author: Warner Losh <imp@freebsd.org>
Date: 2021-01-11 (Mon, 11 Jan 2021)
Changed paths:
M bsd-user/freebsd/syscall_nr.h
Log Message:
-----------
bsd-user: regenerate FreeBSD's system call numbers
Recreate the FreeBSD system call numbers from current sys/syscall.h. Since this
isn't guaranteed to be on all systems, continue the practice of generating it
with some variation on:
sed -e s/SYS_/TARGET_NR_/ < $FREEBSD_SRC/sys/syscall.h > syscall_nr.h
until a more comprehensive system can be put in place.
Signed-off-by: Warner Losh <imp@FreeBSD.org>
Message-Id: <20201218205451.10559-2-imp@freebsd.org>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: ea1ab4cf2c268c61e97b12cac670c5ccfc71d745
https://github.com/qemu/qemu/commit/ea1ab4cf2c268c61e97b12cac670c5ccfc71d745
Author: Stacey Son <sson@FreeBSD.org>
Date: 2021-01-11 (Mon, 11 Jan 2021)
Changed paths:
A bsd-user/arm/target_arch_sysarch.h
A bsd-user/arm/target_syscall.h
A bsd-user/freebsd/os-strace.h
M bsd-user/freebsd/strace.list
A bsd-user/i386/target_arch_sysarch.h
M bsd-user/i386/target_syscall.h
A bsd-user/mips/target_arch_sysarch.h
A bsd-user/mips/target_syscall.h
A bsd-user/mips64/target_arch_sysarch.h
A bsd-user/mips64/target_syscall.h
A bsd-user/netbsd/os-strace.h
A bsd-user/openbsd/os-strace.h
A bsd-user/sparc/target_arch_sysarch.h
M bsd-user/sparc/target_syscall.h
A bsd-user/sparc64/target_arch_sysarch.h
M bsd-user/sparc64/target_syscall.h
M bsd-user/strace.c
A bsd-user/x86_64/target_arch_sysarch.h
M bsd-user/x86_64/target_syscall.h
M meson.build
Log Message:
-----------
bsd-user: move strace OS/arch dependent code to host/arch dirs
This change moves host OS and arch dependent code for the sysarch
system call related to the -strace functionality into the
appropriate host OS and target arch directories.
Signed-off-by: Stacey Son <sson@FreeBSD.org>
Signed-off-by: Sean Bruno <sburno@FreeBSD.org>
[ imp integrated minor build fixes from sbruno ]
Signed-off-by: Warner Losh <imp@FreeBSD.org>
Message-Id: <20201218205451.10559-4-imp@freebsd.org>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: f6eb4a0841ee8944bf19eed84832d2cd9209da3c
https://github.com/qemu/qemu/commit/f6eb4a0841ee8944bf19eed84832d2cd9209da3c
Author: Warner Losh <imp@freebsd.org>
Date: 2021-01-11 (Mon, 11 Jan 2021)
Changed paths:
M bsd-user/freebsd/strace.list
Log Message:
-----------
bsd-user: Update strace.list for FreeBSD's latest syscalls
Update strace.list to include all of FreeBSD's syscalls up through svn
r331280.
Signed-off-by: Stacey Son <sson@FreeBSD.org>
Signed-off-by: Sean Bruno <sburno@FreeBSD.org>
Signed-off-by: Alexander Kabaev <kan@FreeBSD.org>
Signed-off-by: Jung-uk Kim <jkim@FreeBSD.org>
Author: Michal Meloun <mmel@FreeBSD.org>
Signed-off-by: Mikaël Urankar <mikael.urankar@gmail.com>
[imp moved this change to early in the sequence]
Signed-off-by: Warner Losh <imp@FreeBSD.org>
Message-Id: <20201218205451.10559-5-imp@freebsd.org>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: 333168efe5c8f6b3eaa4cd2f0b715431234f85eb
https://github.com/qemu/qemu/commit/333168efe5c8f6b3eaa4cd2f0b715431234f85eb
Author: Thomas Huth <thuth@redhat.com>
Date: 2021-01-11 (Mon, 11 Jan 2021)
Changed paths:
M tests/acceptance/machine_s390_ccw_virtio.py
Log Message:
-----------
tests/acceptance: Fix race conditions in s390x tests & skip fedora on
gitlab-CI
There was a race condition in the first test where there was already the
"crw" output in the dmesg, but the "0.0.4711" entry has not been created
in the /sys fs yet. Fix it by waiting until it is there.
The second test has even more problems on gitlab-CI. Even after adding some
more synchronization points (that wait for some messages in the "dmesg"
output to make sure that the modules got loaded correctly), there are still
occasionally some hangs in this test when it is running in the gitlab-CI.
So far I was unable to reproduce these hangs locally on my computer, so
this issue might take a while to debug. Thus disable the 2nd test in the
gitlab-CI until the problems are better understood and fixed.
Signed-off-by: Thomas Huth <thuth@redhat.com>
Tested-by: Willian Rampazzo <willianr@redhat.com>
Reviewed-by: Willian Rampazzo <willianr@redhat.com>
Message-Id: <20210108185645.86351-1-thuth@redhat.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: b677001d70529df271a5d9314440bb201da40acf
https://github.com/qemu/qemu/commit/b677001d70529df271a5d9314440bb201da40acf
Author: Alexander Bulekov <alxndr@bu.edu>
Date: 2021-01-11 (Mon, 11 Jan 2021)
Changed paths:
M tests/qtest/fuzz/generic_fuzz.c
Log Message:
-----------
fuzz: map all BARs and enable PCI devices
Prior to this patch, the fuzzer found inputs to map PCI device BARs and
enable the device. While it is nice that the fuzzer can do this, it
added significant overhead, since the fuzzer needs to map all the
BARs (regenerating the memory topology), at the start of each input.
With this patch, we do this once, before fuzzing, mitigating some of
this overhead.
Signed-off-by: Alexander Bulekov <alxndr@bu.edu>
Reviewed-by: Darren Kenny <darren.kenny@oracle.com>
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Message-Id: <20201221181203.1853-1-alxndr@bu.edu>
Signed-off-by: Thomas Huth <thuth@redhat.com>
Commit: b3f846c59d8405bb87c551187721fc92ff2f1b92
https://github.com/qemu/qemu/commit/b3f846c59d8405bb87c551187721fc92ff2f1b92
Author: Peter Maydell <peter.maydell@linaro.org>
Date: 2021-01-11 (Mon, 11 Jan 2021)
Changed paths:
M .gitlab-ci.d/containers.yml
M .gitlab-ci.yml
A bsd-user/arm/target_arch_sysarch.h
A bsd-user/arm/target_syscall.h
A bsd-user/freebsd/os-strace.h
M bsd-user/freebsd/strace.list
M bsd-user/freebsd/syscall_nr.h
A bsd-user/i386/target_arch_sysarch.h
M bsd-user/i386/target_syscall.h
A bsd-user/mips/target_arch_sysarch.h
A bsd-user/mips/target_syscall.h
A bsd-user/mips64/target_arch_sysarch.h
A bsd-user/mips64/target_syscall.h
A bsd-user/netbsd/os-strace.h
A bsd-user/openbsd/os-strace.h
A bsd-user/sparc/target_arch_sysarch.h
M bsd-user/sparc/target_syscall.h
A bsd-user/sparc64/target_arch_sysarch.h
M bsd-user/sparc64/target_syscall.h
M bsd-user/strace.c
A bsd-user/x86_64/target_arch_sysarch.h
M bsd-user/x86_64/target_syscall.h
M meson.build
M scripts/oss-fuzz/minimize_qtest_trace.py
M tests/acceptance/machine_s390_ccw_virtio.py
A tests/docker/dockerfiles/opensuse-leap.docker
M tests/qtest/fuzz/generic_fuzz.c
M tests/qtest/libqtest.c
M util/oslib-win32.c
Log Message:
-----------
Merge remote-tracking branch
'remotes/huth-gitlab/tags/pull-request-2021-01-11v2' into staging
* Fuzzer improvements
* Add OpenSUSE leap to the gitlab-CI
* Some fixes to get our CI "green" again
* Some initial patches to update bsd-user
# gpg: Signature made Mon 11 Jan 2021 14:00:07 GMT
# gpg: using RSA key 27B88847EEE0250118F3EAB92ED9D774FE702DB5
# gpg: issuer "thuth@redhat.com"
# gpg: Good signature from "Thomas Huth <th.huth@gmx.de>" [full]
# gpg: aka "Thomas Huth <thuth@redhat.com>" [full]
# gpg: aka "Thomas Huth <huth@tuxfamily.org>" [full]
# gpg: aka "Thomas Huth <th.huth@posteo.de>" [unknown]
# Primary key fingerprint: 27B8 8847 EEE0 2501 18F3 EAB9 2ED9 D774 FE70 2DB5
* remotes/huth-gitlab/tags/pull-request-2021-01-11v2:
fuzz: map all BARs and enable PCI devices
tests/acceptance: Fix race conditions in s390x tests & skip fedora on
gitlab-CI
bsd-user: Update strace.list for FreeBSD's latest syscalls
bsd-user: move strace OS/arch dependent code to host/arch dirs
bsd-user: regenerate FreeBSD's system call numbers
fuzz: heuristic split write based on past IOs
fuzz: add minimization options
fuzz: set bits in operand of write/out to zero
fuzz: remove IO commands iteratively
fuzz: split write operand using binary approach
fuzz: double the IOs to remove for every loop
fuzz: accelerate non-crash detection
util/oslib-win32: Fix _aligned_malloc() arguments order
qtest/libqtest: fix heap-buffer-overflow in qtest_cb_for_every_machine()
gitlab-ci.yml: Add openSUSE Leap 15.2 for gitlab CI/CD
Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Compare: https://github.com/qemu/qemu/compare/7b09f127738a...b3f846c59d84