summaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings
diff options
context:
space:
mode:
authorOliver Hartkopp <socketcan@hartkopp.net>2018-10-24 10:27:12 +0200
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2018-12-01 09:37:30 +0100
commitbf8295faed733debbe5625ec1a0c137f1170ac2f (patch)
treec7cd10d3d71e7e4096141490dd850b3041abac01 /Documentation/devicetree/bindings
parent04f985776f0428a39cc6a68be5c74c3cf2d8cf83 (diff)
downloadlinux-stable-bf8295faed733debbe5625ec1a0c137f1170ac2f.tar.gz
linux-stable-bf8295faed733debbe5625ec1a0c137f1170ac2f.tar.bz2
linux-stable-bf8295faed733debbe5625ec1a0c137f1170ac2f.zip
can: raw: check for CAN FD capable netdev in raw_sendmsg()
commit a43608fa77213ad5ac5f75994254b9f65d57cfa0 upstream. When the socket is CAN FD enabled it can handle CAN FD frame transmissions. Add an additional check in raw_sendmsg() as a CAN2.0 CAN driver (non CAN FD) should never see a CAN FD frame. Due to the commonly used can_dropped_invalid_skb() function the CAN 2.0 driver would drop that CAN FD frame anyway - but with this patch the user gets a proper -EINVAL return code. Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net> Cc: linux-stable <stable@vger.kernel.org> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'Documentation/devicetree/bindings')
0 files changed, 0 insertions, 0 deletions