Abrt in seq_handler_fuzzer.cc |
|||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=4965019968864256 Fuzzer: libFuzzer_chromeos_midis_seq_handler_fuzzer Job Type: libfuzzer_asan_chromeos Platform Id: linux Crash Type: Abrt Crash Address: 0x000000000001 Crash State: seq_handler_fuzzer.cc Sanitizer: address (ASAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_asan_chromeos&range=2543205:2543809 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=4965019968864256 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
May 6 2018
,
May 8 2018
The "Reproducer Testcase" link leads to an empty file. The "Regressed" link doesn't seem to work either. I can't seem to reproduce this inside a chroot locally, so I'm going to CC metzman@ and wait for his findings before looking into this further.
,
May 9 2018
I didn't get a chance to look at this yet. Will try today or tomorrow.
,
May 16 2018
The problem is that /dev/snd doesn't exist on the ClusterFuzz bots that run the fuzzer. It's much better for fuzzers to not depend on the underlying system like this. Can the fuzzer be changed so that this file isn't needed or can be faked?
,
Aug 23
The daemon at a minimum needs the presence of the ALSA interface. All the ALSA library commands depend on it. In it's absence the daemon won't be able to initialize successfully (even in the absence of any connected h/w). Having the sound subsystem devnode present is required for running anything related to the daemon. What is the work involved with enabling ALSA on the Clusterfuzz bot kernel?
,
Aug 23
My first impression is that this will not be possible (in a non-crazy way) with the current architecture of Chrome OS fuzzing on ClusterFuzz, since it is just a chroot on Linux. We've been discussing setting up more realistic environments for fuzzing Chrome OS but there are no definite plans yet. I will think more about this.
,
Aug 24
Issue 873603 has been merged into this issue.
,
Sep 12
ClusterFuzz testcase 4965019968864256 appears to be flaky, updating reproducibility label.
,
Sep 12
ClusterFuzz testcase 4965019968864256 is flaky and no longer crashes, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ClusterFuzz
, May 5 2018Labels: ClusterFuzz-Auto-CC