summaryrefslogtreecommitdiffstats
path: root/drivers/net/can/bfin_can.c
diff options
context:
space:
mode:
authorOliver Hartkopp2009-12-12 05:13:21 +0100
committerDavid S. Miller2009-12-14 04:47:42 +0100
commitc7cd606f60e7679c7f9eee7010f02a6f000209c1 (patch)
tree31c19fd7617ede807757b0ae5c29d218587dc43f /drivers/net/can/bfin_can.c
parentnet: Fix userspace RTM_NEWLINK notifications. (diff)
downloadkernel-qcow2-linux-c7cd606f60e7679c7f9eee7010f02a6f000209c1.tar.gz
kernel-qcow2-linux-c7cd606f60e7679c7f9eee7010f02a6f000209c1.tar.xz
kernel-qcow2-linux-c7cd606f60e7679c7f9eee7010f02a6f000209c1.zip
can: Fix data length code handling in rx path
A valid CAN dataframe can have a data length code (DLC) of 0 .. 8 data bytes. When reading the CAN controllers register the 4-bit value may contain values from 0 .. 15 which may exceed the reserved space in the socket buffer! The ISO 11898-1 Chapter 8.4.2.3 (DLC field) says that register values > 8 should be reduced to 8 without any error reporting or frame drop. This patch introduces a new helper macro to cast a given 4-bit data length code (dlc) to __u8 and ensure the DLC value to be max. 8 bytes. The different handlings in the rx path of the CAN netdevice drivers are fixed. Signed-off-by: Oliver Hartkopp <oliver@hartkopp.net> Signed-off-by: Wolfgang Grandegger <wg@grandegger.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/net/can/bfin_can.c')
-rw-r--r--drivers/net/can/bfin_can.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/net/can/bfin_can.c b/drivers/net/can/bfin_can.c
index c7fc1de28173..0ec1524523cc 100644
--- a/drivers/net/can/bfin_can.c
+++ b/drivers/net/can/bfin_can.c
@@ -392,7 +392,7 @@ static void bfin_can_rx(struct net_device *dev, u16 isrc)
cf->can_id |= CAN_RTR_FLAG;
/* get data length code */
- cf->can_dlc = bfin_read16(&reg->chl[obj].dlc);
+ cf->can_dlc = get_can_dlc(bfin_read16(&reg->chl[obj].dlc) & 0xF);
/* get payload */
for (i = 0; i < 8; i += 2) {