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

Issue 781142 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Null-dereference READ in gl::GLApiBase::glPointParameteriFn

Project Member Reported by ClusterFuzz, Nov 3 2017

Issue description

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

Fuzzer: libFuzzer_gpu_angle_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  gl::GLApiBase::glPointParameteriFn
  gpu::gles2::GLES2DecoderImpl::Initialize
  gpu::CommandBufferSetup::InitDecoder
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=513343:513367

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

Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reference.md for more information.
 
Cc: msrchandra@chromium.org pnangunoori@chromium.org
Components: Internals>GPU>ANGLE
Labels: M-64
Owner: junov@chromium.org
Status: Assigned (was: Untriaged)
Test Predator has given the following results:

Allow blacklisting of use of GpuMemoryBuffers as render targets. by junov@chromium.org
Suspected changelist touched file(s) in the directory gpu/command_buffer/service, which appears in the stack trace.
Suspected changelist touched file(s) associated with the component Internals>GPU>Internals, which we believe is related to this testcase based on information in OWNERS files.

@junov -- Could you please look into this issue, kindly reassign if it has nothing to do with your changes.

Thank You.
Project Member

Comment 2 by ClusterFuzz, Nov 3 2017

Components: Internals>GPU>Internals
Labels: Test-Predator-AutoComponents
Automatically applying components based on crash stacktrace and information from OWNERS files.

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Labels: Test-Predator-Auto-CC
Labels: -Test-Predator-AutoComponents Test-Predator-Auto-Components
Labels: -Test-Predator-Auto-CC

Comment 6 by piman@chromium.org, Nov 9 2017

Cc: geoffl...@chromium.org
Labels: -Pri-1 Pri-2
Owner: piman@chromium.org
Unrelated to that CL.

The fuzzer tries a workaround that doesn't make sense on ANGLE. I'll see if I can easily squash it, but it's not something that matters for production.
Project Member

Comment 7 by ClusterFuzz, Nov 10 2017

ClusterFuzz has detected this issue as fixed in range 515212:515249.

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

Fuzzer: libFuzzer_gpu_angle_fuzzer
Job Type: libfuzzer_chrome_ubsan
Platform Id: linux

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  gl::GLApiBase::glPointParameteriFn
  gpu::gles2::GLES2DecoderImpl::Initialize
  gpu::CommandBufferSetup::InitDecoder
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=513343:513367
Fixed: https://clusterfuzz.com/revisions?job=libfuzzer_chrome_ubsan&range=515212:515249

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

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 8 by ClusterFuzz, Nov 10 2017

Labels: ClusterFuzz-Verified
Status: Verified (was: Assigned)
ClusterFuzz testcase 5225261523271680 is verified as fixed, so closing issue as verified.

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

Comment 9 by piman@chromium.org, Nov 13 2017

Cc: piman@chromium.org
 Issue 784191  has been merged into this issue.

Comment 10 by piman@chromium.org, Nov 13 2017

Labels: -ClusterFuzz-Verified ClusterFuzz-Wrong
Status: Assigned (was: Verified)
Shouldn't have been closed.

Sign in to add a comment