[Bug 46472] Linux kernel 4.19 breaks startup of BO2 due to change in PTRACE_POKEUSER hw breakpoint behavior

[wine-bugs at winehq.org]

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

--- Comment #27 from tjb <troyb at us.ibm.com> ---
(In reply to Alexandre Julliard from comment #22)
> (In reply to tjb from comment #21)
> > (In reply to Anthony Jagers from comment #20)
> > > I tried to file a bug report with the kernel mailing list. Either it got
> > > rejected or buried.  Anyone else want to try?
> > 
> > The kernel guys will need a specific example of why the patch is broken. 
> > The fact that wine used to work on some programs and doesn't work any more
> > with new PTRACE_POKEUSER behavior is not going to matter to them unless it
> > can be shown the change (claimed as a fix) is actually incorrect.  Thus it
> > most likely falls to a core wine dev to smoke this out, someone who actually
> > implemented the low level PTRACE code and would know that the new interface
> > behavior is incorrect, or that the new interface behavior is actually the
> > correct approach and wine needs to be updated to accommodate it.
> 
> Did you actually talk to the kernel guys, or are you just guessing?
> They usually take backwards compatibility seriously.

I stated this because there is some (probably small) chance that the affected
programs (BO2 and others Anthony found) should be crashing due to issues
unrelated to this change, and the kernel change now "correctly" traps the
error.  If this can be shown definatively false (i.e. the change breaks
something in userspace which used to work), then there is a better argument for
preserving the backward compatible behavior unless an argument can be made that
the change is actually needed for some other very solid reason.

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