Closed Bug 564937 Opened 15 years ago Closed 15 years ago

fast iterators shouldn't touch regs.sp[0]

Categories

(Core :: JavaScript Engine, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
blocking2.0 --- beta1+

People

(Reporter: luke, Assigned: luke)

References

Details

(Whiteboard: [sg:critical?] fixed-in-tracemonkey [critsmash:patch])

Attachments

(1 file)

Attached patch fixSplinter Review
Stack code shouldn't read/write regs.sp[0] (or anything higher). With bug 540706, these slots may be used by a more-recently-pushed js::CallStack, JSStackFrame, or arg slots. In particular, using regs.sp[0] as the rval of a js_InternalInvoke is bad. The fact that regs.sp[0] is not rooted (and IteratorMore assumes it is) suggests that this is a bug even without the contiguous stack patch.
Attachment #444507 - Flags: review?(gal)
Comment on attachment 444507 [details] [diff] [review] fix Tryserver carefully, lots of interpreter and tracer dependencies here, but looks good.
Attachment #444507 - Flags: review?(gal) → review+
Marking sensitive out of an excess of caution; treating unrooted locations as rooted is GC-hazardous.
Group: core-security
Whiteboard: [sg:critical?]
Comment on attachment 444507 [details] [diff] [review] fix Sorry I missed this, should have caught it. /be
So I did find this: cx->regs->sp -= fused ? (*orig.pc == JSOP_MOREITER ? 0 : 2) : 1; in TraceRecorder::checkTraceEnd. Does that have any interaction with the change: - TRY_BRANCH_AFTER_COND(cond, 0); + TRY_BRANCH_AFTER_COND(cond, 1); in my patch?
blocking2.0: --- → ?
blocking2.0: ? → beta1+
Andreas and I looked over the above code and the patch seems fine as is, since the checkTraceEnd call happens before JSOP_MOREITER. But also CC'ing Gary, perchance to fuzz.
(In reply to comment #5) > Andreas and I looked over the above code and the patch seems fine as is, since > the checkTraceEnd call happens before JSOP_MOREITER. > > But also CC'ing Gary, perchance to fuzz. Patch looks good on 32-bit shells after 12 hours of dedicated fuzz.
Whiteboard: [sg:critical?] → [sg:critical?] fixed-in-tracemonkey
Whiteboard: [sg:critical?] fixed-in-tracemonkey → [sg:critical?] fixed-in-tracemonkey [critsmash:patch]
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Luke, did this affect 1.9.2? I assume not as bug 540706 did not affect 1.9.2 if I read correctly. Is there any reason to keep this locked?
Nope.
Group: core-security
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: