From: Oliver Hartkopp via B4 Relay <devnull+socketcan.hartkopp.net@kernel.org>
To: Marc Kleine-Budde <mkl@pengutronix.de>,
"David S. Miller" <davem@davemloft.net>,
Urs Thuermann <urs.thuermann@volkswagen.de>,
Vincent Mailhol <mailhol@kernel.org>
Cc: linux-can@vger.kernel.org, linux-kernel@vger.kernel.org,
Oliver Hartkopp <socketcan@hartkopp.net>,
syzbot+5b11eccc403dd1cea9f8@syzkaller.appspotmail.com,
syzbot+75e5e4ae00c3b4bb544e@syzkaller.appspotmail.com
Subject: [PATCH v3 0/3] can: bcm: add/fix locking for config updates at runtime
Date: Thu, 19 Feb 2026 17:51:16 +0100 [thread overview]
Message-ID: <20260219-bcm_spin_lock_init-v3-0-c61026740d7b@hartkopp.net> (raw)
Address three locking issues detected by KASAN and KCSAN.
The first patch fixes an unintialized spin_lock in the KASAN fix.
The second patch addresses the update of content in bcm_rx_setup().
The third patch adds a missing atomic conversion in can_rcv_filter().
Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
---
Changes in v3:
- Add a third patch that fixes a KCSAN issue that showed up while testing
patch 2 8-)
- Link to v2: https://patch.msgid.link/20260219-bcm_spin_lock_init-v2-0-694352bfca62@hartkopp.net
Changes in v2:
- Add a second patch addressing the KCSAN report
- Link to v1: https://patch.msgid.link/20260218-bcm_spin_lock_init-v1-1-592634c8a5b5@hartkopp.net
---
Oliver Hartkopp (3):
can: bcm: fix locking for bcm_op runtime updates
can: bcm: add locking when updating filter and timer values
can: statistics: add missing atomic access in hot path
net/can/af_can.c | 4 ++--
net/can/af_can.h | 2 +-
net/can/bcm.c | 40 +++++++++++++++++++++++++++++++++-------
3 files changed, 36 insertions(+), 10 deletions(-)
---
base-commit: 2961f841b025fb234860bac26dfb7fa7cb0fb122
change-id: 20260218-bcm_spin_lock_init-2518eb8d4501
Best regards,
--
Oliver Hartkopp <socketcan@hartkopp.net>
next reply other threads:[~2026-02-19 16:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 16:51 Oliver Hartkopp via B4 Relay [this message]
2026-02-19 16:51 ` [PATCH v3 1/3] can: bcm: fix locking for bcm_op runtime updates Oliver Hartkopp via B4 Relay
2026-02-19 16:51 ` [PATCH v3 2/3] can: bcm: add locking when updating filter and timer values Oliver Hartkopp via B4 Relay
2026-03-02 10:21 ` Marc Kleine-Budde
2026-03-23 9:42 ` Marc Kleine-Budde
2026-03-23 9:46 ` Oliver Hartkopp
2026-02-19 16:51 ` [PATCH v3 3/3] can: statistics: add missing atomic access in hot path Oliver Hartkopp via B4 Relay
2026-03-02 10:22 ` 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=20260219-bcm_spin_lock_init-v3-0-c61026740d7b@hartkopp.net \
--to=devnull+socketcan.hartkopp.net@kernel.org \
--cc=davem@davemloft.net \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--cc=socketcan@hartkopp.net \
--cc=syzbot+5b11eccc403dd1cea9f8@syzkaller.appspotmail.com \
--cc=syzbot+75e5e4ae00c3b4bb544e@syzkaller.appspotmail.com \
--cc=urs.thuermann@volkswagen.de \
/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
all inboxes | Powered by JetHome®