From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>,
"Andy Lutomirski" <luto@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Vincenzo Frascino" <vincenzo.frascino@arm.com>,
"Shuah Khan" <shuah@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <nick.desaulniers+lkml@gmail.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
"Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>,
llvm@lists.linux.dev, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v2 1/8] selftests: vDSO: fix -Wunitialized in powerpc VDSO_CALL() wrapper
Date: Tue, 12 Aug 2025 08:05:51 +0200 [thread overview]
Message-ID: <d72bb0f7-8dc3-42ca-84d9-c74b4db02445@csgroup.eu> (raw)
In-Reply-To: <20250812-vdso-tests-fixes-v2-1-90f499dd35f8@linutronix.de>
Le 12/08/2025 à 07:39, Thomas Weißschuh a écrit :
> The _rval register variable is meant to be an output operand of the asm
> statement but is instead used as input operand.
> clang 20.1 notices this and triggers -Wuninitialized warnings:
>
> tools/testing/selftests/timers/auxclock.c:154:10: error: variable '_rval' is uninitialized when used here [-Werror,-Wuninitialized]
> 154 | return VDSO_CALL(self->vdso_clock_gettime64, 2, clockid, ts);
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> tools/testing/selftests/timers/../vDSO/vdso_call.h:59:10: note: expanded from macro 'VDSO_CALL'
> 59 | : "r" (_rval) \
> | ^~~~~
> tools/testing/selftests/timers/auxclock.c:154:10: note: variable '_rval' is declared here
> tools/testing/selftests/timers/../vDSO/vdso_call.h:47:2: note: expanded from macro 'VDSO_CALL'
> 47 | register long _rval asm ("r3"); \
> | ^
>
> It seems the list of input and output operands have been switched around.
> However as the argument registers are not always initialized they can not
> be marked as pure inputs as that would trigger -Wuninitialized warnings.
> Adding _rval as another input and output operand does also not work as it
> would collide with the existing _r3 variable.
>
> Instead reuse _r3 for both the argument and the return value.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Closes: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flore.kernel.org%2Foe-kbuild-all%2F202506180223.BOOk5jDK-lkp%40intel.com%2F&data=05%7C02%7Cchristophe.leroy%40csgroup.eu%7C611dd96dfdad4dcd55d708ddd9629305%7C8b87af7d86474dc78df45f69a2011bb5%7C0%7C0%7C638905739611064850%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldUIjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=QcOje8P4T0%2BsqgkSaP%2BkT3fS875kqCZhxChDmvWVY%2Fg%3D&reserved=0
> Fixes: 6eda706a535c ("selftests: vDSO: fix the way vDSO functions are called for powerpc")
> Signed-off-by: Thomas Weißschuh <thomas.weissschuh@linutronix.de>
Reviewed-by: Christophe Leroy <christophe.leroy@csgroup.eu>
> ---
> tools/testing/selftests/vDSO/vdso_call.h | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/tools/testing/selftests/vDSO/vdso_call.h b/tools/testing/selftests/vDSO/vdso_call.h
> index bb237d771051bd4103367fc60b54b505b7586965..e7205584cbdca5e10c13c1e9425d2023b02cda7f 100644
> --- a/tools/testing/selftests/vDSO/vdso_call.h
> +++ b/tools/testing/selftests/vDSO/vdso_call.h
> @@ -44,7 +44,6 @@
> register long _r6 asm ("r6"); \
> register long _r7 asm ("r7"); \
> register long _r8 asm ("r8"); \
> - register long _rval asm ("r3"); \
> \
> LOADARGS_##nr(fn, args); \
> \
> @@ -54,13 +53,13 @@
> " bns+ 1f\n" \
> " neg 3, 3\n" \
> "1:" \
> - : "+r" (_r0), "=r" (_r3), "+r" (_r4), "+r" (_r5), \
> + : "+r" (_r0), "+r" (_r3), "+r" (_r4), "+r" (_r5), \
> "+r" (_r6), "+r" (_r7), "+r" (_r8) \
> - : "r" (_rval) \
> + : \
> : "r9", "r10", "r11", "r12", "cr0", "cr1", "cr5", \
> "cr6", "cr7", "xer", "lr", "ctr", "memory" \
> ); \
> - _rval; \
> + _r3; \
> })
>
> #else
>
next prev parent reply other threads:[~2025-08-12 6:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 5:39 [PATCH v2 0/8] selftests: vDSO: Clean up vdso_test_abi and drop vdso_test_clock_getres Thomas Weißschuh
2025-08-12 5:39 ` [PATCH v2 1/8] selftests: vDSO: fix -Wunitialized in powerpc VDSO_CALL() wrapper Thomas Weißschuh
2025-08-12 6:05 ` Christophe Leroy [this message]
2025-09-09 9:02 ` [tip: timers/vdso] selftests: vDSO: Fix " tip-bot2 for Thomas Weißschuh
2025-08-12 5:39 ` [PATCH v2 2/8] selftests: vDSO: vdso_test_abi: Correctly skip whole test with missing vDSO Thomas Weißschuh
2025-09-09 9:02 ` [tip: timers/vdso] " tip-bot2 for Thomas Weißschuh
2025-08-12 5:39 ` [PATCH v2 3/8] selftests: vDSO: vdso_test_abi: Use ksft_finished() Thomas Weißschuh
2025-09-09 9:02 ` [tip: timers/vdso] " tip-bot2 for Thomas Weißschuh
2025-08-12 5:39 ` [PATCH v2 4/8] selftests: vDSO: vdso_test_abi: Drop clock availability tests Thomas Weißschuh
2025-09-09 9:02 ` [tip: timers/vdso] " tip-bot2 for Thomas Weißschuh
2025-08-12 5:39 ` [PATCH v2 5/8] selftests: vDSO: vdso_test_abi: Use explicit indices for name array Thomas Weißschuh
2025-09-09 9:02 ` [tip: timers/vdso] " tip-bot2 for Thomas Weißschuh
2025-08-12 5:39 ` [PATCH v2 6/8] selftests: vDSO: vdso_test_abi: Test CPUTIME clocks Thomas Weißschuh
2025-09-09 9:02 ` [tip: timers/vdso] " tip-bot2 for Thomas Weißschuh
2025-08-12 5:39 ` [PATCH v2 7/8] selftests: vDSO: vdso_test_abi: Add tests for clock_gettime64() Thomas Weißschuh
2025-09-09 9:02 ` [tip: timers/vdso] " tip-bot2 for Thomas Weißschuh
2025-08-12 5:39 ` [PATCH v2 8/8] selftests: vDSO: Drop vdso_test_clock_getres Thomas Weißschuh
2025-09-09 9:02 ` [tip: timers/vdso] " tip-bot2 for Thomas Weißschuh
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=d72bb0f7-8dc3-42ca-84d9-c74b4db02445@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=Jason@zx2c4.com \
--cc=justinstitt@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=luto@kernel.org \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=tglx@linutronix.de \
--cc=thomas.weissschuh@linutronix.de \
--cc=vincenzo.frascino@arm.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
all inboxes | Powered by JetHome®