netdev - [can-next v2] can: Kconfig: select CAN driver netlink infrastructure by default

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>] [day] [month] [year] [list]

Message-ID: <20251128165712.22306-1-socketcan@hartkopp.net>
Date: Fri, 28 Nov 2025 17:57:12 +0100
From: Oliver Hartkopp <socketcan@...tkopp.net>
To: linux-can@...r.kernel.org
Cc: netdev@...r.kernel.org,
	davem@...emloft.net,
	kuba@...nel.org,
	kernel@...gutronix.de,
	mkl@...gutronix.de,
	Oliver Hartkopp <socketcan@...tkopp.net>,
	Vincent Mailhol <mailhol@...nel.org>,
	kernel test robot <lkp@...el.com>
Subject: [can-next v2] can: Kconfig: select CAN driver netlink infrastructure by default

The CAN bus support enabled with CONFIG_CAN provides a socket-based
access to CAN interfaces. With the introduction of the latest CAN protocol
CAN XL additional configuration status information needs to be exposed to
the network layer than formerly provided by standard Linux network drivers.

This requires the CAN driver infrastructure to be selected by default.
As the CAN network layer can only operate on CAN interfaces anyway all
distributions and common default configs enable at least one CAN driver.

So selecting CONFIG_CAN_DEV and CONFIG_CAN_NETLINK when CONFIG_CAN is
selected by the user has no effect on established configurations but
solves potential build issues when CONFIG_CAN[_XXX]=y is set together with
CANFIG_CAN_DEV=m or CONFIG_CAN_NETLINK=n

Fixes: 1a620a723853 ("can: raw: instantly reject unsupported CAN frames")
Reported-by: Vincent Mailhol <mailhol@...nel.org>
Reported-by: kernel test robot <lkp@...el.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202511282325.uVQFRTkA-lkp@intel.com/
Suggested-by: Marc Kleine-Budde <mkl@...gutronix.de>
Signed-off-by: Oliver Hartkopp <socketcan@...tkopp.net>
---

v2: In fact CONFIG_CAN_NETLINK was missing too. Reported by kernel test robot.

---

 net/can/Kconfig | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/net/can/Kconfig b/net/can/Kconfig
index af64a6f76458..69cab889186c 100644
--- a/net/can/Kconfig
+++ b/net/can/Kconfig
@@ -3,10 +3,12 @@
 # Controller Area Network (CAN) network layer core configuration
 #
 
 menuconfig CAN
 	tristate "CAN bus subsystem support"
+	select CAN_DEV
+	select CAN_NETLINK
 	help
 	  Controller Area Network (CAN) is a slow (up to 1Mbit/s) serial
 	  communications protocol. Development of the CAN bus started in
 	  1983 at Robert Bosch GmbH, and the protocol was officially
 	  released in 1986. The CAN bus was originally mainly for automotive,
-- 
2.47.3