Oliver Hartkopp 40ebaf7365 can: isotp: stop timeout monitoring when no first frame was sent ... [ Upstream commit d734970817 ] The first attempt to fix a the 'impossible' WARN_ON_ONCE(1) in isotp_tx_timer_handler() focussed on the identical CAN IDs created by the syzbot reproducer and lead to upstream fix/commit 3ea566422c ("can: isotp: sanitize CAN ID checks in isotp_bind()"). But this did not catch the root cause of the wrong tx.state in the tx_timer handler. In the isotp 'first frame' case a timeout monitoring needs to be started before the 'first frame' is send. But when this sending failed the timeout monitoring for this specific frame has to be disabled too. Otherwise the tx_timer is fired with the 'warn me' tx.state of ISOTP_IDLE. Fixes: e057dd3fc2 ("can: add ISO 15765-2:2016 transport protocol") Link: https://lore.kernel.org/all/20220405175112.2682-1-socketcan@hartkopp.net Reported-by: syzbot+2339c27f5c66c652843e@syzkaller.appspotmail.com Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de> Signed-off-by: Sasha Levin <sashal@kernel.org>		2022-04-27 14:38:54 +02:00
..
j1939	net-timestamp: convert sk->sk_tskey to atomic_t	2022-03-02 11:48:01 +01:00
af_can.c
af_can.h
bcm.c
gw.c
isotp.c	can: isotp: stop timeout monitoring when no first frame was sent	2022-04-27 14:38:54 +02:00
Kconfig
Makefile
proc.c
raw.c