From: Thomas Gleixner <tglx@linutronix.de>
To: "Terry Tritton" <terry.tritton@linaro.org>,
"Shuah Khan" <shuah@kernel.org>, "Ingo Molnar" <mingo@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Darren Hart" <dvhart@infradead.org>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"André Almeida" <andrealmeid@igalia.com>
Cc: ttritton@google.com, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
Terry Tritton <terry.tritton@linaro.org>,
Wei Gao <wegao@suse.com>
Subject: Re: [PATCH v3] selftests/futex: Convert 32bit timespec struct to 64bit version for 32bit compatibility mode
Date: Wed, 02 Jul 2025 22:15:06 +0200 [thread overview]
Message-ID: <87y0t6jqnp.ffs@tglx> (raw)
In-Reply-To: <20250702102157.5222-1-terry.tritton@linaro.org>
On Wed, Jul 02 2025 at 11:21, Terry Tritton wrote:
> Futex_waitv can not accept old_timespec32 struct, so userspace should
sys_futex_wait()
> convert it from 32bit to 64bit before syscall in 32bit compatible mode.
>
> This fix is based off [1]
>
> Link: https://lore.kernel.org/all/20231203235117.29677-1-wegao@suse.com/ [1]
>
> Originally-by: Wei Gao <wegao@suse.com>
> Signed-off-by: Terry Tritton <terry.tritton@linaro.org>
> ---
> Changes in v3:
> - Fix signed-off-by chain but for real this time
>
> Changes in v2:
> - Fix signed-off-by chain
>
> .../testing/selftests/futex/include/futex2test.h | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/tools/testing/selftests/futex/include/futex2test.h b/tools/testing/selftests/futex/include/futex2test.h
> index ea79662405bc..6780e51eb2d6 100644
> --- a/tools/testing/selftests/futex/include/futex2test.h
> +++ b/tools/testing/selftests/futex/include/futex2test.h
> @@ -55,6 +55,13 @@ struct futex32_numa {
> futex_t numa;
> };
>
> +#if !defined(__LP64__)
> +struct timespec64 {
> + int64_t tv_sec;
> + int64_t tv_nsec;
> +};
> +#endif
Why not use __kernel_timespec which is the actual data type that syscall
requests?
> +
> /**
> * futex_waitv - Wait at multiple futexes, wake on any
> * @waiters: Array of waiters
> @@ -65,7 +72,15 @@ struct futex32_numa {
> static inline int futex_waitv(volatile struct futex_waitv *waiters, unsigned long nr_waiters,
> unsigned long flags, struct timespec *timo, clockid_t clockid)
> {
> +#if !defined(__LP64__)
> + struct timespec64 timo64 = {0};
> +
> + timo64.tv_sec = timo->tv_sec;
> + timo64.tv_nsec = timo->tv_nsec;
> + return syscall(__NR_futex_waitv, waiters, nr_waiters, flags, &timo64, clockid);
> +#else
> return syscall(__NR_futex_waitv, waiters, nr_waiters, flags, timo, clockid);
> +#endif
You simply can do
struct __kernel_timespec ts = {
.tv_sec = timo->tv_sec,
.tv_nsec = timo->tv_nsec,
};
return syscall(__NR_futex_waitv, waiters, nr_waiters, flags, &ts, clockid);
unconditionally. No?
Thanks,
tglx
next prev parent reply other threads:[~2025-07-02 20:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 10:21 [PATCH v3] selftests/futex: Convert 32bit timespec struct to 64bit version for 32bit compatibility mode Terry Tritton
2025-07-02 20:15 ` Thomas Gleixner [this message]
2025-07-03 23:58 ` Wei Gao
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=87y0t6jqnp.ffs@tglx \
--to=tglx@linutronix.de \
--cc=andrealmeid@igalia.com \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=shuah@kernel.org \
--cc=terry.tritton@linaro.org \
--cc=ttritton@google.com \
--cc=wegao@suse.com \
/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