April 2017 - Wine-Devel - list.winehq.org

Re: [v6 PATCH 00/21] x86: Enable User-Mode Instruction Prevention

by Stas Sergeev

30.03.2017 08:14, Ricardo Neri пишет: >>>>>> You know the wine's >>>>>> requirements now - they are very small. And >>>>>> dosemu doesn't need anything at all but smsw. >>>>>> And even smsw is very rare. >>>>> But emulation is still needed for SMSW, right? >>>> Likely so. >>>> If you want, I can enable the logging of this command >>>> and see if it is used by some of the DOS programs I have. >>> It would be great if you could do that, if you don't mind. >> OK, scheduled to the week-end. >> I'll let you know. > Thanks! OK, done the testing. It appears smsw is used in v86 by windows-3.1 and dos4gw at the very least, and these are the "major" apps. So doing without a fixup in v86 will not go unnoticed. Unfortunately this also means that KVM-vm86 should be properly tested. I have also found a weird program that does SGDT under v86. This causes "ERROR: SGDT not implemented" under dosemu, but the prog still works fine as it obviously does not care about the results. This app can easily be broken of course, if that makes any sense (likely not).

April 1, 2017

Re: [PATCH] usp10: Handle invalid arguments in ScriptIsComplex()

by Marvin

Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=29873 Your paranoid android. === wxppro (32 bit usp10) === usp10.c:3938: Test failed: got 0x00000001 09e8:usp10: unhandled exception c0000005 at 74DA37CD === w2003std (32 bit usp10) === usp10.c:3938: Test failed: got 0x00000001 05f0:usp10: unhandled exception c0000005 at 754A73F9 === wvistau64 (32 bit usp10) === usp10.c:3938: Test failed: got 0x00000001 00c4:usp10: unhandled exception c0000005 at 76089892 === w2008s64 (32 bit usp10) === usp10.c:3938: Test failed: got 0x00000001 0b54:usp10: unhandled exception c0000005 at 76729892 === wvistau64 (64 bit usp10) === usp10.c:3938: Test failed: got 0x00000001 00c4:usp10: unhandled exception c0000005 at 000007FEFEE0119A === w2008s64 (64 bit usp10) === usp10.c:3938: Test failed: got 0x00000001 07ec:usp10: unhandled exception c0000005 at 000007FEFD9F119A

April 1, 2017

Re: [v6 PATCH 00/21] x86: Enable User-Mode Instruction Prevention

by Andy Lutomirski

On Fri, Mar 31, 2017 at 2:26 PM, Stas Sergeev <stsp(a)list.ru> wrote: > 31.03.2017 17:11, Alexandre Julliard пишет: >> >> In fact it would be nice to be able to make sidt/sgdt/etc. segfault >> too. I know a new syscall is a pain, > > Maybe arch_prctl() then? I still like my idea of a generic mechanism to turn off backwards-compatibility things. After all, hardened programs should turn off UMIP fixups entirely. They should also turn off vsyscall emulation entirely, and I see no reason that these mechanisms should be different. --Andy

April 1, 2017