From: Nathan Chancellor <nathan@kernel.org>
To: Marco Elver <elver@google.com>
Cc: Heiko Carstens <hca@linux.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
kernel test robot <lkp@intel.com>,
llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [peterz-queue:locking/core 34/39] WARNING: modpost: EXPORT symbol "stack_depot_save_flags" [vmlinux] version generation failed, symbol will not be versioned.
Date: Wed, 7 Jan 2026 15:56:49 -0700 [thread overview]
Message-ID: <20260107225649.GA1867428@ax162> (raw)
In-Reply-To: <aV7fxXjaOBtHhI9X@elver.google.com>
On Wed, Jan 07, 2026 at 11:35:49PM +0100, Marco Elver wrote:
> This works:
Ah duh :)
> --- a/include/linux/compiler-context-analysis.h
> +++ b/include/linux/compiler-context-analysis.h
> @@ -6,7 +6,7 @@
> #ifndef _LINUX_COMPILER_CONTEXT_ANALYSIS_H
> #define _LINUX_COMPILER_CONTEXT_ANALYSIS_H
>
> -#if defined(WARN_CONTEXT_ANALYSIS) && !defined(__CHECKER__)
> +#if defined(WARN_CONTEXT_ANALYSIS) && !defined(__CHECKER__) && !defined(__GENKSYMS__)
>
> I guess the genksyms parser just can't deal with some of the syntax
> (just like __CHECKER__).
Right. Not to mention that these macros should have no bearing on the
ABI stability for the sake of module versioning so there is no point to
consider them during genksyms (if I understand correctly).
Cheers,
Nathan
next prev parent reply other threads:[~2026-01-07 22:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-22 14:11 [peterz-queue:locking/core 34/39] WARNING: modpost: EXPORT symbol "stack_depot_save_flags" [vmlinux] version generation failed, symbol will not be versioned kernel test robot
2026-01-05 15:35 ` Peter Zijlstra
2026-01-07 11:39 ` Heiko Carstens
2026-01-07 11:46 ` Heiko Carstens
2026-01-07 20:45 ` Nathan Chancellor
2026-01-07 22:35 ` Marco Elver
2026-01-07 22:56 ` Nathan Chancellor [this message]
2026-01-08 7:51 ` Peter Zijlstra
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=20260107225649.GA1867428@ax162 \
--to=nathan@kernel.org \
--cc=elver@google.com \
--cc=hca@linux.ibm.com \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.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