netdev - Re: [PATCH 1/2] [v2] net: ethernet: ti-cpsw: fix linking built-in code to modules

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: <8663692f-528f-4d68-8c35-136e5f1244dc@intel.com>
Date: Wed, 17 Apr 2024 13:49:35 +0200
From: Alexander Lobakin <aleksander.lobakin@...el.com>
To: Arnd Bergmann <arnd@...nel.org>
CC: Jakub Kicinski <kuba@...nel.org>, Arnd Bergmann <arnd@...db.de>, "David S.
 Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>, "Paolo
 Abeni" <pabeni@...hat.com>, Siddharth Vadapalli <s-vadapalli@...com>, "Ravi
 Gunasekaran" <r-gunasekaran@...com>, Roger Quadros <rogerq@...nel.org>, "MD
 Danish Anwar" <danishanwar@...com>, Vignesh Raghavendra <vigneshr@...com>,
	Diogo Ivo <diogo.ivo@...mens.com>, Tanmay Patil <t-patil@...com>, "Simon
 Horman" <horms@...nel.org>, Ratheesh Kannoth <rkannoth@...vell.com>,
	"Grygorii Strashko" <grygorii.strashko@...com>, <netdev@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>, <linux-omap@...r.kernel.org>,
	<bpf@...r.kernel.org>
Subject: Re: [PATCH 1/2] [v2] net: ethernet: ti-cpsw: fix linking built-in
 code to modules

From: Arnd Bergmann <arnd@...nel.org>
Date: Wed, 17 Apr 2024 10:43:01 +0200

> From: Arnd Bergmann <arnd@...db.de>
> 
> There are six variants of the cpsw driver, sharing various parts of
> the code: davinci-emac, cpsw, cpsw-switchdev, netcp, netcp_ethss and
> am65-cpsw-nuss.

https://lore.kernel.org/all/20221119225650.1044591-10-alobakin@pm.me

:D

> 
> I noticed that this means some files can be linked into more than
> one loadable module, or even part of vmlinux but also linked into
> a loadable module, both of which mess up assumptions of the build
> system.

Thanks,
Olek