summaryrefslogtreecommitdiffstats
path: root/net/can
diff options
context:
space:
mode:
authorOliver Hartkopp <socketcan@hartkopp.net>2023-06-07 09:27:08 +0200
committerMarc Kleine-Budde <mkl@pengutronix.de>2023-06-22 10:45:09 +0200
commite38910c0072b541a91954682c8b074a93e57c09b (patch)
treef05a5da6cdab0752206842f3374cbc2715ebe1b4 /net/can
parent7f4e09700bdc13ce9aafa279bc999051e9bcda35 (diff)
downloadlinux-e38910c0072b541a91954682c8b074a93e57c09b.tar.gz
linux-e38910c0072b541a91954682c8b074a93e57c09b.tar.bz2
linux-e38910c0072b541a91954682c8b074a93e57c09b.zip
can: isotp: isotp_sendmsg(): fix return error fix on TX path
With commit d674a8f123b4 ("can: isotp: isotp_sendmsg(): fix return error on FC timeout on TX path") the missing correct return value in the case of a protocol error was introduced. But the way the error value has been read and sent to the user space does not follow the common scheme to clear the error after reading which is provided by the sock_error() function. This leads to an error report at the following write() attempt although everything should be working. Fixes: d674a8f123b4 ("can: isotp: isotp_sendmsg(): fix return error on FC timeout on TX path") Reported-by: Carsten Schmidt <carsten.schmidt-achim@t-online.de> Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net> Link: https://lore.kernel.org/all/20230607072708.38809-1-socketcan@hartkopp.net Cc: stable@vger.kernel.org Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Diffstat (limited to 'net/can')
-rw-r--r--net/can/isotp.c5
1 files changed, 3 insertions, 2 deletions
diff --git a/net/can/isotp.c b/net/can/isotp.c
index 84f9aba02901..ca9d728d6d72 100644
--- a/net/can/isotp.c
+++ b/net/can/isotp.c
@@ -1112,8 +1112,9 @@ wait_free_buffer:
if (err)
goto err_event_drop;
- if (sk->sk_err)
- return -sk->sk_err;
+ err = sock_error(sk);
+ if (err)
+ return err;
}
return size;