New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 907051 link

Starred by 1 user
Status: Untriaged
Owner:
lakshm...@chromium.org
Cc:
█ gmx@chromium.org
lakshm...@chromium.org
█ manojguptamanojgupta@chromium.org
cmt...@chromium.org
█ chongjiang@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Undefined-shift in quipper::PerfReader::set_metadata_mask_bit

Project Member Reported by ClusterFuzz, Nov 20 
Detailed report: https://clusterfuzz.com/testcase?key=6130499468394496

Fuzzer: libFuzzer_chromeos_quipper_perf_reader_read_fuzzer
Job Type: libfuzzer_ubsan_chromeos
Platform Id: linux

Crash Type: Undefined-shift
Crash Address: 
Crash State:
  quipper::PerfReader::set_metadata_mask_bit
  quipper::PerfReader::ReadMetadataWithoutHeader
  quipper::PerfReader::ReadHeaderFeature
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_ubsan_chromeos&range=3110653:3111064

Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=6130499468394496

Issue filed automatically.

See https://chromium.googlesource.com/chromiumos/docs/+/master/fuzzing.md#Reproducing-crashes-from-ClusterFuzz for more information.
Project Member

Comment 1 by ClusterFuzz, Nov 20

Cc: lakshm...@chromium.org gmx@chromium.org chongjiang@chromium.org
Labels: ClusterFuzz-Auto-CC
Automatically adding ccs based on OWNERS file / target commit history.

If this is incorrect, please add ClusterFuzz-Wrong label.

Comment 2 by manojgupta@chromium.org, Nov 20

Cc: -manojgupta@google.com cmt...@chromium.org manojguptamanojgupta@chromium.org
Owner: lakshm...@chromium.org
Project Member

Comment 3 by ClusterFuzz, Dec 1

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 6130499468394496 appears to be flaky, updating reproducibility label.

Comment 4 by infe...@chromium.org, Dec 1

Labels: -Unreproducible Reproducible
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.
Project Member

Comment 5 by ClusterFuzz, Dec 4

Labels: -Reproducible Unreproducible
ClusterFuzz testcase 6130499468394496 appears to be flaky, updating reproducibility label.

Comment 6 by metzman@chromium.org, Dec 4

Labels: -Unreproducible Reproducible
Please ignore the last comment about testcase being unreproducible. 
The testcase is still reproducible. 
This was caused by a bug in ClusterFuzz that has been fixed. 
Sorry again for the inconvenience.
►

Sign in to add a comment