The Linux Kernel Mailing List
 help / color / mirror / Atom feed
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 0/4] ntsync documentation, selftests, and owner validation
Date: Wed, 01 Jul 2026 11:45:13 -0500	[thread overview]
Message-ID: <3049825.e9J7NaK4W3@camazotz> (raw)
In-Reply-To: <20260628024239.152852-1-ivanrwcm25@gmail.com>

On Saturday, 27 June 2026 21:42:35 CDT Iván Ezequiel Rodriguez wrote:
> This series improves ntsync without changing wait/wake semantics:
> 
>  1/4 — Align Documentation/userspace-api/ntsync.rst with
>        include/uapi/linux/ntsync.h (ioctl macro names and struct layout).
> 
>  2/4 — Fix wake_all selftest: CREATE_EVENT returns an fd, not zero.
> 
>  3/4 — Add selftests for documented EINVAL cases (zero owner, non-zero
>        pad, cross-instance object use).
> 
>  4/4 — Reject wait ioctls when owner is zero, matching the documented
>        uAPI (3/4 depends on 4/4 for the owner tests).
> 
> Patch 4/4 closes a spec gap: Documentation/userspace-api/ntsync.rst
> requires EINVAL when wait owner is zero, but setup_wait() only validated
> pad and flags.  Unlock/kill mutex ioctls already reject owner == 0.
> 
> Testing:
> - scripts/checkpatch.pl --strict --no-tree: clean (4/4 patches)
> - make headers && make -C tools/testing/selftests TARGETS=drivers/ntsync
> - Kernel 7.1.0-ntsync-test+ (CONFIG_NTSYNC=y), QEMU x86_64 initramfs:
>   tools/testing/selftests/drivers/ntsync/ntsync — 12/12 PASS,
>   including wake_all and wait_args_validation
> - On 6.17.0-35-generic with the distro ntsync.ko (without patch 4/4):
>   wait_args_validation fails on owner==0 (wait proceeds instead of
>   EINVAL), confirming the gap this series fixes
> 
> Elizabeth Figura <zfigura@codeweavers.com>
> wine-devel@winehq.org
> ---
>  Documentation/userspace-api/ntsync.rst         | 22 +++++-----
>  tools/testing/selftests/drivers/ntsync/ntsync.c | 45 ++++++++++++++++++++
>  drivers/misc/ntsync.c                          |  3 ++
>  3 files changed, 59 insertions(+), 11 deletions(-)
> 
> Iván Ezequiel Rodriguez (4):
>   docs: ntsync: align uAPI ioctl names and struct layout with ntsync.h
>   selftests: ntsync: fix wake_all CREATE_EVENT fd expectation
>   selftests: ntsync: add wait argument validation tests
>   ntsync: reject wait ioctls with zero owner
> 
> --
> 2.43.0
> 

Some of these changes overlap with changes already sent in <https://lore.kernel.org/all/20250314071454.201697-1-suhui@nfschina.com/>, which were never applied. This series does not overlap with patches 2/4 and 3/4 from that series.



      parent reply	other threads:[~2026-07-01 16:45 UTC|newest]

Thread overview: 10+ 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
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 ` Elizabeth Figura [this message]

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=3049825.e9J7NaK4W3@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