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

Issue 719803 link

Starred by 1 user

Issue metadata

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



Sign in to add a comment

Crash in gpu::gles2::GLES2DecoderPassthroughImpl::DoBindTexture

Project Member Reported by ClusterFuzz, May 9 2017

Issue description

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

Fuzzer: afl_gpu_angle_passthrough_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

Crash Type: UNKNOWN WRITE
Crash Address: 0x000000000000
Crash State:
  gpu::gles2::GLES2DecoderPassthroughImpl::DoBindTexture
  gpu::gles2::GLES2DecoderPassthroughImpl::DoCommands
  gpu::CommandParser::ProcessCommands
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=470009:470101

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


Issue filed automatically.

See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.md for more information.
 
Cc: msrchandra@chromium.org
Components: Internals>GPU>Internals
Labels: Test-Predator-Wrong-CLs M-60
Owner: kbr@chromium.org
Status: Assigned (was: Untriaged)
Predator and CL did not provide any possible suspects.
Using Code Search for the file, "gles2_cmd_decoder_passthrough.cc" assigning to the concern owner.
Suspecting Commit#
https://chromium.googlesource.com/chromium/src/+/69c721ec714b0650dec773173ef4be5a25347a49

@kbr -- Could you please look into the issue, kindly re-assign if this is not related to your changes.
Thank You.

Comment 2 by kbr@chromium.org, May 16 2017

Cc: geoffl...@chromium.org piman@chromium.org
Geoff, are you familiar with these fuzzers running against the pass-through command buffer?

Comment 3 by kbr@chromium.org, May 16 2017

Labels: -Pri-1 Pri-2
Also, since this configuration isn't shipping yet, downgrading to P2.

Yep, I can take this.
Owner: geoffl...@chromium.org

Comment 6 by kbr@chromium.org, May 16 2017

Cc: kbr@chromium.org
Thanks Geoff. Let me know if I can help.

Project Member

Comment 7 by bugdroid1@chromium.org, May 31 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/59d2ca1729430fc7713e642d04a772773248f030

commit 59d2ca1729430fc7713e642d04a772773248f030
Author: geofflang <geofflang@chromium.org>
Date: Wed May 31 15:16:50 2017

Track currently bound external and multisample textures.

This caused assertions in glBindTexture even when binding 0. Caught by
the fuzzer which uses an ES 3.1 context.

BUG= 726265 
BUG= 719933 
BUG= 719803 
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2909683002
Cr-Commit-Position: refs/heads/master@{#475912}

[modify] https://crrev.com/59d2ca1729430fc7713e642d04a772773248f030/gpu/command_buffer/service/gles2_cmd_decoder_passthrough.cc

Project Member

Comment 8 by ClusterFuzz, Jun 2 2017

ClusterFuzz has detected this issue as fixed in range 476373:476444.

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

Fuzzer: afl_gpu_angle_passthrough_fuzzer
Job Type: afl_chrome_asan
Platform Id: linux

Crash Type: Null-dereference WRITE
Crash Address: 0x000000000000
Crash State:
  gpu::gles2::GLES2DecoderPassthroughImpl::DoBindTexture
  gpu::gles2::GLES2DecoderPassthroughImpl::DoCommands
  ProcessCommands
  
Sanitizer: address (ASAN)

Regressed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=470009:470101
Fixed: https://clusterfuzz.com/revisions?job=afl_chrome_asan&range=476373:476444

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


See https://chromium.googlesource.com/chromium/src/+/master/testing/libfuzzer/reproducing.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, Jun 2 2017

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

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

Sign in to add a comment