UPSTREAM: can: statistics: use atomic access in hot path

[ Upstream commit 80b5f901 ]

In can_send() and can_receive() CAN messages and CAN filter matches are
counted to be visible in the CAN procfs files.

KCSAN detected a data race within can_send() when two CAN frames have
been generated by a timer event writing to the same CAN netdevice at the
same time. Use atomic operations to access the statistics in the hot path
to fix the KCSAN complaint.

Reported-by:  <syzbot+78ce4489b812515d5e4d@syzkaller.appspotmail.com>
Closes: https://lore.kernel.org/all/67cd717d.050a0220.e1a89.0006.GAE@google.com


Change-Id: Ia1b2b44418970aad7fff7472ad1f805a9c0bf096
Signed-off-by: Oliver Hartkopp <socketcan@hartkopp.net>
Reviewed-by: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
Link: https://patch.msgid.link/20250310143353.3242-1-socketcan@hartkopp.net


Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Signed-off-by: Sasha Levin <sashal@kernel.org>
(cherry picked from commit d840c84c)
Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>