Misaligned-address in vrend_decode_block |
|||||||||
Issue descriptionDetailed report: https://clusterfuzz.com/testcase?key=5223013728124928 Fuzzer: libFuzzer_chromeos_virgl_fuzzer Job Type: libfuzzer_ubsan_chromeos Platform Id: linux Crash Type: Misaligned-address Crash Address: Crash State: vrend_decode_block virgl_fuzzer.c Sanitizer: undefined (UBSAN) Reproducer Testcase: https://clusterfuzz.com/download?testcase_id=5223013728124928 Issue filed automatically. See https://chromium.googlesource.com/chromiumos/docs/+/master/fuzzing.md#Reproducing-crashes-from-ClusterFuzz for more information.
,
Oct 30
Didn't we change the OWNERS file to add pwang@? If not we should
,
Oct 31
We did: https://cs.corp.google.com/chromeos_public/src/third_party/chromiumos-overlay/media-libs/virglrenderer/files/fuzzer-OWNERS?q=fuzzer-owners+virglrenderer&dr metzman@ Do you know what's going on here?
,
Oct 31
Thanks for pointing this out, I'll take a look today.
,
Oct 31
David: I think the issue is that pwang@ is in fact not in the owners file. pwang@ isn't in the link you sent me. Or am I misunderstanding the problem?
,
Oct 31
I think the problem here is ddmail@google.com is not in the cc list and all the other email addresses are listed. On Wed, Oct 31, 2018, 16:47 metzman via monorail < monorail+v2.2965673606@chromium.org wrote:
,
Nov 1
Ah. Didn't realize ddmail was your LDAP. Looking into this.
,
Nov 1
It looks like our bug filing code limits CCing to 3 email address. inferno@ Do you think we should get rid of this limit? I don't think there is value in only CCing the first 3 email addresses (maybe if we randomly picked them).
,
Nov 1
If you need to remove someone to make it work, then you can also remove me.
,
Nov 1
We can't cc everyone, as a lot of OWNERS files have like more than a dozen owners. E.g. https://cs.chromium.org/chromium/src/content/OWNERS?g=0&l=12, so it feels more like a spam. We can increase limit to 4/5. also, can do the randomized picking of these if needed.
,
Nov 15
I've changed this code to CC up to 5 people (will pick 5 at random if there are more than 5), so you shouldn't have this problem again.
,
Nov 28
,
Dec 1
ClusterFuzz testcase 5223013728124928 appears to be flaky, updating reproducibility label.
,
Dec 1
ClusterFuzz testcase 5223013728124928 is flaky and no longer crashes, so closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Dec 4
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.
,
Dec 4
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by ClusterFuzz
, Oct 30Labels: ClusterFuzz-Auto-CC