Bug 219966 - modpost: EXPORT symbol "policy_has_boost_freq" [vmlinux] version generation failed, symbol will not be versioned.
Summary: modpost: EXPORT symbol "policy_has_boost_freq" [vmlinux] version generation f...
Status: NEW
Alias: None
Product: Power Management
Classification: Unclassified
Component: cpufreq (show other bugs)
Hardware: All Linux
: P3 normal
Assignee: linux-pm@vger.kernel.org
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-03-29 19:04 UTC by sander44
Modified: 2025-04-06 08:06 UTC (History)
2 users (show)

See Also:
Kernel Version: 6.14.0
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description sander44 2025-03-29 19:04:29 UTC
Hello Kernel Team,

I notice this:

...
WARNING: modpost: EXPORT symbol "policy_has_boost_freq" [vmlinux] version generation failed, symbol will not be versioned.
Is "policy_has_boost_freq" prototyped in <asm/asm-prototypes.h>?
...

Kernel: 6.14.0 mainline
Comment 1 Paul Menzel 2025-04-05 09:07:19 UTC
Thank you. I also get this, but I only with “6.15-rc0” and not with 6.14. In my case, I bisected [1] the issue to commit 6a367577153a (percpu/x86: 
enable strict percpu checks via named AS qualifiers) [2].


[1]: https://lore.kernel.org/lkml/eb3c109f-550f-44ce-b0a1-3837aef1d02a@molgen.mpg.de/T/#u
[2]: https://web.git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6a367577153acd9b432a5340fb10891eeb7e10f1
Comment 2 Uros Bizjak 2025-04-06 06:51:23 UTC
The patch at [1] fixes this issue. Actually, this warning is the
root cause of previous report [2] and is due to genksyms not
being prepared for new keywords.

So, either genksyms should be enhanced or a workaround [1] should be used.

[1] https://lore.kernel.org/lkml/20250404102535.705090-1-ubizjak@gmail.com/
[2] https://lore.kernel.org/lkml/81a25a60-de78-43fb-b56a-131151e1c035@molgen.mpg.de/
Comment 3 Paul Menzel 2025-04-06 08:06:50 UTC
Thank you. Indeed, the warnings are gone with your patch. Sorry, for not checking that before.

@sander44, could you please confirm.

Note You need to log in before you can comment on or make changes to this bug.