From: Thomas Gleixner <tglx@linutronix.de>
To: Wake Liu <wakel@google.com>,
Anna-Maria Behnsen <anna-maria@linutronix.de>,
Frederic Weisbecker <frederic@kernel.org>,
John Stultz <jstultz@google.com>, Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Cc: Stephen Boyd <sboyd@kernel.org>, wakel@google.com
Subject: Re: [PATCH v2] selftests/timers: Consolidate and fix 32-bit overflow in timespec_sub
Date: Sun, 21 Sep 2025 09:49:54 +0200 [thread overview]
Message-ID: <87qzw06y8t.ffs@tglx> (raw)
In-Reply-To: <20250915191944.9779-1-wakel@google.com>
On Tue, Sep 16 2025 at 03:19, Wake Liu wrote:
> The timespec_sub function, as implemented in several timer
timespec_sub()
https://www.kernel.org/doc/html/latest/process/maintainer-tip.html#function-references-in-changelogs
> selftests, is prone to integer overflow on 32-bit systems.
>
> The calculation `NSEC_PER_SEC * b.tv_sec` is performed using
> 32-bit arithmetic, and the result overflows before being
> stored in the 64-bit `ret` variable. This leads to incorrect
> time delta calculations and test failures.
>
> As suggested by tglx, this patch fixes the issue by:
s/this patch fixes/fix/
> 1. Creating a new `static inline` helper function,
> `timespec_to_ns`, which safely converts a `timespec` to
> nanoseconds by casting `tv_sec` to `long long` before
> multiplying with `NSEC_PER_SEC`.
>
> 2. Placing the new helper and a rewritten `timespec_sub` into
> a common header: tools/testing/selftests/timers/helpers.h.
>
> 3. Removing the duplicated, buggy implementations from all
> timer selftests and replacing them with an #include of the
> new header.
>
> This consolidates the code and ensures the calculation is
> correctly performed using 64-bit arithmetic across all tests.
This lacks a Signed-off-by.
> Changes in v2:
> - Per tglx's feedback, instead of changing NSEC_PER_SEC globally,
> this version consolidates the buggy timespec_sub() implementations
> into a new 32-bit safe inline function in a shared header.
> - Amended the commit message to be more descriptive.
change logs go behind the '---' separator as they are not part of the
commit message. It's documented how to format a change log properly.
> -#define UNREASONABLE_LAT (NSEC_PER_SEC * 5) /* hopefully we resume in 5 secs */
> +#define UNREASONABLE_LAT (NSEC_PER_SEC * 5LL) /* hopefully we resume in 5 secs */
How is this change and the pile of similar ones related to $subject and
why are they required in the first place?
> index 000000000000..652f20247091
> --- /dev/null
> +++ b/tools/testing/selftests/timers/helpers.h
> @@ -0,0 +1,31 @@
Lacks a SPDX identifier.
scripts/checkpatch.pl exists for a reason.
Thanks,
tglx
next prev parent reply other threads:[~2025-09-21 7:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 16:21 [PATCH] vdso: Define NSEC_PER_SEC as 64-bit to prevent overflow Wake Liu
2025-08-06 8:44 ` Thomas Gleixner
2025-08-06 8:55 ` Thomas Gleixner
2025-08-09 9:49 ` Wake Liu
2025-08-10 8:03 ` Thomas Gleixner
2025-08-10 8:28 ` Thomas Weißschuh
2025-09-15 19:19 ` [PATCH v2] selftests/timers: Consolidate and fix 32-bit overflow in timespec_sub Wake Liu
2025-09-21 7:49 ` Thomas Gleixner [this message]
2026-01-07 23:19 ` Carlos Llamas
2025-08-06 20:28 ` [PATCH] vdso: Define NSEC_PER_SEC as 64-bit to prevent overflow kernel test robot
2025-08-07 7:37 ` kernel test robot
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=87qzw06y8t.ffs@tglx \
--to=tglx@linutronix.de \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=shuah@kernel.org \
--cc=wakel@google.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