Null-dereference READ in __GI___pthread_mutex_lock |
||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5789177355173888 Fuzzer: libFuzzer_sequence_manager_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000010 Crash State: __GI___pthread_mutex_lock base::internal::LockImpl::Lock base::sequence_manager::ThreadManager::GetTaskQueueFor Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=586754:586756 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5789177355173888 Issue filed automatically. See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
,
Aug 29
Automatically adding ccs based on suspected regression changelists: SQM Fuzzer: Add support for cross-thread posting. by farahcharab@google.com - https://chromium.googlesource.com/chromium/src/+/f67097b4acac3a85de15f259ee38295da301802e If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.
,
Aug 29
Predator has provided one possible suspect provided CL: https://chromium.googlesource.com/chromium/src/+/f67097b4acac3a85de15f259ee38295da301802e Since author is not visited crbug.com recently, hence assigning it to reviewer for further triage.
,
Aug 29
,
Dec 1
ClusterFuzz testcase 5789177355173888 appears to be flaky, updating reproducibility label.
,
Dec 1
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
,
Dec 1
Please ignore the last comment about testcase being unreproducible. The testcase is still reproducible. This happened due to a code refactoring on ClusterFuzz side, and the underlying root cause is now fixed. Resetting the label back to Reproducible. Sorry about the inconvenience caused from these incorrect notifications.
,
Dec 6
ClusterFuzz has detected this issue as fixed in range 614319:614322. Detailed report: https://clusterfuzz.com/testcase?key=5789177355173888 Fuzzer: libFuzzer_sequence_manager_fuzzer Fuzz target binary: sequence_manager_fuzzer Job Type: libfuzzer_chrome_ubsan Platform Id: linux Crash Type: Null-dereference READ Crash Address: 0x000000000010 Crash State: __GI___pthread_mutex_lock base::internal::LockImpl::Lock base::sequence_manager::ThreadManager::GetTaskQueueFor Sanitizer: undefined (UBSAN) Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=586754:586756 Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=614319:614322 Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5789177355173888 See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Dec 6
ClusterFuzz testcase 5789177355173888 is verified as fixed, so closing issue as verified. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue. |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ClusterFuzz
, Aug 29Labels: Test-Predator-Auto-Components