From: Oliver Hartkopp <socketcan@hartkopp.net>
To: linux-can@vger.kernel.org, netdev@vger.kernel.org,
kuba@kernel.org, edumazet@google.com, mkl@pengutronix.de
Cc: Oliver Hartkopp <socketcan@hartkopp.net>
Subject: [NET 0/2] CAN fixes for 6.5-rc7
Date: Mon, 21 Aug 2023 16:45:45 +0200 [thread overview]
Message-ID: <20230821144547.6658-1-socketcan@hartkopp.net> (raw)
Hello Jakub,
as Marc is probably on vacation I send these two fixes directly to the netdev
mailing list to hopefully get them into the current 6.5 cycle.
The isotp fix removes an unnecessary check which leads to delays and/or a wrong
error notification.
The fix for the CAN_RAW socket solves the last issue that has been introduced
with commit ee8b94c8510c ("can: raw: fix receiver memory leak") in this
upstream cycle (detected by Eric Dumazet).
Best regards,
Oliver
Oliver Hartkopp (2):
can: isotp: fix support for transmission of SF without flow control
can: raw: add missing refcount for memory leak fix
net/can/isotp.c | 22 +++++++---------------
net/can/raw.c | 35 ++++++++++++++++++++++++++---------
2 files changed, 33 insertions(+), 24 deletions(-)
--
2.39.2
next reply other threads:[~2023-08-21 14:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-21 14:45 Oliver Hartkopp [this message]
2023-08-21 14:45 ` [NET 1/2] can: isotp: fix support for transmission of SF without flow control Oliver Hartkopp
2023-08-21 14:45 ` [NET 2/2] can: raw: add missing refcount for memory leak fix Oliver Hartkopp
2023-08-22 7:59 ` Simon Horman
2023-08-22 16:45 ` Oliver Hartkopp
2023-08-22 20:08 ` Simon Horman
2023-08-23 0:30 ` [NET 0/2] CAN fixes for 6.5-rc7 patchwork-bot+netdevbpf
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=20230821144547.6658-1-socketcan@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).