CSP code uses SpaceSplitString from a worker but it isn't thread safe |
|||||
Issue descriptionDetailed report: https://cluster-fuzz.appspot.com/testcase?key=6033865827418112 Fuzzer: ochang_domfuzzer Job Type: linux_tsan_chrome_mp Platform Id: linux Crash Type: Data race READ 4 Crash Address: 0x7d080002df50 Crash State: blink::SpaceSplitString::Data::create blink::SpaceSplitString::set blink::Element::classAttributeChanged Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_tsan_chrome_mp&range=389097:389209 Minimized Testcase (0.75 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94whmkW4EjQgugUAseZ8qocikPeJ6FZ1w0slILHuZHlFkWIwqq6-bWOJITQzLB0fIRNUlHO-bdRjUIisJnEMfLp9YBKjpZ4r15b8XT1smpAnm9QAoUEpTH1oLUV8lSQ-_yoJ8vk0RYzdeNqoMcxeIUGXLRX-g?testcase_id=6033865827418112 Filer: ajha See https://dev.chromium.org/Home/chromium-security/bugs/reproducing-clusterfuzz-bugs for more information.
,
Jul 19 2016
This is a bug in the CSP code which is using SpaSpaceSplitString which has a static cache, but using it in workers.
,
Sep 29 2016
ClusterFuzz has detected this issue as fixed in range 421045:421049. Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6033865827418112 Fuzzer: ochang_domfuzzer Job Type: linux_tsan_chrome_mp Platform Id: linux Crash Type: Data race READ 4 Crash Address: 0x7d080002df50 Crash State: blink::SpaceSplitString::Data::create blink::SpaceSplitString::set blink::Element::classAttributeChanged Regressed: https://cluster-fuzz.appspot.com/revisions?job=linux_tsan_chrome_mp&range=389097:389209 Fixed: https://cluster-fuzz.appspot.com/revisions?job=linux_tsan_chrome_mp&range=421045:421049 Minimized Testcase (0.75 Kb): https://cluster-fuzz.appspot.com/download/AMIfv94whmkW4EjQgugUAseZ8qocikPeJ6FZ1w0slILHuZHlFkWIwqq6-bWOJITQzLB0fIRNUlHO-bdRjUIisJnEMfLp9YBKjpZ4r15b8XT1smpAnm9QAoUEpTH1oLUV8lSQ-_yoJ8vk0RYzdeNqoMcxeIUGXLRX-g?testcase_id=6033865827418112 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.
,
Oct 18 2016
,
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 ajha@chromium.org
, Jul 14 2016Components: Tools>Test>FindIt>NoResult
Labels: Te-Logged M-52
Owner: esprehn@chromium.org
Status: Assigned (was: Available)