From: Elizabeth Figura <zfigura@codeweavers.com>
To: "Iván Ezequiel Rodriguez" <ivanrwcm25@gmail.com>
Cc: wine-devel@winehq.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] docs: ntsync: align uAPI ioctl names and struct layout with ntsync.h
Date: Wed, 01 Jul 2026 11:37:36 -0500 [thread overview]
Message-ID: <12921830.O9o76ZdvQC@camazotz> (raw)
In-Reply-To: <20260628024239.152852-2-ivanrwcm25@gmail.com>
On Saturday, 27 June 2026 21:42:36 CDT Iván Ezequiel Rodriguez wrote:
> The userspace-api reference used stale macro names (SEM_POST, SET_EVENT,
> READ_*, KILL_OWNER) and struct field order that did not match
> include/uapi/linux/ntsync.h. Update the documentation to match the
> published uapi so Wine and other consumers grep the correct symbols.
>
> Signed-off-by: Iván Ezequiel Rodriguez <ivanrwcm25@gmail.com>
> ---
> Documentation/userspace-api/ntsync.rst | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
> diff --git a/Documentation/userspace-api/ntsync.rst b/Documentation/userspace-api/ntsync.rst
> index 25e7c4aef968..535585331380 100644
> --- a/Documentation/userspace-api/ntsync.rst
> +++ b/Documentation/userspace-api/ntsync.rst
> @@ -83,18 +83,18 @@ structures used in ioctl calls::
> };
>
> struct ntsync_event_args {
> - __u32 signaled;
> __u32 manual;
> + __u32 signaled;
> };
>
> struct ntsync_wait_args {
> __u64 timeout;
> __u64 objs;
> __u32 count;
> - __u32 owner;
> __u32 index;
> - __u32 alert;
> __u32 flags;
> + __u32 owner;
> + __u32 alert;
> __u32 pad;
> };
>
> @@ -152,7 +152,7 @@ The ioctls on the device file are as follows:
>
> The ioctls on the individual objects are as follows:
>
> -.. c:macro:: NTSYNC_IOC_SEM_POST
> +.. c:macro:: NTSYNC_IOC_SEM_RELEASE
>
> Post to a semaphore object. Takes a pointer to a 32-bit integer,
> which on input holds the count to be added to the semaphore, and on
> @@ -186,7 +186,7 @@ The ioctls on the individual objects are as follows:
> unowned and signaled, and eligible threads waiting on it will be
> woken as appropriate.
>
> -.. c:macro:: NTSYNC_IOC_SET_EVENT
> +.. c:macro:: NTSYNC_IOC_EVENT_SET
>
> Signal an event object. Takes a pointer to a 32-bit integer, which on
> output contains the previous state of the event.
> @@ -194,12 +194,12 @@ The ioctls on the individual objects are as follows:
> Eligible threads will be woken, and auto-reset events will be
> designaled appropriately.
>
> -.. c:macro:: NTSYNC_IOC_RESET_EVENT
> +.. c:macro:: NTSYNC_IOC_EVENT_RESET
>
> Designal an event object. Takes a pointer to a 32-bit integer, which
> on output contains the previous state of the event.
>
> -.. c:macro:: NTSYNC_IOC_PULSE_EVENT
> +.. c:macro:: NTSYNC_IOC_EVENT_PULSE
>
> Wake threads waiting on an event object while leaving it in an
> unsignaled state. Takes a pointer to a 32-bit integer, which on
> @@ -213,7 +213,7 @@ The ioctls on the individual objects are as follows:
> afterwards, and a simultaneous read operation will always report the
> event as unsignaled.
>
> -.. c:macro:: NTSYNC_IOC_READ_SEM
> +.. c:macro:: NTSYNC_IOC_SEM_READ
>
> Read the current state of a semaphore object. Takes a pointer to
> struct :c:type:`ntsync_sem_args`, which is used as follows:
> @@ -225,7 +225,7 @@ The ioctls on the individual objects are as follows:
> * - ``max``
> - On output, contains the maximum count of the semaphore.
>
> -.. c:macro:: NTSYNC_IOC_READ_MUTEX
> +.. c:macro:: NTSYNC_IOC_MUTEX_READ
>
> Read the current state of a mutex object. Takes a pointer to struct
> :c:type:`ntsync_mutex_args`, which is used as follows:
> @@ -242,7 +242,7 @@ The ioctls on the individual objects are as follows:
> ``EOWNERDEAD``. In this case, ``count`` and ``owner`` are set to
> zero.
>
> -.. c:macro:: NTSYNC_IOC_READ_EVENT
> +.. c:macro:: NTSYNC_IOC_EVENT_READ
>
> Read the current state of an event object. Takes a pointer to struct
> :c:type:`ntsync_event_args`, which is used as follows:
> @@ -255,7 +255,7 @@ The ioctls on the individual objects are as follows:
> - On output, contains 1 if the event is a manual-reset event,
> and 0 otherwise.
>
> -.. c:macro:: NTSYNC_IOC_KILL_OWNER
> +.. c:macro:: NTSYNC_IOC_MUTEX_KILL
>
> Mark a mutex as unowned and abandoned if it is owned by the given
> owner. Takes an input-only pointer to a 32-bit integer denoting the
>
Reviewed-by: Elizabeth Figura <zfigura@codeweavers.com>
--
This was already sent as <https://lore.kernel.org/all/20250314071454.201697-5-suhui@nfschina.com/>, which was never applied, although that did not include modifications to the struct field order.
next prev parent reply other threads:[~2026-07-01 16:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-28 2:42 [PATCH 0/4] ntsync documentation, selftests, and owner validation Iván Ezequiel Rodriguez
2026-06-28 2:42 ` [PATCH 1/4] docs: ntsync: align uAPI ioctl names and struct layout with ntsync.h Iván Ezequiel Rodriguez
2026-07-01 16:37 ` Elizabeth Figura [this message]
2026-06-28 2:42 ` [PATCH 2/4] selftests: ntsync: fix wake_all CREATE_EVENT fd expectation Iván Ezequiel Rodriguez
2026-07-01 16:38 ` Elizabeth Figura
2026-06-28 2:42 ` [PATCH 3/4] selftests: ntsync: add wait argument validation tests Iván Ezequiel Rodriguez
2026-07-01 16:38 ` Elizabeth Figura
2026-06-28 2:42 ` [PATCH 4/4] ntsync: reject wait ioctls with zero owner Iván Ezequiel Rodriguez
2026-07-01 16:38 ` Elizabeth Figura
2026-07-01 16:45 ` [PATCH 0/4] ntsync documentation, selftests, and owner validation Elizabeth Figura
-- strict thread matches above, loose matches on Subject: below --
2026-07-20 17:17 [PATCH 0/4] ntsync miscellaneous patches Elizabeth Figura
2026-07-20 17:17 ` [PATCH 1/4] docs: ntsync: align uAPI ioctl names and struct layout with ntsync.h Elizabeth Figura
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12921830.O9o76ZdvQC@camazotz \
--to=zfigura@codeweavers.com \
--cc=ivanrwcm25@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wine-devel@winehq.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox