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

Issue 804072 link

Starred by 1 user
Status: Assigned
Owner:
sugoi@chromium.org
Cc:
█ capn@google.com
sugoi@google.com
sugoi@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Integer-overflow in es2::Device::ClipSrcRect

Project Member Reported by ClusterFuzz, Jan 20 2018 
Detailed report: https://clusterfuzz.com/testcase?key=5018870208528384

Fuzzer: inferno_twister_c
Job Type: linux_ubsan_chrome
Platform Id: linux

Crash Type: Integer-overflow
Crash Address: 
Crash State:
  es2::Device::ClipSrcRect
  es2::Context::blitFramebuffer
  glBlitFramebuffer
  
Sanitizer: undefined (UBSAN)

Regressed: https://clusterfuzz.com/revisions?job=linux_ubsan_chrome&range=529742:529750

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

Issue filed automatically.

See https://github.com/google/clusterfuzz-tools for more information.
Project Member

Comment 1 by ClusterFuzz, Jan 20 2018

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

If this is incorrect, please apply the Test-Predator-Wrong-Components label.
Project Member

Comment 2 by ClusterFuzz, Jan 20 2018

Cc: capn@google.com sugoi@google.com
Labels: Test-Predator-Auto-CC
Automatically adding ccs based on suspected regression changelists:

Allow blitting with out of bounds source coordinates by sugoi@google.com - https://swiftshader.googlesource.com/SwiftShader/+/73771b1f950bd562ea8ad4f502551ef7d3caacbd

Refactor read buffer access. by capn@google.com - https://swiftshader.googlesource.com/SwiftShader/+/3be576c091d4dd99f8b24f0a8740fe76301de965

Untangle internal & implementation format. by capn@google.com - https://swiftshader.googlesource.com/SwiftShader/+/c61f46b8f057aec5bffb87d4619b2994c0105857

If this is incorrect, please let us know why and apply the Test-Predator-Wrong-CLs label.

Comment 3 by piman@chromium.org, Jan 26 2018

Owner: capn@chromium.org

Comment 4 by piman@chromium.org, Jan 26 2018

Status: Assigned (was: Untriaged)

Comment 5 by capn@chromium.org, Feb 5 2018

Owner: sugoi@chromium.org
►

Sign in to add a comment