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

Issue 735167 link

Starred by 1 user

Issue metadata

Status: Verified
Owner: ----
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Undefined-shift in sw::Shader::analyzeSamplers

Project Member Reported by ClusterFuzz, Jun 20 2017

Issue description

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

Fuzzer: inferno_webbot
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Undefined-shift
Crash Address: 
Crash State:
  sw::Shader::analyzeSamplers
  sw::PixelShader::analyze
  es2::Program::link
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=471618:471627

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


Issue filed automatically.

See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
 
Cc: msrchandra@chromium.org
Components: Internals>GPU>SwiftShader
Labels: M-63 Test-Predator-Wrong-CLs CF-NeedsTriage
Redo Task has been performed for a new regression range as the suspected commits are very old.
Thank You.
Project Member

Comment 2 by ClusterFuzz, Sep 23 2017

ClusterFuzz has detected this issue as fixed in range 503937:503938.

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

Fuzzer: inferno_webbot
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Undefined-shift
Crash Address: 
Crash State:
  sw::Shader::analyzeSamplers
  sw::PixelShader::analyze
  es2::Program::link
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=463855:463874
Fixed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=503937:503938

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

See https://github.com/google/clusterfuzz-tools 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 3 by ClusterFuzz, Sep 23 2017

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