netdev - Re: [PATCH net-next] ethtool: untangle the linkmode and ethtool headers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20231020092429.3pitbl3s6x6aonss@skbuf>
Date: Fri, 20 Oct 2023 12:24:29 +0300
From: Vladimir Oltean <vladimir.oltean@....com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: davem@...emloft.net, netdev@...r.kernel.org, edumazet@...gle.com,
	pabeni@...hat.com, andrew@...n.ch, paul.greenwalt@...el.com,
	hkallweit1@...il.com, linux@...linux.org.uk, gal@...dia.com
Subject: Re: [PATCH net-next] ethtool: untangle the linkmode and ethtool
 headers

On Thu, Oct 19, 2023 at 08:28:15AM -0700, Jakub Kicinski wrote:
> +EXPORT_SYMBOL_GPL(ethtool_forced_speed_maps_init);

Is there a rule for EXPORT_SYMBOL() vs EXPORT_SYMBOL_GPL()? My rule of
thumb was that symbols used by drivers should get EXPORT_SYMBOL() for
maximum compatibility with their respective licenses, while symbols
exported for other core kernel modules should get EXPORT_SYMBOL_GPL().