From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
Oliver Hartkopp <socketcan@hartkopp.net>,
Marc Kleine-Budde <mkl@pengutronix.de>
Subject: Re: [PATCH 6.18.y 1/8] can: bcm: add locking when updating filter and timer values
Date: Sun, 26 Jul 2026 08:04:41 -0400 [thread overview]
Message-ID: <20260725192000.stable-0002@kernel.org> (raw)
In-Reply-To: <20260724102558.17056-1-socketcan@hartkopp.net>
> commit 749179c2e25b95d22499ed29096b3e02d6dfd2b4 upstream.
>
> KCSAN detected a simultaneous access to timer values that can be
> overwritten in bcm_rx_setup() when updating timer and filter content
> while bcm_rx_handler(), bcm_rx_timeout_handler() or bcm_rx_thr_handler()
> run concurrently on incoming CAN traffic.
Queued for 6.18, 6.12, 6.6, and 6.1, thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-07-26 12:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-20 15:13 FAILED: patch "[PATCH] can: bcm: add locking when updating filter and timer values" failed to apply to 6.18-stable tree gregkh
2026-07-24 8:41 ` [PATCH 1/8] can: bcm: add locking when updating filter and timer values Oliver Hartkopp
2026-07-24 10:25 ` [PATCH 6.18.y " Oliver Hartkopp
2026-07-24 10:25 ` [PATCH 6.18.y 2/8] can: bcm: fix CAN frame rx/tx statistics Oliver Hartkopp
2026-07-24 10:25 ` [PATCH 6.18.y 3/8] can: bcm: extend bcm_tx_lock usage for data and timer updates Oliver Hartkopp
2026-07-24 10:25 ` [PATCH 6.18.y 4/8] can: bcm: validate frame length in bcm_rx_setup() for RTR replies Oliver Hartkopp
2026-07-24 10:25 ` [PATCH 6.18.y 5/8] can: bcm: add missing device refcount for CAN filter removal Oliver Hartkopp
2026-07-24 10:25 ` [PATCH 6.18.y 6/8] can: bcm: fix stale rx/tx ops after device removal Oliver Hartkopp
2026-07-24 10:25 ` [PATCH 6.18.y 7/8] can: bcm: fix data race on rx_stamp/rx_ifindex in bcm_rx_handler() Oliver Hartkopp
2026-07-24 10:25 ` [PATCH 6.18.y 8/8] can: bcm: track a single source interface for ANYDEV timeout/throttle ops Oliver Hartkopp
2026-07-26 12:04 ` Sasha Levin [this message]
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=20260725192000.stable-0002@kernel.org \
--to=sashal@kernel.org \
--cc=mkl@pengutronix.de \
--cc=socketcan@hartkopp.net \
--cc=stable@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