Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Issue 333885 Stack-use-after-return in _mesa_optimize_program
Starred by 5 users Project Member Reported by clusterf...@chromium.org, Jan 13 2014 Back to list
Status: Fixed
Owner:
Closed: Feb 2014
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 1
Type: Bug-Security
Nag



Sign in to add a comment
Detailed report: https://cluster-fuzz.appspot.com/testcase?key=6290276029038592

Fuzzer: Amtinits_glsl_mutation
Job Type: Linux_asan_chrome_mp

Crash Type: Stack-buffer-overflow READ 4
Crash Address: 0x7fecdf8df17c
Crash State:
  - crash stack -
  _mesa_optimize_program
  _mesa_ir_link_shader
  _mesa_glsl_link_shader
  
Regressed: https://cluster-fuzz.appspot.com/revisions?range=226545:226626

Minimized Testcase (16.90 Kb): https://cluster-fuzz.appspot.com/download/AMIfv97Kyy4V0_NAB1K6VwF-M-lRMwb_n8cZxfNiFbQt3Y_2t9T294qI-H9NGKZnXmIRr2DERKO6Jug_1PMj275dPz_o9iZmD86ZAPPWX7ZabvpTIaGNQknp7Ij6IYXvbIJIYxzWNwRq4GYMuJv7Rwt79XBkHQYTSsAkGOtay7-RwMR5Ucbif30
 
Cc: kcc@chromium.org
Labels: -Security_Severity-Medium Security_Severity-High
Owner: kbr@chromium.org
Status: Assigned
assert(inst->DstReg.Index < MAX_PROGRAM_OUTPUTS);
         prevWriteMask = outputWrites[inst->DstReg.Index];
         outputWrites[inst->DstReg.Index] |= inst->DstReg.WriteMask;

We both read and write on the overflowed address. Fixing severity.

This is yet another bug in mesa. Does this impact ChromeOS ?
Project Member Comment 2 by clusterf...@chromium.org, Jan 13 2014
Labels: -M-31 M-32 Pri-1
Comment 3 by kbr@chromium.org, Jan 13 2014
Cc: zmo@chromium.org bajones@chromium.org marc...@chromium.org kbr@chromium.org
Labels: Cr-Blink-WebGL Cr-Internals-GPU-VendorSpecific
Owner: zmo@chromium.org
zmo@: could you please see whether this is reproducible with an ASAN build on Linux?

marcheu@: could you please comment on whether this might affect Chrome OS? It looks like Mesa 9.0.3 is the affected version, as that's the version built into Chromium and used for testing purposes.

It seems to affect Chrome OS, yes (and git mesa for that matter).
We probably need something like the attached patch.
0001-mesa-Don-t-read-write-past-the-end-of-arrays.patch
1.4 KB Download
Comment 6 by kbr@chromium.org, Jan 15 2014
The test case looks like a stripped-down and modified variant of sdk/tests/conformance/glsl/misc/shader-varying-packing-restrictions.html from https://github.com/KhronosGroup/WebGL .

As far as I can tell, the shaders in this test case are supposed to fail to compile, and the failure is supposed to be caught by the ANGLE shader translator's packing restrictions -- the shader isn't even supposed to be passed to the driver.

zmo or bajones, could one of you please confirm the behavior of this test and the related one from the WebGL conformance suite?

marcheu: your Mesa patch looks reasonable but I don't know its internals.

Project Member Comment 7 by clusterf...@chromium.org, Jan 17 2014
Summary: Stack-use-after-return in _mesa_optimize_program (was: Stack-buffer-overflow in _mesa_optimize_program)
Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4827801278480384

Fuzzer: Amtinits_glsl_mutation
Job Type: Linux_asan_chrome_mp

Crash Type: Stack-use-after-return READ 4
Crash Address: 0x7f1c8825a36c
Crash State:
  - crash stack -
  _mesa_optimize_program
  _mesa_ir_link_shader
  _mesa_glsl_link_shader
  

Unminimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv974Lrcrre7DyDAQK8ESLFeYf2Z7qmA9HMrR6_3Y3kmGcr2JCOhKHabir81-2cDosHBtwlfxtj_n-L7sWWs1KzNf7S17697DPqvNqkB7jpDimW_rXdf_u7lQEAZsD4XloSboXsKb1EZYOSyRiuab6XAlLiLi1KJXCeP9jobPUKLF4T7_o7k


Project Member Comment 8 by clusterf...@chromium.org, Jan 22 2014
Labels: Nag
zmo@: Uh oh! This issue is still open and hasn't been updated in the last 7 days. Since this is a serious security vulnerability, we want to make sure progress is happening. Can you update the bug with current status, and what, if anything, is blocking?

If you are not the right Owner for this bug, please find someone else to own it as soon as possible and remove yourself as Owner.

If the issue is already fixed or you are to unable to reproduce it, please close the bug. (And thanks for fixing the bug!).

These nags can be disabled by adding a 'WIP' label and an optional codereview link.

- Your friendly ClusterFuzz
Comment 9 by zmo@chromium.org, Jan 22 2014
Status: Started
Comment 10 by zmo@chromium.org, Jan 24 2014
Here is the issue (why chromium didn't fail the link check):

We define 65 varying floats in vertex shader, but they didn't appear in fragment shader.  So in chromium, they are considered as NOT statically used, and therefore, they didn't contribute to the packing limit, therefore, chromium side linking check didn't fail.

So apparently there is a bug in mesa driver, that they didn't handle this situation consistently.

We have two options:
1) fix the mesa side bug
2) in ANGLE shader translator, we delete all the varyings that's not statically used.

Ideas?

Personally I prefer 1), because we can only detect varying usage at link time, so that means at link time, we have to do another round of shader translation, which will be bad.
Comment 11 by zmo@chromium.org, Jan 24 2014
or option 3): we tighten up the packing restrictions by counting in the varyings that are not statically used.  This will fail the linking at chromium side, not passing it down to underlying drivers.
Comment 12 by zmo@chromium.org, Jan 24 2014
Per discussion with kbr@ add marcheu@, here is what we will do.

1) in chromium, we land a driver bug workaround that only applies to mesa drivers, that when we apply the varying packing restrictions, we count in all varyings, even those not statically used ones.

2) then marcheu can land his CL to fix the mesa bug in optimizer.

3) at a future time, when marcheu's fix is all over the places, we can blacklist older mesa without this fix, and remove the chromium side driver bug workaround.
Comment 13 Deleted
Comment 14 Deleted
Did something happen in that fixed range that caused all these bugs to turn up fixed ? Just like http://code.google.com/p/chromium/issues/detail?id=326812 is also turning up all fixed ? Ideas ?
Comment 16 by zmo@chromium.org, Jan 30 2014
No, I haven't landed my CL yet.  I assume marcheu@ hasn't landed the mesa fix either, so no idea why it's fixed.
As I said in the other bug ( https://code.google.com/p/chromium/issues/detail?id=326812#c27 ) I don't think this is really fixed. There's probably another issue somewhere...
Mass spam: If this was a blink bug and you saw "fixed in range 247765:247811", this comment is probably wrong. We are working to see what caused ASAN to stop working due to a code change in this range.
Comment 20 by zmo@chromium.org, Feb 7 2014
Cc: jgilb...@mozilla.com
Comment 21 by zmo@chromium.org, Feb 7 2014
Jeff, this is the mesa driver bug I mentioned during this morning's meeting.
Project Member Comment 22 by bugdroid1@chromium.org, Feb 7 2014
Comment 23 by zmo@chromium.org, Feb 7 2014
Labels: -M-32 M-33 Merge-Requested
Looks like we need to merge this back as far as we can.  In order to merge this one, we also need to merge the other one first (https://codereview.chromium.org/147593011/).

I think M32 ship is gone.  Let's get it into M33.
Project Member Comment 24 by clusterf...@chromium.org, Feb 7 2014
Labels: ReleaseBlock-Stable
Comment 25 by laforge@google.com, Feb 10 2014
Labels: -Merge-Requested Merge-Approved
Project Member Comment 26 by bugdroid1@chromium.org, Feb 10 2014
Labels: -Merge-Approved merge-merged-1750
------------------------------------------------------------------------
r250146 | zmo@chromium.org | 2014-02-10T17:59:20.161025Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/gles2_cmd_decoder_unittest_base.cc?r1=250146&r2=250145&pathrev=250146
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/gles2_cmd_decoder_unittest_base.h?r1=250146&r2=250145&pathrev=250146
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/config/gpu_driver_bug_workaround_type.h?r1=250146&r2=250145&pathrev=250146
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/program_manager_unittest.cc?r1=250146&r2=250145&pathrev=250146
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/program_manager.cc?r1=250146&r2=250145&pathrev=250146
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/gles2_cmd_decoder_unittest.cc?r1=250146&r2=250145&pathrev=250146
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/gles2_cmd_decoder_unittest_1.cc?r1=250146&r2=250145&pathrev=250146
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/program_manager.h?r1=250146&r2=250145&pathrev=250146
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/gles2_cmd_decoder.cc?r1=250146&r2=250145&pathrev=250146
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/config/gpu_driver_bug_list_json.cc?r1=250146&r2=250145&pathrev=250146

Merge 249460 "Hookup clear_uniforms_before_first_program_use wor..."

> Hookup clear_uniforms_before_first_program_use workaround with implementation.
> 
> Right now it's hardwired in command buffer.
> 
> BUG= 340516 , 333885 
> TEST=gpu_unittests, webgl conformance tests
> R=bajones@chromium.org, kbr@chromium.org
> 
> Review URL: https://codereview.chromium.org/147593011

TBR=zmo@chromium.org

Review URL: https://codereview.chromium.org/148153025
------------------------------------------------------------------------
Comment 27 by zmo@chromium.org, Feb 10 2014
Status: Fixed
Project Member Comment 28 by bugdroid1@chromium.org, Feb 10 2014
------------------------------------------------------------------------
r250147 | zmo@chromium.org | 2014-02-10T18:01:15.885699Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/config/gpu_driver_bug_workaround_type.h?r1=250147&r2=250146&pathrev=250147
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/program_manager_unittest.cc?r1=250147&r2=250146&pathrev=250147
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/program_manager.cc?r1=250147&r2=250146&pathrev=250147
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/gles2_cmd_decoder_unittest_1.cc?r1=250147&r2=250146&pathrev=250147
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/program_manager.h?r1=250147&r2=250146&pathrev=250147
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/gles2_cmd_decoder.cc?r1=250147&r2=250146&pathrev=250147
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/config/gpu_driver_bug_list_json.cc?r1=250147&r2=250146&pathrev=250147

Merge 249547 "Add a gpu driver bug workaround to count in all va..."

> Add a gpu driver bug workaround to count in all varyings in packing check.
> 
> This is to workaround a Mesa driver bug.
> 
> BUG= 333885 
> TEST=gpu_unittests, test as mentioned in the bug report
> R=bajones@chromium.org, kbr@chromium.org
> 
> Review URL: https://codereview.chromium.org/153173002

TBR=zmo@chromium.org

Review URL: https://codereview.chromium.org/156783005
------------------------------------------------------------------------
Project Member Comment 29 by bugdroid1@chromium.org, Feb 10 2014
------------------------------------------------------------------------
r250175 | laforge@chromium.org | 2014-02-10T19:36:35.411591Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/config/gpu_driver_bug_workaround_type.h?r1=250175&r2=250174&pathrev=250175
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/program_manager_unittest.cc?r1=250175&r2=250174&pathrev=250175
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/program_manager.cc?r1=250175&r2=250174&pathrev=250175
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/gles2_cmd_decoder_unittest_1.cc?r1=250175&r2=250174&pathrev=250175
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/program_manager.h?r1=250175&r2=250174&pathrev=250175
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/gles2_cmd_decoder.cc?r1=250175&r2=250174&pathrev=250175
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/config/gpu_driver_bug_list_json.cc?r1=250175&r2=250174&pathrev=250175

Revert 250147 "Merge 249547 "Add a gpu driver bug workaround to ..."

> Merge 249547 "Add a gpu driver bug workaround to count in all va..."
> 
> > Add a gpu driver bug workaround to count in all varyings in packing check.
> > 
> > This is to workaround a Mesa driver bug.
> > 
> > BUG= 333885 
> > TEST=gpu_unittests, test as mentioned in the bug report
> > R=bajones@chromium.org, kbr@chromium.org
> > 
> > Review URL: https://codereview.chromium.org/153173002
> 
> TBR=zmo@chromium.org
> 
> Review URL: https://codereview.chromium.org/156783005

TBR=zmo@chromium.org

Review URL: https://codereview.chromium.org/159173003
------------------------------------------------------------------------
Project Member Comment 30 by bugdroid1@chromium.org, Feb 10 2014
------------------------------------------------------------------------
r250179 | laforge@chromium.org | 2014-02-10T19:40:01.883820Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/gles2_cmd_decoder_unittest.cc?r1=250179&r2=250178&pathrev=250179
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/gles2_cmd_decoder_unittest_1.cc?r1=250179&r2=250178&pathrev=250179
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/program_manager.h?r1=250179&r2=250178&pathrev=250179
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/gles2_cmd_decoder.cc?r1=250179&r2=250178&pathrev=250179
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/config/gpu_driver_bug_list_json.cc?r1=250179&r2=250178&pathrev=250179
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/gles2_cmd_decoder_unittest_base.cc?r1=250179&r2=250178&pathrev=250179
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/gles2_cmd_decoder_unittest_base.h?r1=250179&r2=250178&pathrev=250179
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/config/gpu_driver_bug_workaround_type.h?r1=250179&r2=250178&pathrev=250179
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/program_manager_unittest.cc?r1=250179&r2=250178&pathrev=250179
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/program_manager.cc?r1=250179&r2=250178&pathrev=250179

Revert 250146 "Merge 249460 "Hookup clear_uniforms_before_first_..."

> Merge 249460 "Hookup clear_uniforms_before_first_program_use wor..."
> 
> > Hookup clear_uniforms_before_first_program_use workaround with implementation.
> > 
> > Right now it's hardwired in command buffer.
> > 
> > BUG= 340516 , 333885 
> > TEST=gpu_unittests, webgl conformance tests
> > R=bajones@chromium.org, kbr@chromium.org
> > 
> > Review URL: https://codereview.chromium.org/147593011
> 
> TBR=zmo@chromium.org
> 
> Review URL: https://codereview.chromium.org/148153025

TBR=zmo@chromium.org

Review URL: https://codereview.chromium.org/159183002
------------------------------------------------------------------------
Project Member Comment 31 by clusterf...@chromium.org, Feb 10 2014
Labels: -Restrict-View-SecurityTeam Restrict-View-SecurityNotify
Comment 32 by kbr@chromium.org, Feb 10 2014
Status: Started
What happened with the merge? Did it break the build?

Project Member Comment 33 by bugdroid1@chromium.org, Feb 10 2014
------------------------------------------------------------------------
r250202 | zmo@chromium.org | 2014-02-10T20:58:32.385485Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/config/gpu_driver_bug_list_json.cc?r1=250202&r2=250201&pathrev=250202
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/gles2_cmd_decoder_unittest_base.cc?r1=250202&r2=250201&pathrev=250202
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/gles2_cmd_decoder_unittest_base.h?r1=250202&r2=250201&pathrev=250202
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/config/gpu_driver_bug_workaround_type.h?r1=250202&r2=250201&pathrev=250202
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/program_manager_unittest.cc?r1=250202&r2=250201&pathrev=250202
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/program_manager.cc?r1=250202&r2=250201&pathrev=250202
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/gles2_cmd_decoder_unittest.cc?r1=250202&r2=250201&pathrev=250202
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/gles2_cmd_decoder_unittest_1.cc?r1=250202&r2=250201&pathrev=250202
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/program_manager.h?r1=250202&r2=250201&pathrev=250202
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/gles2_cmd_decoder.cc?r1=250202&r2=250201&pathrev=250202

Manually merge r249460 into M33: Hookup clear_uniforms_before_first_program_use workaround with implementation.

Original CL: https://codereview.chromium.org/147593011

BUG= 340516 , 333885 
TEST=gpu_unittests, webgl conformance tests
TBR=zmo@chromium.org,bajones@chromium.org, kbr@chromium.org

Review URL: https://codereview.chromium.org/159243002
------------------------------------------------------------------------
Project Member Comment 34 by bugdroid1@chromium.org, Feb 10 2014
------------------------------------------------------------------------
r250203 | zmo@chromium.org | 2014-02-10T21:05:06.256656Z

Changed paths:
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/config/gpu_driver_bug_workaround_type.h?r1=250203&r2=250202&pathrev=250203
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/program_manager_unittest.cc?r1=250203&r2=250202&pathrev=250203
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/program_manager.cc?r1=250203&r2=250202&pathrev=250203
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/gles2_cmd_decoder_unittest_1.cc?r1=250203&r2=250202&pathrev=250203
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/program_manager.h?r1=250203&r2=250202&pathrev=250203
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/command_buffer/service/gles2_cmd_decoder.cc?r1=250203&r2=250202&pathrev=250203
   M http://src.chromium.org/viewvc/chrome/branches/1750/src/gpu/config/gpu_driver_bug_list_json.cc?r1=250203&r2=250202&pathrev=250203

Merge r249547 into M33: Add a gpu driver bug workaround to count in all varyings in packing check.

Original CL: https://codereview.chromium.org/153173002

This is to workaround a Mesa driver bug.

BUG= 333885 
TEST=gpu_unittests, test as mentioned in the bug report
TBR=zmo@chromium.org,bajones@chromium.org, kbr@chromium.org

Review URL: https://codereview.chromium.org/146243006
------------------------------------------------------------------------
Comment 35 by zmo@chromium.org, Feb 13 2014
Status: Fixed
Comment 36 by dharani@google.com, Feb 19 2014
Labels: Release-0-M33
Cc: ddkil...@apple.com
Project Member Comment 38 by clusterf...@chromium.org, Mar 5 2014
ClusterFuzz has detected this issue as fixed in range 245341:245384.

Detailed report: https://cluster-fuzz.appspot.com/testcase?key=4827801278480384

Fuzzer: Amtinits_glsl_mutation
Job Type: Linux_asan_chrome_mp

Crash Type: Stack-buffer-overflow READ 4
Crash Address: 0x7f53282d535c
Crash State:
  - crash stack -
  _mesa_optimize_program
  _mesa_ir_link_shader
  _mesa_glsl_link_shader
  
Regressed: https://cluster-fuzz.appspot.com/revisions?range=226545:226626
Fixed: https://cluster-fuzz.appspot.com/revisions?range=245341:245384

Minimized Testcase: https://cluster-fuzz.appspot.com/download/AMIfv94H1e_cNgvsOwKDMVzjnyqPp3n3R1S2A-h_hW3v1yVczIrsY3NB_xo8LmaO3HvYS6hpO-4CFeuH-aSX-T-xXR-Qy10TQuVsnvmaij26Meo_MOjeHSxuJiKQAUFMByUkyrulLYYnd_0E5Czt9hFzu4swfS6Zn0S0K7CHGetyBOrumAOle6U

If you suspect that the result above is incorrect, try re-doing that job on the testcase report page.

Comment 39 by kbr@chromium.org, Apr 9 2014
Cc: jda...@gmail.com
Project Member Comment 40 by clusterf...@chromium.org, May 21 2014
Labels: -Restrict-View-SecurityNotify
Bulk update: removing view restriction from closed bugs.
Project Member Comment 41 by clusterf...@chromium.org, Feb 2 2016
Labels: -Security_Impact-Beta
Comment 42 by tri...@gmail.com, Jun 23 2016
Labels: -merge-merged-1750 -M-33 Merge-merged-1750 m-33
If this is fixed, why does it show up under Problems Detected on ChromeOS dev which is using Mesa 12.1 ~ m53 ?
Comment 43 by tri...@gmail.com, Jun 23 2016
Sorry, above comment meant to add "on the chrome://gpu page"
Project Member Comment 44 by sheriffbot@chromium.org, Oct 1
This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member Comment 45 by sheriffbot@chromium.org, Oct 2
This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: allpublic
Sign in to add a comment