[syzbot] [can?] INFO: trying to register non-static key in bcm_can_tx

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: cee73b1e840c Merge tag 'riscv-for-linus-7.0-mw1' of git://..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=172d2c02580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f71c66df48515cc1
dashboard link: https://syzkaller.appspot.com/bug?extid=5b11eccc403dd1cea9f8
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11c8415a580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=12a2fa52580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/9e927e1d94c1/disk-cee73b1e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2203b2372c8f/vmlinux-cee73b1e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ab3f368371b6/bzImage-cee73b1e.xz

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

INFO: trying to register non-static key.
The code is fine but needs lockdep annotation, or maybe
you didn't initialize this object before use?
turning off the locking correctness validator.
CPU: 0 UID: 0 PID: 5983 Comm: syz.0.17 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/24/2026
Call Trace:
<IRQ>
__dump_stack lib/dump_stack.c:94 [inline]
dump_stack_lvl+0x100/0x190 lib/dump_stack.c:120
assign_lock_key kernel/locking/lockdep.c:984 [inline]
register_lock_class+0x549/0x560 kernel/locking/lockdep.c:1299
__lock_acquire+0x3cb/0x2630 kernel/locking/lockdep.c:5112
lock_acquire kernel/locking/lockdep.c:5868 [inline]
lock_acquire+0x17c/0x330 kernel/locking/lockdep.c:5825
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:150 [inline]
_raw_spin_lock_bh+0x33/0x40 kernel/locking/spinlock.c:178
spin_lock_bh include/linux/spinlock.h:347 [inline]
bcm_can_tx.part.0+0x79/0x890 net/can/bcm.c:305
bcm_can_tx net/can/bcm.c:301 [inline]
bcm_rx_handler+0x6fa/0x880 net/can/bcm.c:731
deliver net/can/af_can.c:575 [inline]
can_rcv_filter+0x2a4/0x900 net/can/af_can.c:609
can_receive+0x2cb/0x500 net/can/af_can.c:674
can_rcv+0x29e/0x300 net/can/af_can.c:699
__netif_receive_skb_one_core+0x1b2/0x1e0 net/core/dev.c:6149
__netif_receive_skb+0x1f/0x120 net/core/dev.c:6262
process_backlog+0x37a/0x1580 net/core/dev.c:6614
__napi_poll.constprop.0+0xaf/0x450 net/core/dev.c:7678
napi_poll net/core/dev.c:7741 [inline]
net_rx_action+0xa40/0xf20 net/core/dev.c:7893
handle_softirqs+0x1ea/0x910 kernel/softirq.c:622
do_softirq kernel/softirq.c:523 [inline]
do_softirq+0xac/0xe0 kernel/softirq.c:510
</IRQ>
<TASK>
__local_bh_enable_ip+0xf8/0x120 kernel/softirq.c:450
local_bh_enable include/linux/bottom_half.h:33 [inline]
rcu_read_unlock_bh include/linux/rcupdate.h:924 [inline]
__dev_queue_xmit+0x7f1/0x46f0 net/core/dev.c:4856
dev_queue_xmit include/linux/netdevice.h:3384 [inline]
can_send+0x5d7/0xbd0 net/can/af_can.c:279
raw_sendmsg+0xdf9/0x1480 net/can/raw.c:1000
sock_sendmsg_nosec net/socket.c:727 [inline]
__sock_sendmsg net/socket.c:742 [inline]
____sys_sendmsg+0xa54/0xc30 net/socket.c:2592
___sys_sendmsg+0x190/0x1e0 net/socket.c:2646
__sys_sendmsg+0x170/0x220 net/socket.c:2678
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x106/0xf80 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fab0c99bf79
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fff12c0b798 EFLAGS: 00000246 ORIG_RAX: 000000000000002e
RAX: ffffffffffffffda RBX: 00007fab0cc15fa0 RCX: 00007fab0c99bf79
RDX: 0000000020044850 RSI: 0000200000000240 RDI: 0000000000000003
RBP: 00007fab0ca327e0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fab0cc15fac R14: 00007fab0cc15fa0 R15: 00007fab0cc15fa0
</TASK>


---
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.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup