public inbox for llvm@lists.linux.dev
 help / color / mirror / Atom feed
From: Heiko Carstens <hca@linux.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: kernel test robot <lkp@intel.com>, Marco Elver <elver@google.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 12:46:08 +0100	[thread overview]
Message-ID: <20260107114608.10536C6a-hca@linux.ibm.com> (raw)
In-Reply-To: <20260105153520.GV3707891@noisy.programming.kicks-ass.net>

On Mon, Jan 05, 2026 at 04:35:20PM +0100, Peter Zijlstra wrote:
> > commit: ee771bab5add646af678f7a40b6272c21a0964d7 [34/39] stackdepot: Enable context analysis
> > All warnings (new ones prefixed by >>, old ones prefixed by <<):
> > 
> > >> WARNING: modpost: EXPORT symbol "stack_depot_save_flags" [vmlinux] version generation failed, symbol will not be versioned.
> > Is "stack_depot_save_flags" prototyped in <asm/asm-prototypes.h>?
> > >> WARNING: modpost: EXPORT symbol "stack_depot_save" [vmlinux] version generation failed, symbol will not be versioned.
> > Is "stack_depot_save" prototyped in <asm/asm-prototypes.h>?
> 
> Heiko, I'm seeing these warnings, and I can reproduce in a local build.
> But I have to note that its just one more of an already existing string
> of similar failures.
> 
> I don't see anything like this on x86, not have I had robot reports for
> other architectures. As such, I'm considering this a pre-existing s390
> issue.
> 
> Please let me know if this is something you want me to look at
> nevertheless.

Sorry, to be more precise: I haven't seen anything like this before on s390.
All other occurences are also new and come with EXPORT_SYMBOL statements
within files where context analysis has been enabled.

When enabling CONFIG_MODVERSIONS I see this also for x86 builds.

I assume you cannot see this error pattern for s390 builds with
context analysis disabled?

  parent reply	other threads:[~2026-01-07 11:46 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 [this message]
2026-01-07 20:45     ` Nathan Chancellor
2026-01-07 22:35       ` Marco Elver
2026-01-07 22:56         ` Nathan Chancellor
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=20260107114608.10536C6a-hca@linux.ibm.com \
    --to=hca@linux.ibm.com \
    --cc=elver@google.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