summaryrefslogtreecommitdiffstats
path: root/net/can/Makefile
diff options
context:
space:
mode:
authorOliver Hartkopp <socketcan@hartkopp.net>2015-06-26 11:58:19 +0200
committerMarc Kleine-Budde <mkl@pengutronix.de>2015-07-12 21:13:22 +0200
commitd3b58c47d330de8c29898fe9746f7530408f8a59 (patch)
tree7878e10d9185bab8f6b70a64dabd3851f739cecd /net/can/Makefile
parent2acb5c301edf39ab6d066687ce70da1166e4de9e (diff)
downloadop-kernel-dev-d3b58c47d330de8c29898fe9746f7530408f8a59.zip
op-kernel-dev-d3b58c47d330de8c29898fe9746f7530408f8a59.tar.gz
can: replace timestamp as unique skb attribute
Commit 514ac99c64b "can: fix multiple delivery of a single CAN frame for overlapping CAN filters" requires the skb->tstamp to be set to check for identical CAN skbs. Without timestamping to be required by user space applications this timestamp was not generated which lead to commit 36c01245eb8 "can: fix loss of CAN frames in raw_rcv" - which forces the timestamp to be set in all CAN related skbuffs by introducing several __net_timestamp() calls. This forces e.g. out of tree drivers which are not using alloc_can{,fd}_skb() to add __net_timestamp() after skbuff creation to prevent the frame loss fixed in mainline Linux. This patch removes the timestamp dependency and uses an atomic counter to create an unique identifier together with the skbuff pointer. Btw: the new skbcnt element introduced in struct can_skb_priv has to be initialized with zero in out-of-tree drivers which are not using alloc_can{,fd}_skb() too. Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net> Cc: linux-stable <stable@vger.kernel.org> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Diffstat (limited to 'net/can/Makefile')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud