On Tue, Oct 01, 2024 at 04:34:00AM GMT, Bert Karwatzki wrote: > I just noticed (via a bisect between v6.11 and v6.12-rc1) that this patch > (commit f8d112a4e657 in linux-next tree) leads to a severe memory corruption > error under these (rather rare) circumstances: > 1. Start a 32bit windows game via steam (which uses proton, steam's version of wine) > 2. When starting the game you the proton version used has to be updated > > The effect is the following: The updating process of proton hangs and the game does > not start and even after an exit from steam two processes remain, one of them at > 100% CPU: > $ ps aux | grep rundll > bert 222638 1.7 0.1 2054868 87492 ? Ss 23:14 0:01 C:\windows\syswow64\rundll32.exe setupapi,InstallHinfSection Wow64Install 128 \\?\Z:\mnt\data\.steam\debian-installation\steamapps\common\Proton - Experimental\files\share\wine\wine.inf > bert 222639 99.8 0.0 2054868 2380 ? R 23:14 1:01 C:\windows\syswow64\rundll32.exe setupapi,InstallHinfSection Wow64Install 128 \\?\Z:\mnt\data\.steam\debian-installation\steamapps\common\Proton - Experimental\files\share\wine\wine.inf [snip] Replying to head of thread so we don't get too lost in the mail thread. Could you try this patch on latest next or mm-unstable and see if it fixes the issue? The theory is that perhaps an error is arising and being masked by this incorrect error handling. Regardless I'll upstream this fix, but be good if it also resolved the bug you've found! Thanks, Lorenzo ----8<----
