Closed
Bug 1878958
Opened 1 year ago
Closed 1 year ago
IPC should expose method to determine if message type is sync
Categories
(Core :: IPC, enhancement)
Core
IPC
Tracking
()
RESOLVED
FIXED
125 Branch
People
(Reporter: decoder, Assigned: decoder)
Details
(Keywords: sec-want, Whiteboard: [adv-main125-])
Attachments
(1 file)
Currently, we have no way to know if a particular IPC message type is supposed to be sync or not. The IPCFuzzController therefore currently does not create sync messages at all because guessing the sync flag would lead to a high amount of discarded messages.
This can be solved by exposing the sync status through a function similar to the IPC::StringFromIPCMessageType function generated by IPDL.
| Assignee | ||
Comment 1•1 year ago
|
||
Pushed by choller@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/3d865fe1a532
Add IPCMessageTypeIsSync and use it in IPCFuzzController. r=nika
Comment 3•1 year ago
|
||
Backed out for causing lint failures:
https://hg.mozilla.org/integration/autoland/rev/bef8b1b461b8524917fc01cd866e903290b1d7f6
Flags: needinfo?(choller)
Updated•1 year ago
|
Attachment #9378639 -
Attachment description: Bug 1878958 - Add IPCMessageTypeIsSync and use it in IPCFuzzController. r?nika,truber → Bug 1878958 - Add IPCMessageTypeIsSync and use it in IPCFuzzController. r?nika
Pushed by choller@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/3c8dcaf3eb8c
Add IPCMessageTypeIsSync and use it in IPCFuzzController. r=nika
Comment 5•1 year ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox123:
--- → wontfix
status-firefox125:
--- → fixed
status-firefox-esr115:
--- → wontfix
Flags: needinfo?(choller)
Resolution: --- → FIXED
Target Milestone: --- → 125 Branch
Updated•1 year ago
|
QA Whiteboard: [post-critsmash-triage]
Flags: qe-verify-
Updated•1 year ago
|
Whiteboard: [adv-main125-]
Updated•1 year ago
|
Group: core-security-release
You need to log in
before you can comment on or make changes to this bug.
Description
•