Almost nothing in here is arm-related, but the target-arm

queue was convenient for these last minute bits and pieces

for 5.0...

The following changes since commit 14e5526b51910efd62cd31cd95b49baca975c83f:

Merge remote-tracking branch 'remotes/mst/tags/for_upstream' into staging (2020-04-13 15:42:51 +0100)

https://git.linaro.org/people/pmaydell/qemu-arm.git tags/pull-target-arm-20200414

for you to fetch changes up to 84f82ddcbb4ac4ed04c8675e85155329f23184f0:

Deprecate KVM support for AArch32 (2020-04-14 17:20:22 +0100)

patch queue:

* Fix some problems that trip up Coverity's scanner

* run-coverity-scan: New script automating the scan-and-upload process

* docs: Improve our gdbstub documentation

* configure: Honour --disable-werror for Sphinx

* docs: Fix errors produced when building with Sphinx 3.0

* docs: Require Sphinx 1.6 or better

* Add deprecation notice for KVM support on AArch32 hosts

Peter Maydell (12):

osdep.h: Drop no-longer-needed Coverity workarounds

thread.h: Fix Coverity version of qemu_cond_timedwait()

thread.h: Remove trailing semicolons from Coverity qemu_mutex_lock() etc

linux-user/flatload.c: Use "" for include of QEMU header target_flat.h

scripts/run-coverity-scan: Script to run Coverity Scan build

scripts/coverity-scan: Add Docker support

docs: Improve our gdbstub documentation

configure: Honour --disable-werror for Sphinx

scripts/kernel-doc: Add missing close-paren in c:function directives

kernel-doc: Use c:struct for Sphinx 3.0 and later

docs: Require Sphinx 1.6 or better

Deprecate KVM support for AArch32

configure | 9 +-

Makefile | 2 +-

include/qemu/osdep.h | 14 -

include/qemu/thread.h | 12 +-

linux-user/flatload.c | 2 +-

MAINTAINERS | 5 +

docs/conf.py | 6 +-

docs/sphinx/kerneldoc.py | 1 +

docs/system/deprecated.rst | 8 +

docs/system/gdb.rst | 22 +-

qemu-options.hx | 24 +-

scripts/coverity-scan/coverity-scan.docker | 131 ++++++++++

scripts/coverity-scan/run-coverity-scan | 401 +++++++++++++++++++++++++++++

scripts/kernel-doc | 18 +-

14 files changed, 615 insertions(+), 40 deletions(-)

create mode 100644 scripts/coverity-scan/coverity-scan.docker

create mode 100755 scripts/coverity-scan/run-coverity-scan

The documentation of our -s and -gdb options is quite old; in

particular it still claims that it will cause QEMU to stop and wait

for the gdb connection, when this has not been true for some time:

you also need to pass -S if you want to make QEMU not launch the

guest on startup.

Improve the documentation to mention this requirement in the

executable's --help output, the documentation of the -gdb option in

the manual, and in the "GDB usage" chapter.

Includes some minor tweaks to these paragraphs of documentation

since I was editing them anyway (such as dropping the description

of our gdb support as "primitive").

Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>

Reviewed-by: Richard Henderson <richard.henderson@linaro.org>

Reviewed-by: Alex Bennée <alex.bennee@linaro.org>

Message-id: 20200403094014.9589-1-peter.maydell@linaro.org

docs/system/gdb.rst | 22 +++++++++++++++-------

qemu-options.hx | 24 ++++++++++++++++++------

2 files changed, 33 insertions(+), 13 deletions(-)

DEF("gdb", HAS_ARG, QEMU_OPTION_gdb, \

- "-gdb dev wait for gdb connection on 'dev'\n", QEMU_ARCH_ALL)

+ "-gdb dev accept gdb connection on 'dev'. (QEMU defaults to starting\n"

+ " the guest without waiting for gdb to connect; use -S too\n"

+ " if you want it to not start execution.)\n",

+ QEMU_ARCH_ALL)

SRST

``-gdb dev``

- Wait for gdb connection on device dev (see

- :ref:`gdb_005fusage`). Typical connections will likely be

- TCP-based, but also UDP, pseudo TTY, or even stdio are reasonable

- use case. The latter is allowing to start QEMU from within gdb and

- establish the connection via a pipe:

+ Accept a gdb connection on device dev (see

+ :ref:`gdb_005fusage`). Note that this option does not pause QEMU

+ execution -- if you want QEMU to not start the guest until you

+ connect with gdb and issue a ``continue`` command, you will need to

+ also pass the ``-S`` option to QEMU.

+

+ The most usual configuration is to listen on a local TCP socket::

+

+ -gdb tcp::3117

+

+ but you can specify other backends; UDP, pseudo TTY, or even stdio

+ are all reasonable use cases. For example, a stdio connection

+ allows you to start QEMU from within gdb and establish the

+ connection via a pipe:

.. parsed-literal::

When kernel-doc generates a 'c:function' directive for a function

one of whose arguments is a function pointer, it fails to print

the close-paren after the argument list of the function pointer

argument, for instance in the memory API documentation:

.. c:function:: void memory_region_init_resizeable_ram (MemoryRegion * mr, struct Object * owner, const char * name, uint64_t size, uint64_t max_size, void (*resized) (const char*, uint64_t length, void *host, Error ** errp)

which should have a ')' after the 'void *host' which is the

last argument to 'resized'.

Older versions of Sphinx don't try to parse the argumnet

to c:function, but Sphinx 3.0 does do this and will complain:

/home/petmay01/linaro/qemu-from-laptop/qemu/docs/../include/exec/memory.h:834: WARNING: Error in declarator or parameters

Invalid C declaration: Expecting "," or ")" in parameters, got "EOF". [error at 208]

void memory_region_init_resizeable_ram (MemoryRegion * mr, struct Object * owner, const char * name, uint64_t size, uint64_t max_size, void (*resized) (const char*, uint64_t length, void *host, Error ** errp)

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------^

Add the missing close-paren.

Message-id: 20200411182934.28678-3-peter.maydell@linaro.org

Reviewed-by: Alex Bennée <alex.bennee@linaro.org>

scripts/kernel-doc | 2 +-

1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/scripts/kernel-doc b/scripts/kernel-doc

index XXXXXXX..XXXXXXX 100755

--- a/scripts/kernel-doc

+++ b/scripts/kernel-doc

@@ -XXX,XX +XXX,XX @@ sub output_function_rst(%) {

    if ($type =~ m/([^\(]*\(\*)\s*\)\s*\(([^\)]*)\)/) {

     # pointer-to-function

-     print $1 . $parameter . ") (" . $2;

+     print $1 . $parameter . ") (" . $2 . ")";

    } else {

     print $type . " " . $parameter;

    }

Versions of Sphinx older than 1.6 can't build all of our documentation,

because they are too picky about the syntax of the argument to the

option:: directive; see Sphinx bugs #646, #3366:

https://github.com/sphinx-doc/sphinx/issues/646

https://github.com/sphinx-doc/sphinx/issues/3366

Trying to build with a 1.4.x Sphinx fails with

docs/system/images.rst:4: SEVERE: Duplicate ID: "cmdoption-qcow2-arg-encrypt"

and a 1.5.x Sphinx fails with

docs/system/invocation.rst:544: WARNING: Malformed option description '[enable=]PATTERN', should look like "opt", "-opt

args", "--opt args", "/opt args" or "+opt args"

Update our needs_sphinx setting to indicate that we require at least

1.6. This will allow configure to fall back to "don't build the

docs" rather than causing the build to fail entirely, which is

probably what most users building on a host old enough to have such

an old Sphinx would want; if they do want the docs then they'll have

a useful indication of what they need to do (upgrade Sphinx!) rather

than a confusing error message.

In theory our distro support policy would suggest that we should

support building on the Sphinx shipped in those distros, but:

* EPEL7 has Sphinx 1.2.3 (which we've never supported!)

* Debian Stretch has Sphinx 1.4.8

Trying to get our docs to work with Sphinx 1.4 is not tractable

for the 5.0 release and I'm not sure it's worthwhile effort anyway;

at least with this change the build as a whole now succeeds.

Thanks to John Snow for doing the investigation and testing to

confirm what Sphinx versions fail in what ways and what distros

shipped what.

docs/conf.py | 6 ++++--

1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/docs/conf.py b/docs/conf.py

--- a/docs/conf.py

+++ b/docs/conf.py

@@ -XXX,XX +XXX,XX @@ sys.path.insert(0, os.path.join(qemu_docdir, "sphinx"))

# If your documentation needs a minimal Sphinx version, state it here.

#

-# 1.3 is where the 'alabaster' theme was shipped with Sphinx.

-needs_sphinx = '1.3'

+# Sphinx 1.5 and earlier can't build our docs because they are too

+# picky about the syntax of the argument to the option:: directive

+# (see Sphinx bugs #646, #3366).

+needs_sphinx = '1.6'

# Add any Sphinx extension module names here, as strings. They can be

# extensions coming with Sphinx (named 'sphinx.ext.*') or your custom

The Linux kernel has dropped support for allowing 32-bit Arm systems

to host KVM guests (kernel commit 541ad0150ca4aa663a2, which just

landed upstream in the 5.7 merge window). Mark QEMU's support for

this configuration as deprecated, so that we can delete that support

code in 5.2.

Reviewed-by: Andrew Jones <drjones@redhat.com>

docs/system/deprecated.rst | 8 ++++++++

diff --git a/docs/system/deprecated.rst b/docs/system/deprecated.rst

--- a/docs/system/deprecated.rst

+++ b/docs/system/deprecated.rst

@@ -XXX,XX +XXX,XX @@ The ``compat`` property used to set backwards compatibility modes for

the processor has been deprecated. The ``max-cpu-compat`` property of

the ``pseries`` machine type should be used instead.

+KVM guest support on 32-bit Arm hosts (since 5.0)

+'''''''''''''''''''''''''''''''''''''''''''''''''

+

+The Linux kernel has dropped support for allowing 32-bit Arm systems

+to host KVM guests as of the 5.7 kernel. Accordingly, QEMU is deprecating

+its support for this configuration and will remove it in a future version.

+Running 32-bit guests on a 64-bit Arm host remains supported.

+

System emulator devices

-----------------------

All the Coverity-specific definitions of qemu_mutex_lock() and friends

have a trailing semicolon. This works fine almost everywhere because

of QEMU's mandatory-braces coding style and because most callsites are

simple, but target/s390x/sigp.c has a use of qemu_mutex_trylock() as

an if() statement, which makes the ';' a syntax error:

"../target/s390x/sigp.c", line 461: warning #18: expected a ")"

if (qemu_mutex_trylock(&qemu_sigp_mutex)) {

^

Remove the bogus semicolons from the macro definitions.

Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>

Message-id: 20200319193323.2038-4-peter.maydell@linaro.org

include/qemu/thread.h | 12 ++++++------

1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/include/qemu/thread.h b/include/qemu/thread.h

--- a/include/qemu/thread.h

+++ b/include/qemu/thread.h

@@ -XXX,XX +XXX,XX @@ extern QemuCondTimedWaitFunc qemu_cond_timedwait_func;

* hide them.

*/

#define qemu_mutex_lock(m) \

- qemu_mutex_lock_impl(m, __FILE__, __LINE__);

+ qemu_mutex_lock_impl(m, __FILE__, __LINE__)

#define qemu_mutex_trylock(m) \

- qemu_mutex_trylock_impl(m, __FILE__, __LINE__);

+ qemu_mutex_trylock_impl(m, __FILE__, __LINE__)

#define qemu_rec_mutex_lock(m) \

- qemu_rec_mutex_lock_impl(m, __FILE__, __LINE__);

+ qemu_rec_mutex_lock_impl(m, __FILE__, __LINE__)

#define qemu_rec_mutex_trylock(m) \

- qemu_rec_mutex_trylock_impl(m, __FILE__, __LINE__);

+ qemu_rec_mutex_trylock_impl(m, __FILE__, __LINE__)

#define qemu_cond_wait(c, m) \

- qemu_cond_wait_impl(c, m, __FILE__, __LINE__);

+ qemu_cond_wait_impl(c, m, __FILE__, __LINE__)

#define qemu_cond_timedwait(c, m, ms) \

- qemu_cond_timedwait_impl(c, m, ms, __FILE__, __LINE__);

+ qemu_cond_timedwait_impl(c, m, ms, __FILE__, __LINE__)

#else

#define qemu_mutex_lock(m) ({ \

QemuMutexLockFunc _f = atomic_read(&qemu_mutex_lock_func); \

For Coverity's benefit, we provide simpler versions of functions like

qemu_mutex_lock(), qemu_cond_wait() and qemu_cond_timedwait(). When

we added qemu_cond_timedwait() in commit 3dcc9c6ec4ea, a cut and

paste error meant that the Coverity version of qemu_cond_timedwait()

was using the wrong _impl function, which makes the Coverity parser

complain:

"/qemu/include/qemu/thread.h", line 159: warning #140: too many arguments in

function call

return qemu_cond_timedwait(cond, mutex, ms);

^

"/qemu/include/qemu/thread.h", line 159: warning #120: return value type does

not match the function type

return qemu_cond_timedwait(cond, mutex, ms);

^

"/qemu/include/qemu/thread.h", line 156: warning #1563: function

"qemu_cond_timedwait" not emitted, consider modeling it or review

parse diagnostics to improve fidelity

static inline bool (qemu_cond_timedwait)(QemuCond *cond, QemuMutex *mutex,

^

These aren't fatal, but reduce the scope of the analysis. Fix the error.

Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>

Message-id: 20200319193323.2038-3-peter.maydell@linaro.org

include/qemu/thread.h | 2 +-

diff --git a/include/qemu/thread.h b/include/qemu/thread.h

--- a/include/qemu/thread.h

+++ b/include/qemu/thread.h

@@ -XXX,XX +XXX,XX @@ extern QemuCondTimedWaitFunc qemu_cond_timedwait_func;

#define qemu_cond_wait(c, m) \

qemu_cond_wait_impl(c, m, __FILE__, __LINE__);

#define qemu_cond_timedwait(c, m, ms) \

- qemu_cond_wait_impl(c, m, ms, __FILE__, __LINE__);

+ qemu_cond_timedwait_impl(c, m, ms, __FILE__, __LINE__);

#else

#define qemu_mutex_lock(m) ({ \

QemuMutexLockFunc _f = atomic_read(&qemu_mutex_lock_func); \

In commit a1a98357e3fd in 2018 we added some workarounds for Coverity

not being able to handle the _Float* types introduced by recent

glibc. Newer versions of the Coverity scan tools have support for

these types, and will fail with errors about duplicate typedefs if we

have our workaround. Remove our copy of the typedefs.

Message-id: 20200319193323.2038-2-peter.maydell@linaro.org

include/qemu/osdep.h | 14 --------------

1 file changed, 14 deletions(-)

diff --git a/include/qemu/osdep.h b/include/qemu/osdep.h

--- a/include/qemu/osdep.h

+++ b/include/qemu/osdep.h

@@ -XXX,XX +XXX,XX @@

#else

#include "exec/poison.h"

#endif

-#ifdef __COVERITY__

-/* Coverity does not like the new _Float* types that are used by

- * recent glibc, and croaks on every single file that includes

- * stdlib.h. These typedefs are enough to please it.

- *

- * Note that these fix parse errors so they cannot be placed in

- * scripts/coverity-model.c.

- */

-typedef float _Float32;

-typedef double _Float32x;

-typedef double _Float64;

-typedef __float80 _Float64x;

-typedef __float128 _Float128;

-#endif

#include "qemu/compiler.h"

If we are not making warnings fatal for compilation, make them

non-fatal when building the Sphinx documentation also. (For instance

Sphinx 3.0 warns about some constructs that older versions were happy

with, which is a build failure if we use the warnings-as-errors

flag.)

This provides a workaround at least for LP:1872113.

configure | 9 ++++++++-

Makefile | 2 +-

2 files changed, 9 insertions(+), 2 deletions(-)

@@ -XXX,XX +XXX,XX @@ if check_include sys/kcov.h ; then

kcov=yes

+# If we're making warnings fatal, apply this to Sphinx runs as well

+sphinx_werror=""

+if test "$werror" = "yes"; then

+ sphinx_werror="-W"

+fi

+

# Check we have a new enough version of sphinx-build

has_sphinx_build() {

# This is a bit awkward but works: create a trivial document and

@@ -XXX,XX +XXX,XX @@ has_sphinx_build() {

# sphinx-build doesn't exist at all or if it is too old.

mkdir -p "$TMPDIR1/sphinx"

touch "$TMPDIR1/sphinx/index.rst"

- "$sphinx_build" -c "$source_path/docs" -b html "$TMPDIR1/sphinx" "$TMPDIR1/sphinx/out" >/dev/null 2>&1

+ "$sphinx_build" $sphinx_werror -c "$source_path/docs" -b html "$TMPDIR1/sphinx" "$TMPDIR1/sphinx/out" >/dev/null 2>&1

}

# Check if tools are available to build documentation.

@@ -XXX,XX +XXX,XX @@ echo "INSTALL_PROG=$install -c -m 0755" >> $config_host_mak

echo "INSTALL_LIB=$install -c -m 0644" >> $config_host_mak

echo "PYTHON=$python" >> $config_host_mak

echo "SPHINX_BUILD=$sphinx_build" >> $config_host_mak

+echo "SPHINX_WERROR=$sphinx_werror" >> $config_host_mak

echo "GENISOIMAGE=$genisoimage" >> $config_host_mak

echo "CC=$cc" >> $config_host_mak

if $iasl -h > /dev/null 2>&1; then

diff --git a/Makefile b/Makefile

--- a/Makefile

+++ b/Makefile

@@ -XXX,XX +XXX,XX @@ sphinxdocs: $(MANUAL_BUILDDIR)/devel/index.html \

# Note the use of different doctree for each (manual, builder) tuple;

# this works around Sphinx not handling parallel invocation on

# a single doctree: https://github.com/sphinx-doc/sphinx/issues/2946

-build-manual = $(call quiet-command,CONFDIR="$(qemu_confdir)" $(SPHINX_BUILD) $(if $(V),,-q) -W -b $2 -D version=$(VERSION) -D release="$(FULL_VERSION)" -d .doctrees/$1-$2 $(SRC_PATH)/docs/$1 $(MANUAL_BUILDDIR)/$1 ,"SPHINX","$(MANUAL_BUILDDIR)/$1")

+build-manual = $(call quiet-command,CONFDIR="$(qemu_confdir)" $(SPHINX_BUILD) $(if $(V),,-q) $(SPHINX_WERROR) -b $2 -D version=$(VERSION) -D release="$(FULL_VERSION)" -d .doctrees/$1-$2 $(SRC_PATH)/docs/$1 $(MANUAL_BUILDDIR)/$1 ,"SPHINX","$(MANUAL_BUILDDIR)/$1")

# We assume all RST files in the manual's directory are used in it

manual-deps = $(wildcard $(SRC_PATH)/docs/$1/*.rst $(SRC_PATH)/docs/$1/*/*.rst) \

$(SRC_PATH)/docs/defs.rst.inc \

The kernel-doc Sphinx plugin and associated script currently emit

'c:type' directives for "struct foo" documentation.

Sphinx 3.0 warns about this:

/home/petmay01/linaro/qemu-from-laptop/qemu/docs/../include/exec/memory.h:3: WARNING: Type must be either just a name or a typedef-like declaration.

If just a name:

Error in declarator or parameters

Invalid C declaration: Expected identifier in nested name, got keyword: struct [error at 6]

struct MemoryListener

------^

If typedef-like declaration:

Error in declarator or parameters

Invalid C declaration: Expected identifier in nested name. [error at 21]

struct MemoryListener

---------------------^

because it wants us to use the new-in-3.0 'c:struct' instead.

Plumb the Sphinx version through to the kernel-doc script

and use it to select 'c:struct' for newer versions than 3.0.

Fixes: LP:1872113

Signed-off-by: Peter Maydell <peter.maydell@linaro.org>

Reviewed-by: Alex Bennée <alex.bennee@linaro.org>

---

docs/sphinx/kerneldoc.py | 1 +

scripts/kernel-doc | 16 +++++++++++++++-

2 files changed, 16 insertions(+), 1 deletion(-)

diff --git a/docs/sphinx/kerneldoc.py b/docs/sphinx/kerneldoc.py

--- a/docs/sphinx/kerneldoc.py

+++ b/docs/sphinx/kerneldoc.py

@@ -XXX,XX +XXX,XX @@ class KernelDocDirective(Directive):

env.note_dependency(os.path.abspath(f))

cmd += ['-export-file', f]

+ cmd += ['-sphinx-version', sphinx.__version__]

cmd += [filename]

try:

diff --git a/scripts/kernel-doc b/scripts/kernel-doc

index XXXXXXX..XXXXXXX 100755

--- a/scripts/kernel-doc

+++ b/scripts/kernel-doc

@@ -XXX,XX +XXX,XX @@ Output selection (mutually exclusive):

            DOC: sections. May be specified multiple times.

Output selection modifiers:

+ -sphinx-version VER Generate rST syntax for the specified Sphinx version.

+ Only works with reStructuredTextFormat.

-no-doc-sections    Do not output DOC: sections.

-enable-lineno Enable output of #define LINENO lines. Only works with

reStructuredText format.

@@ -XXX,XX +XXX,XX @@ use constant {

};

my $output_selection = OUTPUT_ALL;

my $show_not_found = 0;    # No longer used

+my $sphinx_version = "0.0"; # if not specified, assume old

my @export_file_list;

@@ -XXX,XX +XXX,XX @@ while ($ARGV[0] =~ m/^--?(.*)/) {

     $enable_lineno = 1;

} elsif ($cmd eq 'show-not-found') {

    $show_not_found = 1; # A no-op but don't fail

+ } elsif ($cmd eq 'sphinx-version') {

+ $sphinx_version = shift @ARGV;

} else {

    # Unknown argument

usage();

@@ -XXX,XX +XXX,XX @@ sub output_struct_rst(%) {

my $oldprefix = $lineprefix;

my $name = $args{'type'} . " " . $args{'struct'};

- print "\n\n.. c:type:: " . $name . "\n\n";

+ # Sphinx 3.0 and up will emit warnings for "c:type:: struct Foo".

+ # It wants to see "c:struct:: Foo" (and will add the word 'struct' in

+ # the rendered output).

+ if ((split(/\./, $sphinx_version))[0] >= 3) {

+ my $sname = $name;

+ $sname =~ s/^struct //;

+ print "\n\n.. c:struct:: " . $sname . "\n\n";

+ } else {

+ print "\n\n.. c:type:: " . $name . "\n\n";

+ }

print_lineno($declaration_start_line);

$lineprefix = " ";

output_highlight_rst($args{'purpose'});

Add a new script to automate the process of running the Coverity

Scan build tools and uploading the resulting tarball to the

website.

This is intended eventually to be driven from Travis,

but it can be run locally, if you are a maintainer of the

QEMU project on the Coverity Scan website and have the secret

upload token.

The script must be run on a Fedora 30 system. Support for using a

Docker container is added in a following commit.

Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>

Signed-off-by: Peter Maydell <peter.maydell@linaro.org>

Message-id: 20200319193323.2038-6-peter.maydell@linaro.org

---

MAINTAINERS | 5 +

scripts/coverity-scan/run-coverity-scan | 311 ++++++++++++++++++++++++

2 files changed, 316 insertions(+)

create mode 100755 scripts/coverity-scan/run-coverity-scan

diff --git a/MAINTAINERS b/MAINTAINERS

--- a/MAINTAINERS

+++ b/MAINTAINERS

@@ -XXX,XX +XXX,XX @@ M: Markus Armbruster <armbru@redhat.com>

S: Supported

F: scripts/coverity-model.c

+Coverity Scan integration

+M: Peter Maydell <peter.maydell@linaro.org>

+S: Maintained

+F: scripts/coverity-scan/

Device Tree

M: Alistair Francis <alistair.francis@wdc.com>

R: David Gibson <david@gibson.dropbear.id.au>

diff --git a/scripts/coverity-scan/run-coverity-scan b/scripts/coverity-scan/run-coverity-scan

new file mode 100755

index XXXXXXX..XXXXXXX

--- /dev/null

+++ b/scripts/coverity-scan/run-coverity-scan

@@ -XXX,XX +XXX,XX @@

+#!/bin/sh -e

+# Upload a created tarball to Coverity Scan, as per

+# https://scan.coverity.com/projects/qemu/builds/new

+# This work is licensed under the terms of the GNU GPL version 2,

+# or (at your option) any later version.

+# See the COPYING file in the top-level directory.

+#

+# Copyright (c) 2017-2020 Linaro Limited

+# Written by Peter Maydell

+# Note that this script will automatically download and

+# run the (closed-source) coverity build tools, so don't

+# use it if you don't trust them!

+# This script assumes that you're running it from a QEMU source

+# tree, and that tree is a fresh clean one, because we do an in-tree

+# build. (This is necessary so that the filenames that the Coverity

+# Scan server sees are relative paths that match up with the component

+# regular expressions it uses; an out-of-tree build won't work for this.)

+# The host machine should have as many of QEMU's dependencies

+# installed as possible, for maximum coverity coverage.

+# To do an upload you need to be a maintainer in the Coverity online

+# service, and you will need to know the "Coverity token", which is a

+# secret 8 digit hex string. You can find that from the web UI in the

+# project settings, if you have maintainer access there.

+# Command line options:

+# --dry-run : run the tools, but don't actually do the upload

+# --update-tools-only : update the cached copy of the tools, but don't run them

+# --tokenfile : file to read Coverity token from

+# --version ver : specify version being analyzed (default: ask git)

+# --description desc : specify description of this version (default: ask git)

+# --srcdir : QEMU source tree to analyze (default: current working dir)

+# --results-tarball : path to copy the results tarball to (default: don't

+# copy it anywhere, just upload it)

+#

+# User-specifiable environment variables:

+# COVERITY_TOKEN -- Coverity token

+# COVERITY_EMAIL -- the email address to use for uploads (default:

+# looks at your git user.email config)

+# COVERITY_BUILD_CMD -- make command (default: 'make -jN' where N is

+# number of CPUs as determined by 'nproc')

+# COVERITY_TOOL_BASE -- set to directory to put coverity tools

+# (default: /tmp/coverity-tools)

+#

+# You must specify the token, either by environment variable or by

+# putting it in a file and using --tokenfile. Everything else has

+# a reasonable default if this is run from a git tree.

+check_upload_permissions() {

+ # Check whether we can do an upload to the server; will exit the script

+ # with status 1 if the check failed (usually a bad token);

+ # will exit the script with status 0 if the check indicated that we

+ # can't upload yet (ie we are at quota)

+ # Assumes that PROJTOKEN, PROJNAME and DRYRUN have been initialized.

+ echo "Checking upload permissions..."

+

+ if ! up_perm="$(wget https://scan.coverity.com/api/upload_permitted --post-data "token=$PROJTOKEN&project=$PROJNAME" -q -O -)"; then

+ echo "Coverity Scan API access denied: bad token?"

+ exit 1

+ fi

+

+ # Really up_perm is a JSON response with either

+ # {upload_permitted:true} or {next_upload_permitted_at:<date>}

+ # We do some hacky string parsing instead of properly parsing it.

+ case "$up_perm" in

+ *upload_permitted*true*)

+ echo "Coverity Scan: upload permitted"

+ ;;

+ *next_upload_permitted_at*)

+ if [ "$DRYRUN" = yes ]; then

+ echo "Coverity Scan: upload quota reached, continuing dry run"

+ else

+ echo "Coverity Scan: upload quota reached; stopping here"

+ # Exit success as this isn't a build error.

+ exit 0

+ fi

+ ;;

+ *)

+ echo "Coverity Scan upload check: unexpected result $up_perm"

+ exit 1

+ ;;

+ esac

+update_coverity_tools () {

+ # Check for whether we need to download the Coverity tools

+ # (either because we don't have a copy, or because it's out of date)

+ # Assumes that COVERITY_TOOL_BASE, PROJTOKEN and PROJNAME are set.

+ mkdir -p "$COVERITY_TOOL_BASE"

+ cd "$COVERITY_TOOL_BASE"

+ echo "Checking for new version of coverity build tools..."

+ wget https://scan.coverity.com/download/linux64 --post-data "token=$PROJTOKEN&project=$PROJNAME&md5=1" -O coverity_tool.md5.new

+

+ if ! cmp -s coverity_tool.md5 coverity_tool.md5.new; then

+ # out of date md5 or no md5: download new build tool

+ # blow away the old build tool

+ echo "Downloading coverity build tools..."

+ rm -rf coverity_tool coverity_tool.tgz

+ wget https://scan.coverity.com/download/linux64 --post-data "token=$PROJTOKEN&project=$PROJNAME" -O coverity_tool.tgz

+ if ! (cat coverity_tool.md5.new; echo " coverity_tool.tgz") | md5sum -c --status; then

+ echo "Downloaded tarball didn't match md5sum!"

+ exit 1

+ fi

+ # extract the new one, keeping it corralled in a 'coverity_tool' directory

+ echo "Unpacking coverity build tools..."

+ mkdir -p coverity_tool

+ cd coverity_tool

+ tar xf ../coverity_tool.tgz

+ cd ..

+ mv coverity_tool.md5.new coverity_tool.md5

+ fi

+

+ rm -f coverity_tool.md5.new

+}

+

+

+# Check user-provided environment variables and arguments

+DRYRUN=no

+UPDATE_ONLY=no

+

+while [ "$#" -ge 1 ]; do

+ case "$1" in

+ --dry-run)

+ shift

+ DRYRUN=yes

+ ;;

+ --update-tools-only)

+ shift

+ UPDATE_ONLY=yes

+ ;;

+ --version)

+ shift

+ if [ $# -eq 0 ]; then

+ echo "--version needs an argument"

+ exit 1

+ fi

+ VERSION="$1"

+ shift

+ ;;

+ --description)

+ shift

+ if [ $# -eq 0 ]; then

+ echo "--description needs an argument"

+ exit 1

+ fi

+ DESCRIPTION="$1"

+ shift

+ ;;

+ --tokenfile)

+ shift

+ if [ $# -eq 0 ]; then

+ echo "--tokenfile needs an argument"

+ exit 1

+ fi

+ COVERITY_TOKEN="$(cat "$1")"

+ shift

+ ;;