New issue
Advanced search Search tips

Issue 904712 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Nov 17
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

Abrt in spirv_cross::Compiler::parse

Project Member Reported by ClusterFuzz, Nov 13

Issue description

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

Fuzzer: libFuzzer_dawn_spirv_cross_msl_full_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x0539003285f6
Crash State:
  spirv_cross::Compiler::parse
  spirv_cross::CompilerGLSL::CompilerGLSL
  GLSLFullFuzzTask
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=607427:607452

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Project Member

Comment 1 by ClusterFuzz, Nov 13

Cc: kainino@chromium.org cwallez@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.
Project Member

Comment 2 by ClusterFuzz, Nov 13

Labels: Test-Predator-Auto-Owner
Owner: rharrison@chromium.org
Status: Assigned (was: Untriaged)
Automatically assigning owner based on suspected regression changelist https://dawn.googlesource.com/dawn/+/9854295ff60b96f9c96c2711c55d2562c080dae9 (Add fuzzers for SPIRV-Cross).

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label. If you aren't the correct owner for this issue, please unassign yourself as soon as possible so it can be re-triaged.
Cc: rharrison@chromium.org
Owner: fjhenigman@chromium.org
Components: Internals>GPU>Dawn
Owner: rharrison@chromium.org
This shouldn't be happening, this is exactly the error that the signal trap is supposed to catch.
Project Member

Comment 5 by bugdroid1@chromium.org, Nov 14

The following revision refers to this bug:
  https://dawn.googlesource.com/dawn/+/499bc0318d40efa7da12dbddceccb10d289918aa

commit 499bc0318d40efa7da12dbddceccb10d289918aa
Author: Ryan Harrison <rharrison@chromium.org>
Date: Wed Nov 14 21:04:16 2018

Set correct ASAN flags for SPIRV-cross fuzzers

These fuzzers currently depend on being able to change the signal
handler at runtime, but the default flags being used forbid this. This
CL overrides the upstream default to allow changing the handler.

BUG= chromium:904725 , chromium:904712 

Change-Id: I68423564981b7f2e39f7c00744b92da982cf19e9
Reviewed-on: https://dawn-review.googlesource.com/c/2361
Commit-Queue: Corentin Wallez <cwallez@chromium.org>
Reviewed-by: Max Moroz <mmoroz@chromium.org>
Reviewed-by: Corentin Wallez <cwallez@chromium.org>

[modify] https://crrev.com/499bc0318d40efa7da12dbddceccb10d289918aa/src/fuzzers/BUILD.gn

Status: Fixed (was: Assigned)
Status: Assigned (was: Fixed)
Project Member

Comment 8 by ClusterFuzz, Nov 17

ClusterFuzz has detected this issue as fixed in range 608346:608347.

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

Fuzzer: libFuzzer_dawn_spirv_cross_msl_full_fuzzer
Job Type: libfuzzer_chrome_asan
Platform Id: linux

Crash Type: Abrt
Crash Address: 0x0539003285f6
Crash State:
  spirv_cross::Compiler::parse
  spirv_cross::CompilerGLSL::CompilerGLSL
  GLSLFullFuzzTask
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=607427:607452
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_asan&range=608346:608347

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

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.
Project Member

Comment 9 by ClusterFuzz, Nov 17

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 6271424660242432 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