next->value()->IsFixedArray() in wasm-module.cc |
|||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=5090414011088896 Fuzzer: mbarbella_js_mutation Job Type: linux_asan_d8_v8_mipsel_dbg Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: next->value()->IsFixedArray() in wasm-module.cc Regressed: V8: r39794:39795 Minimized Testcase (2.05 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94gztVoGcERY9nTmXCuihHp-28HwgbCo47KmsF74cVRK_VVDueYiihGxjnCqPZY8t8JASdTAbxe05gKK4102bBdmh09lNy40UXqkejfIZTq_BS3WA5eBV_XoQOFuVx3IOq9sx8OdOovwIhD9gLv3iZauvDrJw?testcase_id=5090414011088896 Issue manually filed by: mstarzinger See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Sep 28 2016
Yep, this is a corner case with the handling of weak lists during instantiation. mtrofin@ had a GC-based solution for this before, but I will find a solution for this without an explicit GC tomorrow.
,
Sep 29 2016
Fix available, https://codereview.chromium.org/2371403003/ (incl. regression test)
,
Sep 29 2016
The following revision refers to this bug: https://chromium.googlesource.com/v8/v8.git/+/aff5ab11321d9a9d297260d32d0a004bd348913d commit aff5ab11321d9a9d297260d32d0a004bd348913d Author: mtrofin <mtrofin@chromium.org> Date: Thu Sep 29 04:24:18 2016 [wasm] fix for GC during instantiation. BUG= chromium:651070 Review-Url: https://codereview.chromium.org/2371403003 Cr-Commit-Position: refs/heads/master@{#39848} [modify] https://crrev.com/aff5ab11321d9a9d297260d32d0a004bd348913d/src/wasm/wasm-module.cc [add] https://crrev.com/aff5ab11321d9a9d297260d32d0a004bd348913d/test/mjsunit/regress/wasm/regression-02862.js
,
Sep 29 2016
ClusterFuzz has detected this issue as fixed in range 39837:39838. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=5090414011088896 Fuzzer: mbarbella_js_mutation Job Type: linux_asan_d8_v8_mipsel_dbg Platform Id: linux Crash Type: CHECK failure Crash Address: Crash State: next->value()->IsFixedArray() in wasm-module.cc Regressed: V8: r39794:39795 Fixed: V8: r39837:39838 Minimized Testcase (2.05 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94gztVoGcERY9nTmXCuihHp-28HwgbCo47KmsF74cVRK_VVDueYiihGxjnCqPZY8t8JASdTAbxe05gKK4102bBdmh09lNy40UXqkejfIZTq_BS3WA5eBV_XoQOFuVx3IOq9sx8OdOovwIhD9gLv3iZauvDrJw?testcase_id=5090414011088896 See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information. If you suspect that the result above is incorrect, try re-doing that job on the test case report page.
,
Sep 29 2016
ClusterFuzz testcase is verified as fixed, closing issue. If this is incorrect, please add ClusterFuzz-Wrong label and re-open the issue.
,
Nov 22 2016
Removing EditIssue view restrictions from ClusterFuzz filed bugs. If you believe that this issue should still be restricted, please reapply the label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by mstarzinger@chromium.org
, Sep 28 2016Owner: titzer@chromium.org
Status: Assigned (was: Untriaged)