From: Marc Kleine-Budde <mkl@pengutronix.de>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, linux-can@vger.kernel.org,
kernel@pengutronix.de
Subject: [PATCH net-next 0/11] pull-request: can-next 2026-10-22
Date: Thu, 22 Oct 2026 01:07:47 +0200 [thread overview]
Message-ID: <20261021231130.2085690-1-mkl@pengutronix.de> (raw)
Hello netdev-team,
this is a pull request of 11 patches for net-next/main and obsoletes
pull-request: linux-can-next-for-7.4-20261021.
The first patch is by Vincent Mailhol and drops CAN-XL frames on non
CAN-XL devices.
A patch by Sang-Heon Jeon removes a redundant NULL check before
netdev_hold() in the CAN RAW protocol.
A patch by Kaixuan Li for the CAN ISOTP protocol improves the check
for the correct CAN CC/FD frames.
The next 3 patches are by Cunhao Lu and make CAN skb freeing safe in
any context in several CAN helper functions.
A series by Oliver Hartkopp et al fixes several problems in the CAN
net-layer:
3 patches target the CAN procfs: A patch by Runyu Xiao resets the CAN
pkg_stats using atomics, a patch by Oliver Hartkopp fixes the stats
calculation after a statistics reset. Followed by a patch to remove
kernel pointers from the output.
The last 2 patches are by Oliver Hartkopp as well, they convert the
unreliable ARPHRD_CAN type check to the robust can_get_ml_priv() and
protect the CAN receive lists with a per-device lock.
regards,
Marc
---
The following changes since commit 7dca8514c51ea5219daf7f28bc1a0536b907e611:
Merge branch 'vsock-so_inq-for-stream-sockets' (2026-10-21 11:58:24 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/mkl/linux-can-next.git tags/linux-can-next-for-7.4-20261022
for you to fetch changes up to 80cea9d8546f7533e9161c7f5b156ecd066647be:
Merge patch series "can: protect the receive lists with a per-device lock" (2026-10-22 01:04:07 +0200)
----------------------------------------------------------------
linux-can-next-for-7.4-20261022
----------------------------------------------------------------
Cunhao Lu (3):
can: skb: make echo skb freeing safe in any IRQ context
can: skb: make CAN skb allocation failure paths IRQ-safe
can: dev: can_put_echo_skb(): free skb on invalid echo index
Kaixuan Li (1):
can: isotp: check the frame type, not just the length
Marc Kleine-Budde (2):
Merge patch series "can: skb: make echo skb freeing safe in any IRQ context"
Merge patch series "can: protect the receive lists with a per-device lock"
Oliver Hartkopp (4):
can: proc: skip stats calculation after reset in can_stat_update()
can: proc: remove pointers from CAN specific proc output
can: replace ARPHRD_CAN type checks with can_get_ml_priv()
can: protect the receive lists with a per-device lock
Runyu Xiao (1):
can: proc: reset pkg_stats atomics individually
Sang-Heon Jeon (1):
can: raw: remove redundant NULL check before netdev_hold()
Vincent Mailhol (1):
can: dev: can_dropped_invalid_skb: drop CAN XL frames on non-CAN XL devices
Documentation/networking/can.rst | 16 ++--
drivers/net/can/dev/skb.c | 16 ++--
include/linux/can/can-ml.h | 3 +
include/linux/can/core.h | 2 +-
include/linux/can/dev.h | 2 +-
include/linux/can/skb.h | 4 +-
include/net/netns/can.h | 2 +-
net/can/af_can.c | 62 ++++++++-------
net/can/af_can.h | 2 +-
net/can/bcm.c | 64 ++++++---------
net/can/gw.c | 9 ++-
net/can/isotp.c | 73 +++++++++++------
net/can/j1939/main.c | 2 +-
net/can/proc.c | 95 +++++++++++++---------
net/can/raw.c | 166 +++++++++++++++++++++++++--------------
15 files changed, 305 insertions(+), 213 deletions(-)
next reply other threads:[~2026-10-21 23:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-21 23:07 Marc Kleine-Budde [this message]
2026-10-21 23:07 ` [PATCH net-next 01/11] can: dev: can_dropped_invalid_skb: drop CAN XL frames on non-CAN XL devices Marc Kleine-Budde
2026-10-21 23:18 ` netdev-bot+sinfo
2026-10-21 23:07 ` [PATCH net-next 02/11] can: skb: make echo skb freeing safe in any IRQ context Marc Kleine-Budde
2026-10-21 23:07 ` [PATCH net-next 03/11] can: raw: remove redundant NULL check before netdev_hold() Marc Kleine-Budde
2026-10-21 23:07 ` [PATCH net-next 04/11] can: skb: make CAN skb allocation failure paths IRQ-safe Marc Kleine-Budde
2026-10-21 23:07 ` [PATCH net-next 05/11] can: isotp: check the frame type, not just the length Marc Kleine-Budde
2026-10-21 23:07 ` [PATCH net-next 06/11] can: proc: reset pkg_stats atomics individually Marc Kleine-Budde
2026-10-21 23:07 ` [PATCH net-next 07/11] can: proc: skip stats calculation after reset in can_stat_update() Marc Kleine-Budde
2026-10-21 23:07 ` [PATCH net-next 08/11] can: proc: remove pointers from CAN specific proc output Marc Kleine-Budde
2026-10-21 23:07 ` [PATCH net-next 09/11] can: dev: can_put_echo_skb(): free skb on invalid echo index Marc Kleine-Budde
2026-10-21 23:07 ` [PATCH net-next 10/11] can: replace ARPHRD_CAN type checks with can_get_ml_priv() Marc Kleine-Budde
2026-10-21 23:07 ` [PATCH net-next 11/11] can: protect the receive lists with a per-device lock Marc Kleine-Budde
2026-10-22 8:37 ` [PATCH net-next 0/11] pull-request: can-next 2026-10-22 Paolo Abeni
2026-10-22 11:19 ` Oliver Hartkopp
2026-10-22 12:41 ` Marc Kleine-Budde
2026-10-22 14:07 ` Oliver Hartkopp
2026-10-22 12:47 ` Paolo Abeni
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=20261021231130.2085690-1-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--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