Re: [PATCH v5 00/16] Add a Generic Virtual Device Fuzzer

[Thomas Huth]

On 21/10/2020 03.07, Alexander Bulekov wrote:
> v5:
>     - Replace GArray-based predefined fuzzer configs with a static
>       struct array
>     - "General" -> "Generic"
>     - Fix bugs with wrong timeout denominator and skipping DMA memwrites
>       without QTEST_LOG
> v4:
>     - Replace yaml + c template-based oss-fuzz configs, with C code to
>       register a FuzzTarget for each config (as suggested by Paolo)
>     - Replicate the functionality of address_space_write_rom to ensure
>       matching behavior when QTEST_LOG is enabled
>     - Improve code documentation/comments
>     - Small formatting changes
> v3:
>       - Use flatviews to help select regions for fuzzing 
>       - Meson-related changes
>     - Add some documentation
>       - Improve minimalization script to trim write{bwlq} commands
> v2:
>       - Remove QOS dependency.
>       - Add a custom crossover function
>       - Fix broken minimization scripts
>       - Fixes to the IO region and DMA handling code
> 
> This is a general virtual-device fuzzer, designed to fuzz devices over Port 
> IO,
> MMIO, and DMA.

 Hi Alexander,

this fails to compile in the Gitlab-CI:

https://gitlab.com/huth/qemu/-/jobs/803091952#L2308

../softmmu/memory.c: In function 'flatview_for_each_range':
2309../softmmu/memory.c:663:24: error: incompatible type for argument 1 of 'cb'
2310         if (cb(fr->addr.start, fr->addr.size, fr->mr, opaque))
2311                ~~~~~~~~^~~~~~
2312../softmmu/memory.c:663:24: note: expected 'ram_addr_t' {aka 'unsigned
int'} but argument is of type 'Int128' {aka 'struct Int128'}
2313../softmmu/memory.c:663:40: error: incompatible type for argument 2 of 'cb'
2314         if (cb(fr->addr.start, fr->addr.size, fr->mr, opaque))
2315                                ~~~~~~~~^~~~~
2316../softmmu/memory.c:663:40: note: expected 'ram_addr_t' {aka 'unsigned
int'} but argument is of type 'Int128' {aka 'struct Int128'}

 Thomas