Oliver Hartkopp b5f020f82a can: isotp: tx-path: zero initialize outgoing CAN frames ... Commit d4eb538e1f ("can: isotp: TX-path: ensure that CAN frame flags are initialized") ensured the TX flags to be properly set for outgoing CAN frames. In fact the root cause of the issue results from a missing initialization of outgoing CAN frames created by isotp. This is no problem on the CAN bus as the CAN driver only picks the correctly defined content from the struct can(fd)_frame. But when the outgoing frames are monitored (e.g. with candump) we potentially leak some bytes in the unused content of struct can(fd)_frame. Fixes: e057dd3fc2 ("can: add ISO 15765-2:2016 transport protocol") Cc: Marc Kleine-Budde <mkl@pengutronix.de> Link: https://lore.kernel.org/r/20210319100619.10858-1-socketcan@hartkopp.net Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>		2021-03-20 20:21:35 +01:00
..
j1939	net: introduce CAN specific pointer in the struct net_device	2021-02-24 14:32:15 -08:00
Kconfig	net: remove redundant 'depends on NET'	2021-01-27 17:04:12 -08:00
Makefile	…
af_can.c	net: introduce CAN specific pointer in the struct net_device	2021-02-24 14:32:15 -08:00
af_can.h	…
bcm.c	…
gw.c	can: gw: fix typo	2021-01-27 10:01:46 +01:00
isotp.c	can: isotp: tx-path: zero initialize outgoing CAN frames	2021-03-20 20:21:35 +01:00
proc.c	net: introduce CAN specific pointer in the struct net_device	2021-02-24 14:32:15 -08:00
raw.c	…