KCSAN: data-race in can_send / can_send (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 659caaf6 Merge tag 'ceph-for-5.10-rc3' of git://github.com..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13852f92500000
kernel config: https://syzkaller.appspot.com/x/.config?x=76dfc991796328d4
dashboard link: https://syzkaller.appspot.com/bug?extid=add1dbcbe9d4ffe6bf3c
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project.git 913f6005669cfb590c99865a90bc51ed0983d09d)
CC: [da...@davemloft.net ku...@kernel.org linu...@vger.kernel.org linux-...@vger.kernel.org m...@pengutronix.de net...@vger.kernel.org sock...@hartkopp.net]

Unfortunately, I don't have any reproducer for this issue yet.

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+add1db...@syzkaller.appspotmail.com

vcan0: j1939_tp_rxtimer: 0x00000000f768a425: rx timeout, send abort
vcan0: j1939_xtp_rx_abort_one: 0x00000000f768a425: 0x00000: (3) A timeout occurred and this is the connection abort to close the session.
==================================================================
BUG: KCSAN: data-race in can_send / can_send

read-write to 0xffff888022adbf90 of 8 bytes by interrupt on cpu 0:
can_send+0x3fd/0x490 net/can/af_can.c:290
j1939_send_one+0x189/0x1b0 net/can/j1939/main.c:340
j1939_tp_tx_dat net/can/j1939/transport.c:623 [inline]
j1939_session_tx_dat net/can/j1939/transport.c:813 [inline]
j1939_xtp_txnext_transmiter net/can/j1939/transport.c:869 [inline]
j1939_tp_txtimer+0x147d/0x2ad0 net/can/j1939/transport.c:1117
__run_hrtimer+0x133/0x420 kernel/time/hrtimer.c:1519
__hrtimer_run_queues kernel/time/hrtimer.c:1583 [inline]
hrtimer_run_softirq+0x1c9/0x2a0 kernel/time/hrtimer.c:1600
__do_softirq+0x12c/0x2b1 kernel/softirq.c:298
run_ksoftirqd+0x13/0x20 kernel/softirq.c:653
smpboot_thread_fn+0x34f/0x520 kernel/smpboot.c:165
kthread+0x1fa/0x220 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296

read-write to 0xffff888022adbf90 of 8 bytes by interrupt on cpu 1:
can_send+0x3fd/0x490 net/can/af_can.c:290
j1939_send_one+0x189/0x1b0 net/can/j1939/main.c:340
j1939_tp_tx_dat net/can/j1939/transport.c:623 [inline]
j1939_session_tx_dat net/can/j1939/transport.c:813 [inline]
j1939_xtp_txnext_transmiter net/can/j1939/transport.c:869 [inline]
j1939_tp_txtimer+0x147d/0x2ad0 net/can/j1939/transport.c:1117
__run_hrtimer+0x133/0x420 kernel/time/hrtimer.c:1519
__hrtimer_run_queues kernel/time/hrtimer.c:1583 [inline]
hrtimer_run_softirq+0x1c9/0x2a0 kernel/time/hrtimer.c:1600
__do_softirq+0x12c/0x2b1 kernel/softirq.c:298
run_ksoftirqd+0x13/0x20 kernel/softirq.c:653
smpboot_thread_fn+0x34f/0x520 kernel/smpboot.c:165
kthread+0x1fa/0x220 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:296

Reported by Kernel Concurrency Sanitizer on:
CPU: 1 PID: 16 Comm: ksoftirqd/1 Not tainted 5.10.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
==================================================================


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzk...@googlegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.