linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* Symbol cpu_feature_keys should be exported to all modules on powerpc
@ 2023-02-28  8:18 王昊然
  2023-02-28  8:28 ` Greg KH
  0 siblings, 1 reply; 3+ messages in thread
From: 王昊然 @ 2023-02-28  8:18 UTC (permalink / raw)
  To: stable; +Cc: Kevin Hao, Paul Mackerras, linuxppc-dev

Just like symbol 'mmu_feature_keys'[1], 'cpu_feature_keys' was referenced
indirectly by many inline functions; any GPL-incompatible modules using such
a function will be potentially broken due to 'cpu_feature_keys' being
exported as GPL-only.

For example it still breaks ZFS, see
https://github.com/openzfs/zfs/issues/14545

[1]: https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20220329085709.4132729-1-haokexin@gmail.com/

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Symbol cpu_feature_keys should be exported to all modules on powerpc
  2023-02-28  8:18 Symbol cpu_feature_keys should be exported to all modules on powerpc 王昊然
@ 2023-02-28  8:28 ` Greg KH
       [not found]   ` <CAPge7yekNA633CiWbCftS5GRHTzYAMeraOmKKSMZL=5GdWzqfw@mail.gmail.com>
  0 siblings, 1 reply; 3+ messages in thread
From: Greg KH @ 2023-02-28  8:28 UTC (permalink / raw)
  To: 王昊然; +Cc: Kevin Hao, stable, Paul Mackerras, linuxppc-dev

On Tue, Feb 28, 2023 at 04:18:12PM +0800, 王昊然 wrote:
> Just like symbol 'mmu_feature_keys'[1], 'cpu_feature_keys' was referenced
> indirectly by many inline functions; any GPL-incompatible modules using such
> a function will be potentially broken due to 'cpu_feature_keys' being
> exported as GPL-only.
> 
> For example it still breaks ZFS, see
> https://github.com/openzfs/zfs/issues/14545
> 
> [1]: https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20220329085709.4132729-1-haokexin@gmail.com/

External modules are always on their own, sorry.  Especially ones that
are not released under the GPL.

good luck!

greg k-h

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Fwd: Symbol cpu_feature_keys should be exported to all modules on powerpc
       [not found]   ` <CAPge7yekNA633CiWbCftS5GRHTzYAMeraOmKKSMZL=5GdWzqfw@mail.gmail.com>
@ 2023-03-01 13:25     ` 王昊然
  0 siblings, 0 replies; 3+ messages in thread
From: 王昊然 @ 2023-03-01 13:25 UTC (permalink / raw)
  To: linuxppc-dev; +Cc: Kevin Hao, Paul Mackerras

---------- Forwarded message ----------
From: 王昊然 <msl0000023508@gmail.com>
Date: Tue, 28 Feb 2023 18:16:14 +0800
Subject: Re: Symbol cpu_feature_keys should be exported to all modules
on powerpc
To: Greg KH <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org

2023-02-28 16:28 GMT+08:00, Greg KH <gregkh@linuxfoundation.org>:
> On Tue, Feb 28, 2023 at 04:18:12PM +0800, 王昊然 wrote:
>> Just like symbol 'mmu_feature_keys'[1], 'cpu_feature_keys' was referenced
>> indirectly by many inline functions; any GPL-incompatible modules using
>> such
>> a function will be potentially broken due to 'cpu_feature_keys' being
>> exported as GPL-only.
>>
>> For example it still breaks ZFS, see
>> https://github.com/openzfs/zfs/issues/14545
>>
>> [1]:
>> https://patchwork.ozlabs.org/project/linuxppc-dev/patch/20220329085709.4132729-1-haokexin@gmail.com/
>
> External modules are always on their own, sorry.  Especially ones that
> are not released under the GPL.
>
> good luck!
>
> greg k-h
>

Some inline functions are just powerpc implementation of some generic KPIs,
such as flush_dcache_page, which indirectly references 'cpu_feature_keys' in
powerpc-specific code; this essentially makes 'flush_dcache_page' GPL-only in
Linux powerpc, but not in other architectures.

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2023-03-01 22:46 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-02-28  8:18 Symbol cpu_feature_keys should be exported to all modules on powerpc 王昊然
2023-02-28  8:28 ` Greg KH
     [not found]   ` <CAPge7yekNA633CiWbCftS5GRHTzYAMeraOmKKSMZL=5GdWzqfw@mail.gmail.com>
2023-03-01 13:25     ` Fwd: " 王昊然

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).