- wine-gitlab - winehq.org

[PATCH 0/1] MR2150: include: Allow multiple definitions on GCC with DECLSPEC_SELECTANY.
by Alex Henrie (＠alexhenrie) 09 Feb '23

09 Feb '23

Needed to compile Tera Term. As far as I can tell, GCC has always supported `__attribute__((weak))`. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/2150

2 1

[PATCH v15 0/2] MR2100: ntdll: Do not send data to port 0.
by Jason Beetham (＠beef331) 09 Feb '23

09 Feb '23

On Windows it seems sending to port 0 does nothing and does not error. Presently sendmsg errors with EINVAL. This works around it, by checking if it's port 0 then skipping the data. -- v15: ntdll: Do not send data to port 0. https://gitlab.winehq.org/wine/wine/-/merge_requests/2100

4 4

[PATCH 0/1] MR2147: ws2_32: Forbid passing zero buffers to WSARecv().
by Zebediah Figura (＠zfigura) 09 Feb '23

09 Feb '23

This may address bug 54074, but I'm not sure. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/2147

3 2

[PATCH v14 0/2] MR2100: ntdll: Do not send data to port 0.
by Jason Beetham (＠beef331) 09 Feb '23

09 Feb '23

On Windows it seems sending to port 0 does nothing and does not error. Presently sendmsg errors with EINVAL. This works around it, by checking if it's port 0 then skipping the data. -- v14: ntdll: Do not send data to port 0. https://gitlab.winehq.org/wine/wine/-/merge_requests/2100

2 3

Re: [PATCH v13 0/2] MR2100: ntdll: Do not send data to port 0.
by Zebediah Figura (＠zfigura) 09 Feb '23

09 Feb '23

> > but we could return it from the send_socket server request > > Where would I look into this I see the 'macro' call inside `sock_send`, but looking at `send_socket_reply` does not seem to have an protocol attached? It's automatically generated. You'd need to edit protocol.def and then run tools/make_requests. -- https://gitlab.winehq.org/wine/wine/-/merge_requests/2100#note_23545

1 0

[PATCH v11 0/2] MR2100: ntdll: Do not send data to port 0.
by Jason Beetham (＠beef331) 09 Feb '23

09 Feb '23

On Windows it seems sending to port 0 does nothing and does not error. Presently sendmsg errors with EINVAL. This works around it, by checking if it's port 0 then skipping the data. -- v11: ntdll: Do not send data to port 0. https://gitlab.winehq.org/wine/wine/-/merge_requests/2100

3 3

Re: [PATCH v13 0/2] MR2100: ntdll: Do not send data to port 0.
by Jason Beetham (＠beef331) 09 Feb '23

09 Feb '23

> but we could return it from the send_socket server request Where would I look into this I see the 'macro' call inside `sock_send`, but looking at `send_socket_reply` does not seem to have an protocol attached? -- https://gitlab.winehq.org/wine/wine/-/merge_requests/2100#note_23543

1 0

[PATCH v3 0/3] MR1895: Fixes for NtOpenFile of read-only files with FILE_WRITE_ATTRIBUTES
by Joel Holdsworth (＠jhol) 08 Feb '23

08 Feb '23

Previously, the Wine implementation of `NtOpenFile` would fail to open read-only files for `FILE_WRITE_ATTRIBUTES` access in wine-server, because it would attempt to open the file with `O_RDWR` or `O_WRONLY` access. This patch-set adds test cases to highlight the issue, and solves it by only opening the file with write access where necessary. * Wine Bug: [#50771](https://bugs.winehq.org/show_bug.cgi?id=50771) * Related Wine-Staging Patches: * [0002-server-Allow-to-open-files-without-any-permission-bi.patch](https://gi… * [0006-ntdll-tests-Added-tests-for-open-behaviour-on-readon.patch](https://gi… * [0007-server-FILE_WRITE_ATTRIBUTES-should-succeed-for-read.patch](https://gi… -- v3: server: Allow to open read-only files with FILE_WRITE_ATTRIBUTES https://gitlab.winehq.org/wine/wine/-/merge_requests/1895

3 4

[PATCH v10 0/2] MR2100: ntdll: Do not send data to port 0.
by Jason Beetham (＠beef331) 08 Feb '23

08 Feb '23

On Windows it seems sending to port 0 does nothing and does not error. Presently sendmsg errors with EINVAL. This works around it, by checking if it's port 0 then skipping the data. -- v10: ntdll: Do not send data to port 0. ws2_32/tests: Check if sending to port 0 succeeds. https://gitlab.winehq.org/wine/wine/-/merge_requests/2100

3 4

[PATCH v12 0/2] MR2100: ntdll: Do not send data to port 0.
by Jason Beetham (＠beef331) 08 Feb '23

08 Feb '23

On Windows it seems sending to port 0 does nothing and does not error. Presently sendmsg errors with EINVAL. This works around it, by checking if it's port 0 then skipping the data. -- v12: ntdll: Do not send data to port 0. https://gitlab.winehq.org/wine/wine/-/merge_requests/2100

3 3

2025

2024

2023

2022

wine-gitlab