Assert that we do not have any Object subclasses flowing through generic GCMethods

RESOLVED FIXED in Firefox 40

Status

()

defect
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: terrence, Assigned: terrence)

Tracking

(Blocks 1 bug)

Trunk
mozilla40
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox40 fixed)

Details

Attachments

(1 attachment)

I should have done this when I added the JSFunction overload, but didn't want to make the bug that obvious in the checkin. We should be good now though, so let's get that assertion in place.

Filing as sec-sensitive until the try results are back, just incase.
Comment on attachment 8600381 [details] [diff] [review]
forward_security_on_object_exposure-v0.diff

Try run seems to be green.
Attachment #8600381 - Flags: review?(jcoppeard)
Comment on attachment 8600381 [details] [diff] [review]
forward_security_on_object_exposure-v0.diff

Review of attachment 8600381 [details] [diff] [review]:
-----------------------------------------------------------------

Nice.
Attachment #8600381 - Flags: review?(jcoppeard) → review+
Try is green -- as I thought, there are no Object subclasses other than Function we need to handle explicitly in barriers.
Group: core-security
https://hg.mozilla.org/mozilla-central/rev/10c0adba47eb
Status: ASSIGNED → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla40
You need to log in before you can comment on or make changes to this bug.