[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[RFC 0/8] Introduce an extensible static analyzer
From: |
Alberto Faria |
Subject: |
[RFC 0/8] Introduce an extensible static analyzer |
Date: |
Sat, 2 Jul 2022 12:33:23 +0100 |
This series introduces a static analyzer for QEMU. It consists of a
single static-analyzer.py script that relies on libclang's Python
bindings, and provides a common framework on which arbitrary static
analysis checks can be developed and run against QEMU's code base.
Summary of the series:
- Patch 1 adds the base static analyzer, along with a simple check
that finds static functions whose return value is never used, and
patch 2 fixes some occurrences of this.
- Patch 3 adds a check to ensure that non-coroutine_fn functions don't
perform direct calls to coroutine_fn functions, and patch 4 fixes
some violations of this rule.
- Patch 5 adds a check to enforce coroutine_fn restrictions on
function pointers, namely around assignment and indirect calls, and
patch 6 fixes some problems it detects. (Implementing this check
properly is complicated, since AFAICT annotation attributes cannot
be applied directly to types. This part still needs a lot of work.)
- Patch 7 introduces a no_coroutine_fn marker for functions that
should not be called from coroutines, makes generated_co_wrapper
evaluate to no_coroutine_fn, and adds a check enforcing this rule.
Patch 8 fixes some violations that it finds.
The current primary motivation for this work is enforcing rules around
block layer coroutines, which is why most of the series focuses on that.
However, the static analyzer is intended to be sufficiently generic to
satisfy other present and future QEMU static analysis needs.
This is very early work-in-progress, and a lot is missing. One notable
omission is build system integration, including keeping track of which
translation units have been modified and need re-analyzing.
Performance is bad, but there is a lot of potential for optimization,
such as avoiding redundant AST traversals. Switching to C libclang is
also a possibility, although Python makes it easy to quickly prototype
new checks, which should encourage adoption and contributions.
The script takes a path to the build directory, and any number of paths
to directories or files to analyze. Example run on a 12-thread laptop:
$ time ./static-analyzer.py build block
block/commit.c:525:15: non-coroutine_fn function calls coroutine_fn
block/nbd.c:206:5: non-coroutine_fn function calls coroutine_fn
[...]
block/ssh.c:1167:13: non-coroutine_fn function calls coroutine_fn
block/nfs.c:229:27: non-coroutine_fn function calls coroutine_fn
Analyzed 79 translation units.
real 0m45.277s
user 7m55.496s
sys 0m1.445s
You will need libclang's Python bindings to run this. On Fedora, `dnf
install python3-clang` should suffice.
Alberto Faria (8):
Add an extensible static analyzer
Drop some unused static function return values
static-analyzer: Enforce coroutine_fn restrictions for direct calls
Fix some direct calls from non-coroutine_fn to coroutine_fn
static-analyzer: Enforce coroutine_fn restrictions on function
pointers
Fix some coroutine_fn indirect calls and pointer assignments
block: Add no_coroutine_fn marker
Avoid calls from coroutine_fn to no_coroutine_fn
block/block-backend.c | 15 +-
block/copy-before-write.c | 3 +-
block/dirty-bitmap.c | 6 +-
block/file-posix.c | 6 +-
block/io.c | 34 +-
block/iscsi.c | 3 +-
block/parallels.c | 4 +-
block/qcow2-bitmap.c | 6 +-
block/qcow2-refcount.c | 2 +-
block/qcow2.h | 14 +-
block/qed-table.c | 2 +-
block/qed.c | 8 +-
block/quorum.c | 5 +-
block/vmdk.c | 4 +-
block/vpc.c | 9 +-
block/vvfat.c | 11 +-
include/block/block-common.h | 2 +-
include/block/block-io.h | 7 +-
include/block/block_int-common.h | 12 +-
include/qemu/coroutine.h | 25 +
static-analyzer.py | 890 +++++++++++++++++++++++++++++++
21 files changed, 987 insertions(+), 81 deletions(-)
create mode 100755 static-analyzer.py
--
2.36.1
- [RFC 0/8] Introduce an extensible static analyzer,
Alberto Faria <=
- [RFC 1/8] Add an extensible static analyzer, Alberto Faria, 2022/07/02
- [RFC 2/8] Drop some unused static function return values, Alberto Faria, 2022/07/02
- [RFC 3/8] static-analyzer: Enforce coroutine_fn restrictions for direct calls, Alberto Faria, 2022/07/02
- [RFC 4/8] Fix some direct calls from non-coroutine_fn to coroutine_fn, Alberto Faria, 2022/07/02
- [RFC 5/8] static-analyzer: Enforce coroutine_fn restrictions on function pointers, Alberto Faria, 2022/07/02