From: bruce.ashfield@gmail.com
To: richard.purdie@linuxfoundation.org
Cc: openembedded-core@lists.openembedded.org
Subject: [meta][PATCH 04/06] kernel-devsrc: strip riscv vdso-cfi-offsets .cmd file
Date: Fri, 21 Aug 2026 07:25:06 -0400 [thread overview]
Message-ID: <20260821112509.861559-5-bruce.ashfield@gmail.com> (raw)
In-Reply-To: <20260821112509.861559-1-bruce.ashfield@gmail.com>
From: Bruce Ashfield <bruce.ashfield@gmail.com>
The riscv vDSO gained a CFI-instrumented build (VDSO_CFI_BUILD): when
enabled, arch/riscv/kernel/vdso/Makefile emits the offsets header as
include/generated/vdso-cfi-offsets.h instead of vdso-offsets.h. The
associated kbuild .cmd file records the full compiler invocation and
leaks TMPDIR / the build-host HOME into both the kernel-devsrc and
linux-headers packages, failing do_package_qa on qemuriscv64:
QA Issue: File .../include/generated/.vdso-cfi-offsets.h.cmd in package
kernel-devsrc contains reference to TMPDIR [buildpaths]
Remove it alongside the existing vdso*-offsets .cmd files. linux-headers
copies $kerneldir/build/* after this step, so dropping the build-tree
copy clears both packages. riscv-only today and a no-op (rm -f)
elsewhere, so it is safe for all architectures.
Signed-off-by: Bruce Ashfield <bruce.ashfield@gmail.com>
---
meta/recipes-kernel/linux/kernel-devsrc.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-kernel/linux/kernel-devsrc.bb b/meta/recipes-kernel/linux/kernel-devsrc.bb
index 4ae121eb62..47c0abfa38 100644
--- a/meta/recipes-kernel/linux/kernel-devsrc.bb
+++ b/meta/recipes-kernel/linux/kernel-devsrc.bb
@@ -129,6 +129,8 @@ do_install() {
rm -f $kerneldir/include/generated/.vdso-offsets.h.cmd
rm -f $kerneldir/build/include/generated/.vdso-offsets.h.cmd
+ rm -f $kerneldir/include/generated/.vdso-cfi-offsets.h.cmd
+ rm -f $kerneldir/build/include/generated/.vdso-cfi-offsets.h.cmd
rm -f $kerneldir/build/include/generated/.compat_vdso-offsets.h.cmd
rm -f $kerneldir/build/include/generated/.vdso32-offsets.h.cmd
rm -f $kerneldir/build/include/generated/.vdso64-offsets.h.cmd
--
2.43.0
next prev parent reply other threads:[~2026-08-21 11:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 11:25 [PATCH 0/6] kernel-yocto: 6.18 and 7.2 RFC/prep bruce.ashfield
2026-08-21 11:25 ` [meta][PATCH 01/06] linux-yocto/6.18: update to v6.18.44 bruce.ashfield
2026-08-21 11:25 ` [meta][PATCH 02/06] linux-libc-headers: update to 7.2 bruce.ashfield
2026-08-21 11:25 ` [meta][PATCH 03/06] linux-yocto/7.2: introduce reference kernel recipes bruce.ashfield
2026-08-27 6:20 ` [OE-core] " Mathieu Dubois-Briand
[not found] ` <18CF953235C263D2.642712@lists.openembedded.org>
2026-08-27 7:05 ` Mathieu Dubois-Briand
2026-08-27 15:37 ` Mathieu Dubois-Briand
2026-08-21 11:25 ` bruce.ashfield [this message]
2026-08-21 11:25 ` [meta][PATCH 05/06] kernel-devsrc: copy arch/x86 vdso2c sources for on-target prepare bruce.ashfield
2026-08-21 11:25 ` [meta-yocto-bsp][PATCH 06/06] linux-yocto/6.18: update to v6.18.44 bruce.ashfield
2026-08-21 11:33 ` Patchtest results for " patchtest
2026-08-21 15:43 ` [OE-core] [PATCH 0/6] kernel-yocto: 6.18 and 7.2 RFC/prep Khem Raj
2026-08-21 21:51 ` Khem Raj
2026-08-21 21:45 ` Richard Purdie
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=20260821112509.861559-5-bruce.ashfield@gmail.com \
--to=bruce.ashfield@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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