From: Chaosheng Qu <quchaosheng000406@163.com>
To: netdev-bot+sashiko@kernel.org
Cc: Robin van der Gracht <robin@protonic.nl>,
Oleksij Rempel <o.rempel@pengutronix.de>,
Oliver Hartkopp <socketcan@hartkopp.net>,
Marc Kleine-Budde <mkl@pengutronix.de>,
kernel@pengutronix.de, linux-can@vger.kernel.org,
linux-kernel@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH net v7 2/4] can: j1939: validate the EDPO packet number
Date: Fri, 13 Nov 2026 11:11:13 +0800 [thread overview]
Message-ID: <179453947398.30993.18128641012782298880@163.com> (raw)
In-Reply-To: <179452018139.488853.4180903963444412204@kernel.org>
Hi,
The Medium is right. j1939_session_cancel() only touches the rxtimer, so the
txtimer stayed armed on the aborting session. On the transmitter the
-ENOBUFS retries ran up to J1939_XTP_TX_RETRY_LIMIT and replaced session->err
with -ENETUNREACH; on the receiver they sent a CTS or an EOMA, and each of
those ends in j1939_tp_set_rxtimeout(session, 1250), which replaces the abort
timeout. v8 adds j1939_session_timers_cancel() before the abort, and v9 has
it.
Fixes: 9d71dd0c7009 and Cc: stable are in since v8.
Two things I got wrong in this patch, from your review of it on v9. Once
j1939_xtp_rx_cts_one() bounds the CTS, an out-of-range EDPO on the
transmitter side can only come from a frame this host did not build, since
J1939_ECU_LOCAL_SRC is set from the source address alone. ECTS_TOO_BIG blames
a responder CTS that was valid in that case, so the next version uses
BAD_EDPO_OFFSET for both roles. And the comment refers to "4/4", which means
nothing after merge; it will name j1939_xtp_rx_cts_one() instead.
Thanks,
Chaosheng
prev parent reply other threads:[~2026-11-13 3:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 1:34 [PATCH net v7 0/4] can: j1939: fix the abort timer and bound EDPO Chaosheng Qu
2026-11-08 1:34 ` [PATCH net v7 4/4] can: j1939: reject a CTS that names more packets than the message has Chaosheng Qu
2026-11-12 21:49 ` netdev-bot+sashiko
2026-11-13 3:11 ` Chaosheng Qu
2026-11-08 1:34 ` [PATCH net v7 1/4] can: j1939: arm the abort timer under the session list lock Chaosheng Qu
2026-11-12 21:49 ` netdev-bot+sashiko
2026-11-13 3:11 ` Chaosheng Qu
2026-11-08 1:34 ` [PATCH net v7 3/4] can: j1939: drop the message when the reassembled skb is gone Chaosheng Qu
2026-11-12 21:49 ` netdev-bot+sashiko
2026-11-13 3:11 ` Chaosheng Qu
2026-11-13 7:25 ` Oleksij Rempel
2026-11-08 1:34 ` [PATCH net v7 2/4] can: j1939: validate the EDPO packet number Chaosheng Qu
2026-11-12 21:49 ` netdev-bot+sashiko
2026-11-13 3:11 ` Chaosheng Qu [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=179453947398.30993.18128641012782298880@163.com \
--to=quchaosheng000406@163.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev-bot+sashiko@kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=robin@protonic.nl \
--cc=socketcan@hartkopp.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®