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 2/4] selftests: ntsync: fix wake_all CREATE_EVENT fd expectation
Date: Wed, 01 Jul 2026 11:38:16 -0500 [thread overview]
Message-ID: <6279993.lOV4Wx5bFT@camazotz> (raw)
In-Reply-To: <20260628024239.152852-3-ivanrwcm25@gmail.com>
On Saturday, 27 June 2026 21:42:37 CDT Iván Ezequiel Rodriguez wrote:
> wake_all used EXPECT_EQ(0, objs[3]) after NTSYNC_IOC_CREATE_EVENT.
> The ioctl returns a non-negative file descriptor on success; check
> EXPECT_LE(0, objs[3]) like the other CREATE_* paths. The incorrect
> expectation was noted on list (Mar 2025) but is still present in
> mainline.
>
> Signed-off-by: Iván Ezequiel Rodriguez <ivanrwcm25@gmail.com>
> ---
> tools/testing/selftests/drivers/ntsync/ntsync.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/drivers/ntsync/ntsync.c b/tools/testing/selftests/drivers/ntsync/ntsync.c
> index e6a37214aa46..12b4b81edf7f 100644
> --- a/tools/testing/selftests/drivers/ntsync/ntsync.c
> +++ b/tools/testing/selftests/drivers/ntsync/ntsync.c
> @@ -968,7 +968,7 @@ TEST(wake_all)
> auto_event_args.manual = false;
> auto_event_args.signaled = true;
> objs[3] = ioctl(fd, NTSYNC_IOC_CREATE_EVENT, &auto_event_args);
> - EXPECT_EQ(0, objs[3]);
> + EXPECT_LE(0, objs[3]);
>
> wait_args.timeout = get_abs_timeout(1000);
> wait_args.objs = (uintptr_t)objs;
>
Reviewed-by: Elizabeth Figura <zfigura@codeweavers.com>
--
This was already sent as <https://lore.kernel.org/all/20250314071454.201697-2-suhui@nfschina.com/> and never committed.
next prev parent reply other threads:[~2026-07-01 16:38 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 [this message]
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
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=6279993.lOV4Wx5bFT@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