powerpc: Export mmu_feature_keys[] as non-GPL
PATCH 1/1 powerpc: Export mmu_feature_keys[] as non-GPL
When the mmu_feature_keys[] was introduced in the commit c12e6f24d413 ("powerpc: Add option to use jump label for mmu_has_feature()"), it is unlikely that it would be used either directly or indirectly in the out of tree modules. So we export it as GPL only. But with the evolution of the codes, especially the PPC_KUAP support, it may be indirectly referenced by some primitive macro or inline functions such as get_user() or __copy_from_user_inatomic(), this will make it impossible to build many non GPL modules (such as ZFS) on ppc architecture. Fix this by exposing the mmu_feature_keys[] to the non-GPL modules too.
--- arch/powerpc/kernel/cputable.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/powerpc/kernel/cputable.c +1 -1
@@ -2119,7 +2119,7 @@ void __init cpu_feature_keys_init(void)struct static_key_true mmu_feature_keys[NUM_MMU_FTR_KEYS ] = { [0 ...NUM_MMU_FTR_KEYS -1 ] =STATIC_KEY_TRUE_INIT }; -EXPORT_SYMBOL_GPL (mmu_feature_keys); +EXPORT_SYMBOL (mmu_feature_keys);void __init mmu_feature_keys_init (void ) {
Signature · 1 line
2.34.1
Michael Ellerman
AppliedQuoted 11 lines · Kevin Hao
When the mmu_feature_keys[] was introduced in the commit
c12e6f24d413("powerpc: Add option to use jump label formmu_has_feature()"), it is unlikely that it would be used either directly or indirectly in the out of tree modules. So we export it as GPL only. But with the evolution of the codes, especially thePPC_KUAPsupport, it may be indirectly referenced by some primitive macro or inline functions such asget_user()or__copy_from_user_inatomic(), this will make it impossible to build many non GPL modules (such as ZFS) on ppc architecture. Fix this by exposing the mmu_feature_keys[] to the non-GPL modules too.
Quoted 1 line
[...]
Applied to powerpc/next.
[1/1] powerpc: Export mmu_feature_keys[] as non-GPL
https://git.kernel.org/powerpc/c/d9e5c3e9e75162f845880535957b7fd0b4637d23
cheers