[Bug 50281] fsync patch for wine 6.0-rc1 (without staging)

[WineHQ Bugzilla]

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

--- Comment #10 from Zebediah Figura <z.figura12 at gmail.com> ---
(In reply to Shmerl from comment #9)
> (In reply to Zebediah Figura from comment #8)
> > 
> > I am doubtful that it will be accepted into wine-staging either.
> > 
> 
> Can you please explain why it can't be accepted in either staging or regular
> Wine or point out to some thread that already explains that to avoid
> repeating it? It's kind of disheartening for users of Wine who don't use
> Proton since it will require applying these patches manually if won't be
> part of staging either.

Neither esync nor fsync will be accepted into upstream wine for the following
reasons:

* they rely on use of shared memory to retain object state, which is not robust
against misbehaving processes (and hence is not secure either);

* they do not offer full compatibility with the windows API and in practice
break many applications.

And no, neither one of these can be fixed within the current design, or I would
have done so already.

fsync is unlikely to be accepted into wine-staging because it represents a
significant additional maintenance burden for practically no benefit. In
particular the number of applications that it is known to help can be counted
on one hand. Furthermore esync is already a very significant maintenance
burden; it has been easily the worst patch set in wine-staging since its
induction.

-- 
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.