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/12] pull-request: can-next 2026-10-18
Date: Sun, 18 Oct 2026 18:41:36 +0200 [thread overview]
Message-ID: <20261018164417.1540449-1-mkl@pengutronix.de> (raw)
Hello netdev-team,
this is a pull request of 12 patches for net-next/main.
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.
Oliver Hartkopp's patch converts the unreliable ARPHRD_CAN type check
to the robust can_get_ml_priv().
A patch by Runyu Xiao for CAN proc resets the pkg_stats using atomics
individually. Oliver Hartkopp also contributes a patch for the CAN
proc to remove kernel pointers from the output.
A patch by Kaixuan Li for the CAN ISOTP protocol improves the check
for the correct CAN CC/FD frames.
Oliver Hartkopp series targets the CAN isotp, bcm and raw protocols
and fixes a use-after-free in the in isotp and bcm and converts the
raw protocol to the same locking scheme.
The next 3 patches are by Cunhao Lu and make CAN skb freeing safe in
any context in several CAN helper functions.
regards,
Marc
---
The following changes since commit 98c2ad4f5d805dbc1ea436a334ee59311806a48c:
Merge branch 'ipv4-remove-netns-argument-from-fib_table_lookup' (2026-10-16 18:52:36 -0700)
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-20261018
for you to fetch changes up to e9244db8f2baa66da454037e093524324ad174ee:
Merge patch series "can: skb: make echo skb freeing safe in any IRQ context" (2026-10-18 18:32:55 +0200)
----------------------------------------------------------------
linux-can-next-for-7.4-20261018
----------------------------------------------------------------
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: take rtnl_lock() before leaving the notifier list"
Merge patch series "can: skb: make echo skb freeing safe in any IRQ context"
Oliver Hartkopp (5):
can: replace ARPHRD_CAN type checks with can_get_ml_priv()
can: isotp: fix filter removal race between release and netns change
can: bcm: fix filter removal race between release and netns change
can: proc: remove pointers from CAN specific proc output
can: raw: take rtnl_lock() before leaving the notifier list
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/core.h | 2 +-
include/linux/can/dev.h | 2 +-
include/linux/can/skb.h | 4 +--
net/can/af_can.c | 21 ++++++-------
net/can/af_can.h | 2 +-
net/can/bcm.c | 68 +++++++++++++++++++---------------------
net/can/gw.c | 9 +++---
net/can/isotp.c | 34 +++++++++++++-------
net/can/j1939/main.c | 2 +-
net/can/proc.c | 65 ++++++++++++++++++++++++++------------
net/can/raw.c | 24 +++++++-------
13 files changed, 150 insertions(+), 115 deletions(-)
next reply other threads:[~2026-10-18 16:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 16:41 Marc Kleine-Budde [this message]
2026-10-18 16:41 ` [PATCH net-next 01/12] can: dev: can_dropped_invalid_skb: drop CAN XL frames on non-CAN XL devices Marc Kleine-Budde
2026-10-18 16:54 ` netdev-bot+sinfo
2026-10-18 16:41 ` [PATCH net-next 02/12] can: raw: remove redundant NULL check before netdev_hold() Marc Kleine-Budde
2026-10-18 16:41 ` [PATCH net-next 03/12] can: replace ARPHRD_CAN type checks with can_get_ml_priv() Marc Kleine-Budde
2026-10-18 16:41 ` [PATCH net-next 04/12] can: isotp: fix filter removal race between release and netns change Marc Kleine-Budde
2026-10-18 16:41 ` [PATCH net-next 05/12] can: proc: reset pkg_stats atomics individually Marc Kleine-Budde
2026-10-18 16:41 ` [PATCH net-next 06/12] can: bcm: fix filter removal race between release and netns change Marc Kleine-Budde
2026-10-18 18:37 ` Oliver Hartkopp
2026-10-19 8:30 ` Oliver Hartkopp
2026-10-19 9:18 ` Marc Kleine-Budde
2026-10-19 18:07 ` netdev-bot+sashiko
2026-10-19 19:20 ` Oliver Hartkopp
2026-10-18 16:41 ` [PATCH net-next 07/12] can: proc: remove pointers from CAN specific proc output Marc Kleine-Budde
2026-10-18 16:41 ` [PATCH net-next 08/12] can: raw: take rtnl_lock() before leaving the notifier list Marc Kleine-Budde
2026-10-18 16:41 ` [PATCH net-next 09/12] can: isotp: check the frame type, not just the length Marc Kleine-Budde
2026-10-18 16:41 ` [PATCH net-next 10/12] can: skb: make echo skb freeing safe in any IRQ context Marc Kleine-Budde
2026-10-19 18:07 ` netdev-bot+sashiko
2026-10-18 16:41 ` [PATCH net-next 11/12] can: skb: make CAN skb allocation failure paths IRQ-safe Marc Kleine-Budde
2026-10-18 16:41 ` [PATCH net-next 12/12] can: dev: can_put_echo_skb(): free skb on invalid echo index Marc Kleine-Budde
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=20261018164417.1540449-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