From: Oliver Hartkopp <socketcan@hartkopp.net>
To: linux-can@vger.kernel.org
Cc: Oliver Hartkopp <socketcan@hartkopp.net>
Subject: [PATCH 0/3] CAN netlayer fixes for stable
Date: Mon, 28 Sep 2026 18:59:24 +0200 [thread overview]
Message-ID: <20260928165927.31667-1-socketcan@hartkopp.net> (raw)
This patch set aggregates the open stable fixes for the CAN netlayer.
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
include/linux/can/core.h | 3 +-
include/linux/can/skb.h | 4 +-
include/net/can.h | 3 ++
net/can/af_can.c | 36 +++++++------
net/can/bcm.c | 107 +++++++++++++++++++++++++++++----------
net/can/gw.c | 10 ++--
net/can/isotp.c | 16 +++---
net/can/raw.c | 7 +--
8 files changed, 125 insertions(+), 61 deletions(-)
--
2.53.0
next reply other threads:[~2026-09-28 17:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 16:59 Oliver Hartkopp [this message]
2026-09-28 16:59 ` [PATCH 1/3] can: remove CAN filters independent from namespace Oliver Hartkopp
2026-09-28 16:59 ` [PATCH 2/3] can: convert unreliable ARPHRD_CAN type checks to robust can_get_ml_priv() Oliver Hartkopp
2026-09-28 16:59 ` [PATCH 3/3] can: fix unique skb identifier regression under RPS Oliver Hartkopp
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=20260928165927.31667-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox