From: Kees Cook <kees@kernel.org>
To: Jaihind Yadav <jaihindy@qti.qualcomm.com>
Cc: nathan@kernel.org, nsc@kernel.org,
linux-hardening@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-modules@vger.kernel.org
Subject: Re: [PATCH v3] scripts/gcc-plugins: suppress recorded GCC switches for extmod builds
Date: Tue, 1 Sep 2026 14:11:11 -0700 [thread overview]
Message-ID: <202609011410.3F904D4@keescook> (raw)
In-Reply-To: <20260820060116.786173-1-jaihindy@qti.qualcomm.com>
On Thu, Aug 20, 2026 at 11:31:16AM +0530, Jaihind Yadav wrote:
> With GCC plugins enabled, external module builds can record
> -fplugin=... paths in DWARF producer metadata via
> -grecord-gcc-switches, leaking host/build specific paths and
> triggering QA checks.
>
> Handle this in scripts/Makefile.gcc-plugins for KBUILD_EXTMOD
> builds by adding -gno-record-gcc-switches to plugin cflags.
>
> This keeps plugin behavior unchanged while avoiding absolute
> plugin path leakage in external module debug metadata.
>
> Suggested-by: Nathan Chancellor <nathan@kernel.org>
> Link: https://lore.kernel.org/all/20260817185146.GC1249844@ax162/
> Signed-off-by: Jaihind Yadav <jaihindy@qti.qualcomm.com>
Acked-by: Kees Cook <kees@kernel.org>
I'm fine with this going via the kbuild tree. :)
-Kees
--
Kees Cook
next prev parent reply other threads:[~2026-09-01 21:11 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 9:35 [PATCH 0/1] scripts: kstack_erase: avoid absolute stackleak plugin path Jaihind Yadav
2026-07-20 9:35 ` [PATCH 1/1] scripts: kstack_erase: use relative " Jaihind Yadav
2026-07-22 14:45 ` Nicolas Schier
2026-07-22 17:17 ` Jaihind Yadav
2026-07-22 19:00 ` Jaihind Yadav
2026-07-24 20:18 ` Nicolas Schier
2026-08-03 18:12 ` Nathan Chancellor
2026-08-12 10:55 ` Jaihind Yadav
2026-08-12 16:48 ` Nathan Chancellor
2026-08-13 8:29 ` [PATCH v2] kstack_erase: suppress -grecord-gcc-switches for external module builds Jaihind Yadav
2026-08-13 16:42 ` Kees Cook
2026-08-14 8:27 ` Jaihind Yadav
2026-08-14 18:23 ` Nicolas Schier
2026-08-14 22:45 ` Nathan Chancellor
2026-08-16 8:11 ` Jaihind Yadav
2026-08-17 18:51 ` Nathan Chancellor
2026-08-19 5:03 ` Jaihind Yadav
2026-08-20 6:01 ` [PATCH v3] scripts/gcc-plugins: suppress recorded GCC switches for extmod builds Jaihind Yadav
2026-08-28 15:13 ` Nicolas Schier
2026-09-01 21:11 ` Kees Cook [this message]
2026-09-01 23:13 ` Nathan Chancellor
2026-09-02 5:21 ` Jaihind Yadav
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=202609011410.3F904D4@keescook \
--to=kees@kernel.org \
--cc=jaihindy@qti.qualcomm.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=nsc@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®