Re: [PATCH v44 0/6] MR7650: Add support for AF_UNIX sockets (followup)

[Ralf Habacker (＠rhabacker)]

On Fri Nov 14 07:44:36 2025 +0000, Ralf Habacker wrote:
> After adding AF_UNIX-related tests with
> https://gitlab.winehq.org/rhabacker/wine/-/commit/41ed5dc8ca55ad74dd9f9ecae1...
> by @julliard, the following command line was executed
> (cd ~/src/wine-build; WINEPREFIX=~/src/wine/.wine strace
> ../wine/tools/runtest -q -P wine -T . -M ws2_32.dll -p
> dlls/ws2_32/tests/i386-windows/ws2_32_test.exe sock) > out.log 2>&1
>
> and the following test errors occur:
> sock.c:14624: Test failed: test_afunix.sock: wrong attr ffffffff
> sock.c:14658: Test failed: test_afunix.sock: wrong family 0
> sock.c:14693: Test failed: test_afunix.sock: wrong family 0
> sock.c:14703: Test failed: test_afunix.sock: wrong attr ffffffff
> sock.c:14712: Test failed: test_afunix.sock: wrong error 433
> sock.c:14716: Test failed: test_afunix.sock: open failed 433
> sock.c:14719: Test failed: test_afunix.sock: DeviceIoControl failed 6
> sock.c:14720: Test failed: test_afunix.sock: got tag 0
> sock.c:14624: Test failed: .\tmp.sock: wrong attr ffffffff
> sock.c:14658: Test failed: .\tmp.sock: wrong family 0
> sock.c:14693: Test failed: .\tmp.sock: wrong family 0
> sock.c:14703: Test failed: .\tmp.sock: wrong attr ffffffff
> sock.c:14712: Test failed: .\tmp.sock: wrong error 433
> sock.c:14716: Test failed: .\tmp.sock: open failed 433
> sock.c:14719: Test failed: .\tmp.sock: DeviceIoControl failed 6
> sock.c:14720: Test failed: .\tmp.sock: got tag 0
> sock.c:14624: Test failed: C:\users\ralf\AppData\Local\Temp\tmp.sock:
> wrong attr ffffffff
> sock.c:14658: Test failed: C:\users\ralf\AppData\Local\Temp\tmp.sock:
> wrong family 0
> sock.c:14693: Test failed: C:\users\ralf\AppData\Local\Temp\tmp.sock:
> wrong family 0
> sock.c:14703: Test failed: C:\users\ralf\AppData\Local\Temp\tmp.sock:
> wrong attr ffffffff
> sock.c:14712: Test failed: C:\users\ralf\AppData\Local\Temp\tmp.sock:
> wrong error 433
> sock.c:14716: Test failed: C:\users\ralf\AppData\Local\Temp\tmp.sock:
> open failed 433
> sock.c:14719: Test failed: C:\users\ralf\AppData\Local\Temp\tmp.sock:
> DeviceIoControl failed 6
> sock.c:14720: Test failed: C:\users\ralf\AppData\Local\Temp\tmp.sock:
> got tag 0
> sock.c:14624: Test failed:
> \??\C:\users\ralf\AppData\Local\Temp\tmp.sock: wrong attr ffffffff
> sock.c:14658: Test failed:
> \??\C:\users\ralf\AppData\Local\Temp\tmp.sock: wrong family 0
> sock.c:14693: Test failed:
> \??\C:\users\ralf\AppData\Local\Temp\tmp.sock: wrong family 0
> sock.c:14703: Test failed:
> \??\C:\users\ralf\AppData\Local\Temp\tmp.sock: wrong attr ffffffff
> sock.c:14712: Test failed:
> \??\C:\users\ralf\AppData\Local\Temp\tmp.sock: wrong error 433
> sock.c:14716: Test failed:
> \??\C:\users\ralf\AppData\Local\Temp\tmp.sock: open failed 433
> sock.c:14719: Test failed:
> \??\C:\users\ralf\AppData\Local\Temp\tmp.sock: DeviceIoControl failed 6
> sock.c:14720: Test failed:
> \??\C:\users\ralf\AppData\Local\Temp\tmp.sock: got tag 0

For comparison, I ran “ws2_32_test.exe sock” on a virtual Win11 guest machine, which produced the following output:
```
.\ws2_32_test.exe
27cc:sock: 841 tests executed (0 marked as todo, 0 as flaky, 0 failures), 0 skipped.
```
This shows that the problems listed are indeed present in Wine.