From: Thomas Huth <thuth@redhat.com>
To: Arnd Bergmann <arnd@arndb.de>, Andy Lutomirski <luto@kernel.org>,
Thomas Gleixner <tglx@kernel.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>
Cc: soc@lists.linux.dev, shuah <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] selftests: vDSO: Fix header search list for vgetrandom-chacha.S
Date: Mon, 2 Nov 2026 09:07:04 +0100 [thread overview]
Message-ID: <4cfd205e-1150-452b-97a6-862329c838b5@redhat.com> (raw)
In-Reply-To: <256fea10-f0c9-411d-a6b6-a82cad357b57@app.fastmail.com>
On 30/10/2026 22.36, Arnd Bergmann wrote:
> On Fri, Oct 30, 2026, at 18:43, Thomas Huth wrote:
>> On aarch64, vgetrandom-chacha.S includes the assembler file from
>> arch/arm64/kernel/vdso/vgetrandom-chacha.S, and that includes
>> <asm/assembler.h> which in turn includes lots of system header files.
>> For this, we should make sure that the kernel headers of the
>> *current* kernel are in the search path of the compiler, otherwise
>> we end up including headers from /usr/include of the current distro
>> instead, and this is calling for trouble! Thus use $(KHDR_INCLUDES)
>> here to make sure that we are using the right header files.
>> (This issue has been found in a patch series that replaces __ASSEMBLY__
>> with __ASSEMBLER__ in the various kernel headers and finally stops
>> defining __ASSEMBLY__ in the kernel makefiles - when vgetrandom-chacha.S
>> now tries to include a header from /usr/include the compilation fails
>> since those headers still require __ASSEMBLY__ to fence away the C code)
>>
>> Signed-off-by: Thomas Huth <thuth@redhat.com>
>> ---
>> See this link for the build failure:
>>
>> https://lore.kernel.org/oe-kbuild-all/9e294bfd-4704-42a5-a704-f301f4afe042@app.fastmail.com/
>
> Tested-by: Arnd Bergmann <arnd@arndb.de> # (build tested)
>
> If you like, I can add this to the asm-generic tree to avoid the
> regression from your series, or Shuah can pick this up the normal
> way as a bugfix for kselftest.
It's maybe better to stick the patch close to my other patches to avoid that
other people run into problems when bisecting later, so unless Shuah objects
I'd prefer if you could pick it up, Arnd!
Thanks,
Thomas
prev parent reply other threads:[~2026-11-02 8:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 17:43 Thomas Huth
2026-10-30 21:36 ` Arnd Bergmann
2026-11-02 8:07 ` Thomas Huth [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=4cfd205e-1150-452b-97a6-862329c838b5@redhat.com \
--to=thuth@redhat.com \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@kernel.org \
--cc=shuah@kernel.org \
--cc=soc@lists.linux.dev \
--cc=tglx@kernel.org \
--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®