Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CacheStorage: Set opaque mode for code cache. #21074

Merged
merged 1 commit into from Jan 8, 2020

Conversation

chromium-wpt-export-bot
Copy link
Collaborator

@chromium-wpt-export-bot chromium-wpt-export-bot commented Jan 7, 2020

This CL restores code to set the V8 code cache generation opaque mode
based on the response tainting. It was previously incorrectly removed
in crrev.com/c/1828726.

This CL adds a test that verifies scripts loaded from cache_storage are
treated as opaque when appropriate. It has been verified to fail
without the fixed code.

The CL also fixes an incorrect DCHECK that the test triggers. The
assumption in the DCHECK was incorrect and should instead be a runtime
check.

Bug: 1037701
Change-Id: I894b30ad9dac6c3a47e1b5f325ee7906768b57f3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1988675
Commit-Queue: Ben Kelly <wanderview@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#729327}

Copy link
Collaborator

@wpt-pr-bot wpt-pr-bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The review process for this patch is being conducted in the Chromium project.

@chromium-wpt-export-bot chromium-wpt-export-bot force-pushed the chromium-export-cl-1988675 branch 4 times, most recently from 9f0bc43 to 1559c91 Compare January 8, 2020 03:26
This CL restores code to set the V8 code cache generation opaque mode
based on the response tainting.  It was previously incorrectly removed
in crrev.com/c/1828726.

This CL adds a test that verifies scripts loaded from cache_storage are
treated as opaque when appropriate.  It has been verified to fail
without the fixed code.

The CL also fixes an incorrect DCHECK that the test triggers.  The
assumption in the DCHECK was incorrect and should instead be a runtime
check.

Bug: 1037701
Change-Id: I894b30ad9dac6c3a47e1b5f325ee7906768b57f3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1988675
Commit-Queue: Ben Kelly <wanderview@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#729327}
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants