Closed
Bug 2049308
Opened 4 months ago
Closed 3 months ago
Harden bailout and recover instruction code
Categories
(Core :: JavaScript Engine: JIT, task, P1)
Core
JavaScript Engine: JIT
Tracking
()
RESOLVED
FIXED
154 Branch
People
(Reporter: jandem, Assigned: jandem)
References
(Blocks 1 open bug)
Details
(Keywords: sec-audit, Whiteboard: [adv-main153-])
Attachments
(2 files)
|
48 bytes,
text/x-phabricator-request
|
Details | Review | |
|
48 bytes,
text/x-phabricator-request
|
phab-bot
:
approval-mozilla-beta+
|
Details | Review |
Bug 2044606 is an example of a bailout/recover-instruction bug where release assertions would have helped. Bailout and recover instruction code is cold - this means it's hard to test well but it also means we could upgrade many assertions to release assertions without affecting performance.
| Assignee | ||
Updated•4 months ago
|
Flags: needinfo?(jdemooij)
| Assignee | ||
Comment 1•3 months ago
|
||
Updated•3 months ago
|
Assignee: nobody → jdemooij
Status: NEW → ASSIGNED
| Assignee | ||
Updated•3 months ago
|
Flags: needinfo?(jdemooij)
Pushed by jdemooij@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/e3b6ef594890
https://hg.mozilla.org/integration/autoland/rev/133fc73680c4
Add some release assertions to the bailout code. r=mgaudet
Pushed by abutkovits@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/318501fda5ec
https://hg.mozilla.org/integration/autoland/rev/84f4e7d72dce
Revert "Bug 2049308 - Add some release assertions to the bailout code. r=mgaudet" for causing bustages in InstrProfilingValue.c.
| Assignee | ||
Comment 4•3 months ago
|
||
Interesting, that looks like an LLVM PGO bug... I'll see if I can figure out which part is responsible.
Updated•3 months ago
|
| Assignee | ||
Updated•3 months ago
|
Flags: needinfo?(jdemooij)
Pushed by jdemooij@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/00f95d292337
https://hg.mozilla.org/integration/autoland/rev/3f82ed2b8963
Add some release assertions to the bailout code. r=mgaudet
Comment 6•3 months ago
|
||
Group: javascript-core-security → core-security-release
Status: ASSIGNED → RESOLVED
Closed: 3 months ago
status-firefox154:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 154 Branch
| Assignee | ||
Updated•3 months ago
|
Flags: needinfo?(jdemooij)
Updated•3 months ago
|
status-firefox152:
--- → wontfix
status-firefox153:
--- → wontfix
status-firefox-esr115:
--- → wontfix
status-firefox-esr140:
--- → wontfix
tracking-firefox154:
--- → +
Comment 7•3 months ago
|
||
Is this worth uplifting to Beta for the benefit of ESR153?
status-firefox-esr153:
--- → affected
Flags: needinfo?(jdemooij)
| Assignee | ||
Comment 8•3 months ago
|
||
Original Revision: https://phabricator.services.mozilla.com/D309004
Updated•3 months ago
|
Attachment #9607043 -
Flags: approval-mozilla-beta?
Comment 9•3 months ago
|
||
firefox-beta Uplift Approval Request
- User impact if declined/Reason for urgency: This patch adds some release assertions to help prevent security bugs. Would be nice to have on ESR153.
- Code covered by automated testing?: yes
- Fix verified in Nightly?: yes
- Needs manual QE testing?: no
- Steps to reproduce for manual QE testing:
- Risk associated with taking this patch: low
- Explanation of risk level: Has been on Nightly for a while. Changes some assertions to release assertions.
- String changes made/needed?: N/A
- Is Android affected?: yes
| Assignee | ||
Comment 10•3 months ago
|
||
(In reply to Ryan VanderMeulen [:RyanVM] from comment #7)
Is this worth uplifting to Beta for the benefit of ESR153?
Yes; I've requested uplift.
Flags: needinfo?(jdemooij)
Updated•3 months ago
|
Attachment #9607043 -
Flags: approval-mozilla-beta? → approval-mozilla-beta+
Updated•3 months ago
|
Updated•3 months ago
|
QA Whiteboard: [sec] [uplift] [qa-triage-done-c154/b153]
Comment 11•3 months ago
|
||
| uplift | ||
Updated•3 months ago
|
Whiteboard: [adv-main153-]
Updated•2 months ago
|
status-firefox-esr153:
affected → ---
tracking-firefox153:
--- → +
Updated•1 month ago
|
Group: core-security-release
You need to log in
before you can comment on or make changes to this bug.
Description
•