From: "Arnd Bergmann" <arnd@arndb.de>
To: "Naresh Kamboju" <naresh.kamboju@linaro.org>,
clang-built-linux <llvm@lists.linux.dev>,
"open list:KERNEL SELFTEST FRAMEWORK"
<linux-kselftest@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org
Cc: "Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Dan Carpenter" <dan.carpenter@linaro.org>,
"Anders Roxell" <anders.roxell@linaro.org>,
shuah <shuah@kernel.org>
Subject: Re: selftest/vDSO: vdso_test_abi tests with gcc-13 and pass with clang-19
Date: Wed, 12 Feb 2025 17:23:25 +0100 [thread overview]
Message-ID: <b7dc96e3-4d8a-4da8-adda-161f8ff815b1@app.fastmail.com> (raw)
In-Reply-To: <CA+G9fYuw3XJ3NcYGHT=Jt9mQP_si49GQNEa6sSNLeqDm9A6+Cw@mail.gmail.com>
On Wed, Feb 12, 2025, at 15:29, Naresh Kamboju wrote:
> The kselftest-vDSO/vdso_test_abi test encounters failures when built
> and executed using GCC-13 on armv7 architecture.
> The issue has been observed on both TI X15 devices and QEMU-armv7.
>
> Interestingly, the same test passes without any issues when built using
> Clang-19.This failure is specific to GCC-13. but test case should have
> been failed on clang toolchain but it did not.
To clarify: the failure depends on how the toolchain is built:
for compilers using the default 32-bit time_t in glibc, ltp does
not notice a problem, but using gcc it will run into a testcase
bug because the vdso_test_abi.c file incorrectly mixes libc types
and kernel types.
> The Clang toolchain likely defaults to the traditional 32-bit time_t on
> 32-bit Debian Trixie (except x86), leading to an ABI issue similar to
> older compilers. This is affecting compatibility.
>
> This is not a new regression,
> this report generated on Linux next but also seen on Linux stable tree.
>
> Test name: kselftest-vDSO/vdso_test_abi
> Fails: gcc-13
> pass: clang-19
>
> Arnd Bergmann investigated and proposed a patch which fixes the problem.
The patch only makes changes ltp so it tests the old system calls
correctly regardless of the toolchain settings.
Someone still needs to change LTP to include this change as well as
add tests for the 64-bit time_t vdso functions.
Arnd
prev parent reply other threads:[~2025-02-12 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 14:29 Naresh Kamboju
2025-02-12 16:23 ` Arnd Bergmann [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=b7dc96e3-4d8a-4da8-adda-161f8ff815b1@app.fastmail.com \
--to=arnd@arndb.de \
--cc=anders.roxell@linaro.org \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=llvm@lists.linux.dev \
--cc=naresh.kamboju@linaro.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=shuah@kernel.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
all inboxes | Powered by JetHome®