- wine-gitlab - winehq.org

[PATCH 0/2] MR9105: Revert "server: Return the NT file name in ObjectNameInformation for file objects."
by Alfred Agrell (＠Alcaro) 05 Oct '25

05 Oct '25

This reverts commit af35741d3681f21222a85900b54d95ee422fe074. As reported on IRC by user supermario1313, and bisected by Rounin, this commit made Wine no longer follow symlinks in Z:, which the former needs for a Wine-aware sandboxing solution. I'm not a huge fan of the test, but I like leaving things untested even less. The Correct™ solution would be CreateSymbolicLink() or FSCTL_SET_REPARSE_POINT, but they're not implemented in Wine. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9105

2 2

Re: [PATCH v4 0/4] MR8991: iphlpapi: Implement GetBestRoute2() and GetBestInterfaceEx().
by Paul Gofman (＠gofman) 04 Oct '25

04 Oct '25

On Sat Oct 4 09:17:56 2025 +0000, Bernhard Übelacker wrote: > Hello @gofman, I fear asan gets triggered by this assignment. > [This is the full output with a backtrace running the iphlpapi:iphlpapi test](https://gitlab.winehq.org/bernhardu/wine/-/blob/asan-pe_2025-09-13_wi… > If I understand it right, the size of `dst_addr` is 28 bytes, that much > it tries to read from the `dst` pointer. > Unfortunately this `dst` is reserved on the stack in `GetBestInterface` > as `struct sockaddr_in sa_in;` which is just 16 bytes. Thanks! I think it is already being addressed in https://gitlab.winehq.org/wine/wine/-/merge_requests/9085 -- https://gitlab.winehq.org/wine/wine/-/merge_requests/8991#note_117618

1 0

[PATCH 0/6] MR9102: ddraw: Fixes for device enumeration.
by Elizabeth Figura (＠zfigura) 04 Oct '25

04 Oct '25

-- https://gitlab.winehq.org/wine/wine/-/merge_requests/9102

2 6

[PATCH v6 0/1] MR7339: ntdll: implement create_logical_proc_info on FreeBSD.
by Damjan Jovanovic (＠dj) 04 Oct '25

04 Oct '25

Add Expat as a dependency, and use it to parse the XML returned from FreeBSD's kern.sched.topology_spec sysctl. -- v6: ntdll: implement create_logical_proc_info on FreeBSD. https://gitlab.winehq.org/wine/wine/-/merge_requests/7339

5 6

[PATCH 0/1] MR9101: netapi32: Add stubs for NetValidatePasswordPolicy and NetValidatePasswordPolicyFree
by Ugur Sari (＠ugursss) 04 Oct '25

04 Oct '25

Implement NetValidatePasswordPolicy and NetValidatePasswordPolicyFree as stubs returning NERR_Success. This prevents crashes in some apps that probe password policy support. Fyi, this fixes a crash on Solidworks installer. Actual implementation requires LSASS and SAM and this stub is possibly the only feasible fix for years to come. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9101

2 1

Re: [PATCH v2 0/1] MR9095: netapi32: Add stubs for NetValidatePasswordPolicy and NetValidatePasswordPolicyFree - closed
by Ugur Sari (＠ugursss) 04 Oct '25

04 Oct '25

This merge request was closed by Ugur Sari. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9095

1 0

[PATCH v6 0/29] MR7226: ntdll: Implement in-process synchronization via the Linux "ntsync" driver.
by Elizabeth Figura (＠zfigura) 04 Oct '25

04 Oct '25

This introduces a faster implementation of signal and wait operations on NT events, semaphores, and mutexes, which improves performance to native levels for a wide variety of games and other applications. The goal here is similar to the long-standing out-of-tree "esync" and "fsync" patch sets, but without the flaws that make those patch sets not upstreamable. The Linux "ntsync" driver is not currently released. It has been accepted into the trunk Linux tree for 6.14, so barring any extraordinary circumstances, the API is frozen and it will be released in its current form in about 2 months. Since it has passed all relevant reviewers on the kernel side, and the API is all but released, it seems there is no reason any more not to submit the Wine side to match. Some important notes: * This patch set does *not* include any way to disable ntsync support, since that kind of configuration often seems to be dispreferred where not necessary. In essence, ntsync should just work everywhere. Probably the easiest way to effectively disable ntsync, for the purposes of testing, is to chmod the /dev/ntsync device to prevent its being opened. Regardless, a Wine switch to disable ntsync can be added simply enough. Note that it should probably not take the form of a registry key, however, since it needs to be easily accessible from the server itself. * It is, generally speaking, not possible for only some objects, or some processes, to have backing ntsync objects, while others use the old server path. The esync/fsync patch sets explicitly protected against this by making sure every process had a consistent view of whether esync was enabled. This is not provided here, since no switch is provided to toggle ntsync, and it should not be possible to get into such an inconsistent state without gross misconfiguration. * Similarly, no diagnostic messages are provided to note that ntsync is in use, or not in use. These messages are part of esync/fsync, as well as part of ntsync "testing" trees unofficially distributed. However, if ntsync is working correctly, no message should be necessary. The basic structure is: * Each type of server object which can be waited on by the client (including events, semaphores, mutexes, but also other types such as processes, files) must store an "inproc_sync" object. This "inproc_sync" object is a full server object (note that this differs from esync/fsync). A vector and server request is introduced to retrieve an NT handle to this object from an arbitrary NT handle. Since the actual ntsync objects are simply distinct file descriptions, we then call get_handle_fd from the client to retrieve an fd to the object, and then perform ioctls on it. * Objects signaled by the server (processes, files, etc) perform ntsync ioctls on that object. The backing object in all such cases is simply an event. * Signal and wait operations on the client side attempt to defer to an "inproc_\*" function, falling back to the server implementation if it returns STATUS_NOT_IMPLEMENTED. This mirrors how in-process synchronization objects (critical sections, SRW locks, etc) used to be implemented—attempting to use an architecture-specific "fast_\*" function and falling back if it returned STATUS_NOT_IMPLEMENTED. * The inproc_sync handles, once retrieved, are cached per-process. This caching takes a similar form to the fd cache. It does not reuse the same infrastructure, however. The primary reason for this is that the fd cache is designed to fit within a 64-bit value and uses 64-bit atomic operations to ensure consistency. However, we need to store more than 64 bits of information. [We also need to modify them after caching, in order to correctly implement handle closing—see below.] The secondary reason is that retrieving the ntsync fd from the inproc_sync handle itself uses the fd cache. * In order to keep the Linux driver simple, it does not implement access flags (EVENT_MODIFY_STATE etc.) Instead, the flags are cached locally and validated there. This too mirrors the fd cache. Note that this means that a malicious process can now modify objects it should not be able modify—which is less true than it is with wineserver—but this is no different from the way other objects (notably fds) are handled, and would require manual syscalls. * In order to achieve correct behaviour related to closing objects while they are used, this patch set essentially relies on refcounting. This is broadly true of the server as well, but because we need to avoid server calls when performing object operations, significantly more care must be taken. In particular, because waits need to be interruptable by signals and then be restarted, we need the backing ntsync object to remain valid until all users are done with it. On a process level, this is achieved by letting multiple processes own handles to the underlying inproc_sync server object. On a thread level, multiple simultaneous calls need to refcount the process's local handle. This refcount is stored in the sync object cache. When it reaches zero, the cache is cleared. Punting this behaviour to the Linux driver would have introduced a great deal more complexity, which is best kept in userspace and out of the kernel. * The cache is, as such, treated as a cache. The penultimate commit, which introduces client support but does not yet cache the objects, effectively illustrates this by never actually caching anything, and retrieving a new NT handle and fd every time. * Certain waits, on internal handles (such as async, startup_info, completion), are delegated to the server even when ntsync is used. Those server objects do not create an underlying ntsync object. -- v6: ntdll: Cache in-process synchronization objects. ntdll: Use server_wait_for_object() when waiting on only the queue object. ntdll: Use in-process synchronization objects. ntdll: Introduce a helper to wait on an internal server handle. server: Allow creating an event object for client-side user APC signaling. server: Introduce select_inproc_queue and unselect_inproc_queue requests. server: Add a request to retrieve the in-process synchronization object from a handle. server: Create in-process synchronization objects for fd-based objects. server: Create in-process synchronization objects for timers. server: Create in-process synchronization objects for threads. server: Create in-process synchronization objects for message queues. server: Create in-process synchronization objects for jobs. server: Create in-process synchronization objects for processes. server: Create in-process synchronization objects for keyed events. server: Create in-process synchronization objects for device managers. server: Create in-process synchronization objects for debug objects. server: Create in-process synchronization objects for console outputs. server: Create in-process synchronization objects for console inputs. server: Create in-process synchronization objects for screen buffers. server: Create in-process synchronization objects for console servers. server: Create in-process synchronization objects for consoles. server: Create in-process synchronization objects for completion ports. server: Create in-process synchronization objects for mutexes. server: Create in-process synchronization objects for semaphores. server: Create in-process synchronization objects for events. server: Add an object operation to retrieve an in-process synchronization object. ntdll: Retrieve and cache an ntsync device in wait calls. This merge request has too many patches to be relayed via email. Please visit the URL below to see the contents of the merge request. https://gitlab.winehq.org/wine/wine/-/merge_requests/7226

8 13

Re: [PATCH v4 0/4] MR8991: iphlpapi: Implement GetBestRoute2() and GetBestInterfaceEx().
by Bernhard Übelacker (＠bernhardu) 04 Oct '25

04 Oct '25

Bernhard Übelacker (@bernhardu) commented about dlls/iphlpapi/iphlpapi_main.c: > } > } > > + uni_row = NULL; > + if (!src && !(v6 && IN6_IS_ADDR_LINKLOCAL(&dst->Ipv6.sin6_addr))) > + { > + static const struct in6_addr ipv6_default_addr = {{{ 0x20, 0x01, 0x0d, 0xb8 }}}; > + SOCKADDR_INET src_addr, dst_addr; > + WORD ver = MAKEWORD (2, 2); > + WSADATA data; > + SOCKET s; > + int len; > + > + WSAStartup ( ver, &data ); > + if ((s = socket( dst->si_family, SOCK_DGRAM, IPPROTO_UDP )) == -1) goto skip_system_route; > + dst_addr = *dst; Hello @gofman, I fear asan gets triggered by this assignment. [This is the full output with a backtrace running the iphlpapi:iphlpapi test](https://gitlab.winehq.org/bernhardu/wine/-/blob/asan-pe_2025-09-13_wi… If I understand it right, the size of `dst_addr` is 28 bytes, that much it tries to read from the `dst` pointer. Unfortunately this `dst` is reserved on the stack in `GetBestInterface` as `struct sockaddr_in sa_in;` which is just 16 bytes. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/8991#note_117605

1 0

[PATCH v2 0/3] MR9006: Several fixes & improvements when winedbg is started in auto mode.
by eric pouech (＠epo) 04 Oct '25

04 Oct '25

This series covers various fixes & improvements when a crash happens in a program which fires up winedbg in auto mode. Firstly, winedbg is a bit too strict for detecting the startup sequence (and fails to display the backtrace in these stricter cases). Third patch relaxes the startup conditions in that case. Secondly, if failing programs is a GUI, winedbg is launched in a new console (since GUI are now detached from console), but console is closed after winedbg terminates (which is after printing the crash details). So rather not useful :-( To work around this, conhost in its configuration dialog has tab 'Configuration' / 'End of program' / 'Close console' checkbox But which is not implemented. Second patch add supports for this in conhost. Lastly, conhost has the ability to store configuration per application. Hence, one can configure conhost with specific settings for winedbg. Interesting options are: - setting very high buffer zone so that conhost keeps track of all winedbg output, - unchecking the 'Close console' option. To set it for winedbg, - start it with './wine wineconsole winedbg' - use 'Properties' from the menu (right-click in conhost) to set the options for winedbg Since 68f3a8e699904bd308de0da4a1e1d2c9eb91ea96, conhost doesn't pick the registry entry for winedbg (if it exists) when started with './wine wineconsole winedbg'. Third patch solves that in a somehow hacky way, but couldn't find a better option that doesn't break https://bugs.winehq.org/show_bug.cgi?id=10941 -- v2: winedbg: No longer expect a startup sequence in auto mode. conhost: Support the close-on-exit configuration option. programs/wineconsole: Ensure conhost gets the expected title. https://gitlab.winehq.org/wine/wine/-/merge_requests/9006

4 8

Re: [PATCH v2 0/1] MR9099: user32/tests: Don't leak thread handle in test_TrackMouseEvent(). - approved
by Alexandre Julliard (＠julliard) 03 Oct '25

03 Oct '25

This merge request was approved by Alexandre Julliard. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/9099

1 0

2025

2024

2023

2022

wine-gitlab