Repository files (latest commit first)

Filename	Latest commit message	Latest commit date
Oliver Hartkopp 516c436ff5 can: bcm/raw: fix msg_namelen values depending on CAN_REQUIRED_SIZE ... [ Upstream commit 9e9714742fb70467464359693a73b911a630226f ] Since commit f5223e9eee ("can: extend sockaddr_can to include j1939 members") the sockaddr_can has been extended in size and a new CAN_REQUIRED_SIZE macro has been introduced to calculate the protocol specific needed size. The ABI for the msg_name and msg_namelen has not been adapted to the new CAN_REQUIRED_SIZE macro for the other CAN protocols which leads to a problem when an existing binary reads the (increased) struct sockaddr_can in msg_name. Fixes: f5223e9eee ("can: extend sockaddr_can to include j1939 members") Reported-by: Richard Weinberger <richard@nod.at> Tested-by: Richard Weinberger <richard@nod.at> Acked-by: Kurt Van Dijck <dev.kurt@vandijck-laurijssen.be> Link: https://lore.kernel.org/linux-can/1135648123.112255.1616613706554.JavaMail.zimbra@nod.at/T/#t Link: https://lore.kernel.org/r/20210325125850.1620-1-socketcan@hartkopp.net Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de> Signed-off-by: Sasha Levin <sashal@kernel.org>		2021-04-14 08:24:14 +02:00
..
j1939	net: introduce CAN specific pointer in the struct net_device	2021-04-07 14:47:41 +02:00
af_can.c	net: introduce CAN specific pointer in the struct net_device	2021-04-07 14:47:41 +02:00
af_can.h
bcm.c	can: bcm/raw: fix msg_namelen values depending on CAN_REQUIRED_SIZE	2021-04-14 08:24:14 +02:00
gw.c
Kconfig
Makefile
proc.c	net: introduce CAN specific pointer in the struct net_device	2021-04-07 14:47:41 +02:00
raw.c	can: bcm/raw: fix msg_namelen values depending on CAN_REQUIRED_SIZE	2021-04-14 08:24:14 +02:00