From: Oliver Hartkopp <socketcan@hartkopp.net>
To: linux-can@vger.kernel.org
Cc: Oliver Hartkopp <socketcan@hartkopp.net>
Subject: [PATCH v4 0/3] CAN netlayer fixes for stable
Date: Tue, 29 Sep 2026 17:41:22 +0200 [thread overview]
Message-ID: <20260929154125.3298-1-socketcan@hartkopp.net> (raw)
This patch set aggregates the open stable fixes for the CAN netlayer.
Patch 3 is new and addresses a RPS regression but it needs the other patches
as basis.
Changes in patch 3 only.
v2: We need a non-zero UID for the cfecho checks in isotp.c
So restore the former while (!(skb->hash)) statement
v3: omit the problematic use of skb->hash reported by sashiko bot
v4: address tc mirred or netem duplicate clones suggested by sashiko bot
Oliver Hartkopp (3):
can: remove CAN filters independent from namespace
can: convert unreliable ARPHRD_CAN type checks to robust can_get_ml_priv()
can: fix unique skb identifier regression under RPS
drivers/net/can/vxcan.c | 3 ++
include/linux/can/core.h | 3 +-
include/linux/can/skb.h | 4 +-
include/net/can.h | 2 +
net/can/af_can.c | 63 ++++++++++++++++-------
net/can/bcm.c | 107 +++++++++++++++++++++++++++++----------
net/can/gw.c | 10 ++--
net/can/isotp.c | 28 +++++-----
net/can/raw.c | 17 ++++---
9 files changed, 167 insertions(+), 70 deletions(-)
--
2.53.0
next reply other threads:[~2026-09-29 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 15:41 Oliver Hartkopp [this message]
2026-09-29 15:41 ` [PATCH v4 1/3] can: remove CAN filters independent from namespace Oliver Hartkopp
2026-10-03 6:00 ` netdev-bot+sashiko
2026-09-29 15:41 ` [PATCH v4 2/3] can: convert unreliable ARPHRD_CAN type checks to robust can_get_ml_priv() Oliver Hartkopp
2026-09-29 15:41 ` [PATCH v4 3/3] can: fix unique skb identifier regression under RPS Oliver Hartkopp
2026-09-29 16:09 ` sashiko-bot
2026-10-03 6:00 ` netdev-bot+sashiko
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=20260929154125.3298-1-socketcan@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=linux-can@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.