[syzbot] [pm?] INFO: trying to register non-static key in netdev_unregister_kobject (2)

[syzbot <syzbot+70bd31b69512b90375b6@syzkaller.appspotmail.com>]

Hello,

syzbot found the following issue on:

HEAD commit:    157a4881225b Merge branch 'add-ethernet-dts-schema-for-qcs..
git tree:       net-next
console output: https://syzkaller.appspot.com/x/log.txt?x=108ca630580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=9a3b9ec43446307a
dashboard link: https://syzkaller.appspot.com/bug?extid=70bd31b69512b90375b6
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/b088f73cb031/disk-157a4881.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/dadddc2fd943/vmlinux-157a4881.xz
kernel image: https://storage.googleapis.com/syzbot-assets/941f3e9fcf4e/bzImage-157a4881.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+70bd31b69512b90375b6@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: 15994 Comm: kbnepd bnep0 Not tainted 6.12.0-rc4-syzkaller-01012-g157a4881225b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Call Trace:
 <TASK>
 __dump_stack lib/dump_stack.c:94 [inline]
 dump_stack_lvl+0x241/0x360 lib/dump_stack.c:120
 assign_lock_key+0x241/0x280 kernel/locking/lockdep.c:981
 register_lock_class+0x1cf/0x980 kernel/locking/lockdep.c:1295
 __lock_acquire+0xf0/0x2050 kernel/locking/lockdep.c:5077
 lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825
 __raw_spin_lock_irq include/linux/spinlock_api_smp.h:119 [inline]
 _raw_spin_lock_irq+0xd3/0x120 kernel/locking/spinlock.c:170
 spin_lock_irq include/linux/spinlock.h:376 [inline]
 pm_runtime_set_memalloc_noio+0x13d/0x260 drivers/base/power/runtime.c:228
 netdev_unregister_kobject+0x178/0x250 net/core/net-sysfs.c:2109
 unregister_netdevice_many_notify+0x1859/0x1da0 net/core/dev.c:11513
 unregister_netdevice_many net/core/dev.c:11541 [inline]
 unregister_netdevice_queue+0x303/0x370 net/core/dev.c:11413
 unregister_netdevice include/linux/netdevice.h:3175 [inline]
 unregister_netdev+0x1c/0x30 net/core/dev.c:11559
 bnep_session+0x2e0e/0x3000 net/bluetooth/bnep/core.c:525
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </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 syzkaller@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 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