[Webkit-unassigned] [Bug 169890] New: WebAssembly: can mprotect ever fail?
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Mar 20 13:59:34 PDT 2017
https://bugs.webkit.org/show_bug.cgi?id=169890
Bug ID: 169890
Summary: WebAssembly: can mprotect ever fail?
Classification: Unclassified
Product: WebKit
Version: WebKit Nightly Build
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: JavaScriptCore
Assignee: webkit-unassigned at lists.webkit.org
Reporter: jfbastien at apple.com
CC: fpizlo at apple.com, jfbastien at apple.com,
keith_miller at apple.com, mark.lam at apple.com,
msaboff at apple.com, sbarati at apple.com
Blocks: 159775
WasmMemory uses mprotect and tries to handle its failure. I'm not sure it should ever fail according to the manpage for MacOS. Linux seems to allow failure if the kernel runs out of memory for its internal data structures, which seems *really* bad.
In both cases I suspect we should just assert out.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20170320/2ab16770/attachment.html>
More information about the webkit-unassigned
mailing list