From: Oliver Hartkopp <socketcan@hartkopp.net>
To: linux-can@vger.kernel.org
Cc: Oliver Hartkopp <socketcan@hartkopp.net>
Subject: [PATCH 0/2] Fix two KCSAN issues
Date: Wed, 20 May 2026 14:14:48 +0200 [thread overview]
Message-ID: <20260520121450.27964-1-socketcan@hartkopp.net> (raw)
Patch 1 supersedes the "add locking when updating filter and timer values"
https://patchwork.kernel.org/project/linux-can/patch/20260219-bcm_spin_lock_init-v3-2-c61026740d7b@hartkopp.net/
where the readers in softirq/timer context have not been addressed
correctly and some comment was insufficient.
Patch 2 fixed an issue that has been detected by KCSAN when I was testing
patch 1 ;-)
Oliver Hartkopp (2):
can: bcm: add locking when updating filter and timer values
can: bcm: use atomic access in receive statistics
net/can/bcm.c | 88 ++++++++++++++++++++++++++++++++++++++++-----------
1 file changed, 69 insertions(+), 19 deletions(-)
--
2.53.0
next reply other threads:[~2026-05-20 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 12:14 Oliver Hartkopp [this message]
2026-05-20 12:14 ` [PATCH 1/2] can: bcm: add locking when updating filter and timer values Oliver Hartkopp
2026-05-20 12:14 ` [PATCH 2/2] can: bcm: use atomic access in receive statistics 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=20260520121450.27964-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