Oliver Hartkopp 5499a6b22e can: bcm: fix support for CAN FD frames ... Since commit 6f3b911d5f ("can: bcm: add support for CAN FD frames") the CAN broadcast manager supports CAN and CAN FD data frames. As these data frames are embedded in struct can[fd]_frames which have a different length the access to the provided array of CAN frames became dependend of op->cfsiz. By using a struct canfd_frame pointer for the array of CAN frames the new offset calculation based on op->cfsiz was accidently applied to CAN FD frame element lengths. This fix makes the pointer to the arrays of the different CAN frame types a void pointer so that the offset calculation in bytes accesses the correct CAN frame elements. Reference: http://marc.info/?l=linux-netdev&m=147980658909653 Reported-by: Andrey Konovalov <andreyknvl@google.com> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net> Tested-by: Andrey Konovalov <andreyknvl@google.com> Cc: linux-stable <stable@vger.kernel.org> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>		2016-11-23 15:22:18 +01:00
..
Kconfig	can: Kconfig: switch on all CAN protocolls by default	2013-01-26 16:58:58 +01:00
Makefile	can: build proc support only if CONFIG_PROC_FS is activated	2016-06-17 15:39:41 +02:00
af_can.c	can: only call can_stat_update with procfs	2016-06-23 11:23:49 +02:00
af_can.h	can: only call can_stat_update with procfs	2016-06-23 11:23:49 +02:00
bcm.c	can: bcm: fix support for CAN FD frames	2016-11-23 15:22:18 +01:00
gw.c	can: cangw: introduce optional uid to reference created routing jobs	2015-06-09 09:39:49 +02:00
proc.c	can: build proc support only if CONFIG_PROC_FS is activated	2016-06-17 15:39:41 +02:00
raw.c	sock: enable timestamping using control messages	2016-04-04 15:50:30 -04:00