Automatically adding ccs based on OWNERS file / target commit history.

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

Will you look into this and see if this is an upstream problem and either address it or reassign it appropriately?

I have no access to the report mentioned in #1. 
Running the testcase locally pass on my setup.

ClusterFuzz has detected this issue as fixed in range 2959649:2966823.

Detailed report: https://clusterfuzz.com/testcase?key=6207976233500672

Fuzzer: libFuzzer_chromeos_virgl_fuzzer
Job Type: libfuzzer_ubsan_chromeos
Platform Id: linux

Crash Type: Index-out-of-bounds
Crash Address: 
Crash State:
  vrend_set_single_ssbo
  vrend_decode_block
  virgl_fuzzer.c
  
Sanitizer: undefined (UBSAN)

Recommended Security Severity: Medium

Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_ubsan_chromeos&range=2959649:2966823

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

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

If you suspect that the result above is incorrect, try re-doing that job on the test case report page.

ClusterFuzz testcase 6207976233500672 is verified as fixed, so closing issue as verified.

If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot