summary refs log tree commit diff
diff options
context:
space:
mode:
authorDaniel Verkamp <dverkamp@chromium.org>2019-10-09 17:22:08 -0700
committerCommit Bot <commit-bot@chromium.org>2019-10-24 00:06:54 +0000
commit7154c0f1e312f6b70e55eef8d7ecdcc47600ac36 (patch)
treefa9be99f4cc39ac6c598d75da5f9fcd5285a579e
parent193d68404643c55558dba5145453666a4adbd2e8 (diff)
downloadcrosvm-7154c0f1e312f6b70e55eef8d7ecdcc47600ac36.tar
crosvm-7154c0f1e312f6b70e55eef8d7ecdcc47600ac36.tar.gz
crosvm-7154c0f1e312f6b70e55eef8d7ecdcc47600ac36.tar.bz2
crosvm-7154c0f1e312f6b70e55eef8d7ecdcc47600ac36.tar.lz
crosvm-7154c0f1e312f6b70e55eef8d7ecdcc47600ac36.tar.xz
crosvm-7154c0f1e312f6b70e55eef8d7ecdcc47600ac36.tar.zst
crosvm-7154c0f1e312f6b70e55eef8d7ecdcc47600ac36.zip
fuzz: remove misleading block fuzzer comment
This looks like it's copied from the qcow fuzzer, and it doesn't apply
to the block fuzzer.  The actual behavior of the block fuzzer is
correctly described by the comment later in the file.

BUG=None
TEST=`USE='asan fuzzer' emerge-nami crosvm`

Change-Id: I9ccd6deba44af8b8df471ee0078ace385696151f
Signed-off-by: Daniel Verkamp <dverkamp@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/1853698
Reviewed-by: Dylan Reid <dgreid@chromium.org>
Tested-by: kokoro <noreply+kokoro@google.com>
-rw-r--r--fuzz/block_fuzzer.rs2
1 files changed, 0 insertions, 2 deletions
diff --git a/fuzz/block_fuzzer.rs b/fuzz/block_fuzzer.rs
index 6dd3cf2..f25e40a 100644
--- a/fuzz/block_fuzzer.rs
+++ b/fuzz/block_fuzzer.rs
@@ -22,8 +22,6 @@ const DESC_SIZE: u64 = 16; // Bytes in one virtio descriptor.
 const QUEUE_SIZE: u16 = 16; // Max entries in the queue.
 const CMD_SIZE: usize = 16; // Bytes in the command.
 
-// Take the first 64 bits of data as an address and the next 64 bits as data to
-// store there. The rest of the data is used as a qcow image.
 #[export_name = "LLVMFuzzerTestOneInput"]
 pub fn test_one_input(data: *const u8, size: usize) -> i32 {
     // We cannot unwind past ffi boundaries.