[Bug 45642] Chrome/ Chromium sandbox needs x86-64 syscall thunks to match Windows

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=45642

--- Comment #18 from Zebediah Figura <z.figura12 at gmail.com> ---
(In reply to Fabian Maurer from comment #17)
> Created attachment 64559 [details]
> Workaround for user shared data issue
> 
> Ah, I misunderstood. I though memory permissions could be set more granular,
> but if it always affects whole pages this would be too expensive...
> 
> How about moving the SystemCallPad flag somewhere else? I attached a PoC,
> this also makes chrome happy. We just need to set some fixed address to the
> value 1 and refer to it in the syscall thunks. Would this be feasable?

That's feasible, yes.

Still, is there any reason we can't just lobby Chromium to fix their software?

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.