diff options
| author | Daniel Verkamp <dverkamp@chromium.org> | 2019-12-11 12:15:29 -0800 |
|---|---|---|
| committer | Commit Bot <commit-bot@chromium.org> | 2019-12-12 19:44:07 +0000 |
| commit | 5118381f2a7486110d77f3aad8d387f1c3c612bf (patch) | |
| tree | c249c6adb8d3156c6585223a973c146d77f89088 /gpu_display/src/generated/xlib.rs | |
| parent | afa30327f8db8b23e517d2aec70d8cc2823c84a0 (diff) | |
| download | crosvm-5118381f2a7486110d77f3aad8d387f1c3c612bf.tar crosvm-5118381f2a7486110d77f3aad8d387f1c3c612bf.tar.gz crosvm-5118381f2a7486110d77f3aad8d387f1c3c612bf.tar.bz2 crosvm-5118381f2a7486110d77f3aad8d387f1c3c612bf.tar.lz crosvm-5118381f2a7486110d77f3aad8d387f1c3c612bf.tar.xz crosvm-5118381f2a7486110d77f3aad8d387f1c3c612bf.tar.zst crosvm-5118381f2a7486110d77f3aad8d387f1c3c612bf.zip | |
fuzz: add block_size to block_fuzzer constructor
Fix the build of block_fuzzer after "devices: block: add block_size option for disks". It might be nice to generate the block size from the random fuzz data, but that would complicate things (we'd have to handle failure of Block::new due to invalid sizes), so let's leave that as a future improvement for now and just use a block_size of 512 to match previous behavior. BUG=chromium:942700 TEST=`USE='asan fuzzer' emerge-nami crosvm` Change-Id: Ia16ef6a57fc8ce4407f8ec9dda0e708302916c4c Signed-off-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/1962535 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Dylan Reid <dgreid@chromium.org>
Diffstat (limited to 'gpu_display/src/generated/xlib.rs')
0 files changed, 0 insertions, 0 deletions