Re: [peterz-queue:locking/core 34/39] WARNING: modpost: EXPORT symbol "stack_depot_save_flags" [vmlinux] version generation failed, symbol will not be versioned.

[Heiko Carstens <hca@linux.ibm.com>]

On Mon, Jan 05, 2026 at 04:35:20PM +0100, Peter Zijlstra wrote:
> On Mon, Dec 22, 2025 at 10:11:10PM +0800, kernel test robot wrote:
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git locking/core
> > head:   77b4ebc9e43b02f3c50dab48963d969964ea83ef
> > commit: ee771bab5add646af678f7a40b6272c21a0964d7 [34/39] stackdepot: Enable context analysis
> > config: s390-defconfig (https://download.01.org/0day-ci/archive/20251222/202512222219.F6EkVNmQ-lkp@intel.com/config)
> > compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 185f5fd5ce4c65116ca8cf6df467a682ef090499)
> > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251222/202512222219.F6EkVNmQ-lkp@intel.com/reproduce)
> > 
> > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > the same patch/commit), kindly add following tags
> > | Reported-by: kernel test robot <lkp@intel.com>
> > | Closes: https://lore.kernel.org/oe-kbuild-all/202512222219.F6EkVNmQ-lkp@intel.com/
> > 
> > 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.

This seems to be an architecture independent problem.
When I enable CONFIG_MODVERSIONS I see this on x86 too.