We passed an is_write flag to the fuzz_dma_read_cb function to differentiate between the mapped DMA regions that need to be populated with fuzzed data, and those that don't. We simply passed through the address_space_map is_write parameter. The goal was to cut down on unnecessarily populating mapped DMA regions, when they are not read from. Unfortunately, nothing precludes code from reading from regions mapped with is_write=true. For example, see: https://lists.gnu.org/archive/html/qemu-devel/2021-01/msg04729.html This patch removes the is_write parameter to fuzz_dma_read_cb. As a result, we will fill all mapped DMA regions with fuzzed data, ignoring the specified transfer direction. Signed-off-by: Alexander Bulekov <alxndr@bu.edu> Reviewed-by: Darren Kenny <darren.kenny@oracle.com> Message-Id: <20210120060255.558535-1-alxndr@bu.edu> |
||
---|---|---|
.. | ||
fork_fuzz.c | ||
fork_fuzz.h | ||
fork_fuzz.ld | ||
fuzz.c | ||
fuzz.h | ||
generic_fuzz.c | ||
generic_fuzz_configs.h | ||
i440fx_fuzz.c | ||
meson.build | ||
qos_fuzz.c | ||
qos_fuzz.h | ||
qtest_wrappers.c | ||
virtio_blk_fuzz.c | ||
virtio_net_fuzz.c | ||
virtio_scsi_fuzz.c |