summaryrefslogtreecommitdiff
path: root/mm/page_alloc.c
diff options
context:
space:
mode:
authorOliver Hartkopp <socketcan@hartkopp.net>2016-11-23 14:33:25 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2016-12-02 09:10:33 +0100
commit374ff835e2b6ab9d6b21d28df39445a163759dd2 (patch)
treee9d1e33548023a75090c81f58fa12a4414b0f2f4 /mm/page_alloc.c
parent7ed8d94b99b31fbd6806a313b953a5090e1c26cf (diff)
can: bcm: fix support for CAN FD frames
commit 5499a6b22e5508b921c447757685b0a5e40a07ed upstream. Since commit 6f3b911d5f29b98 ("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> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'mm/page_alloc.c')
0 files changed, 0 insertions, 0 deletions