[v5.15] WARNING in bnep_session

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c52b9710c83d Linux 5.15.156
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10e5a46b180000
kernel config: https://syzkaller.appspot.com/x/.config?x=567b6ddc38438433
dashboard link: https://syzkaller.appspot.com/bug?extid=21d6e6c0b5d4ec36f406
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17364230980000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/1bd4b9969373/disk-c52b9710.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/10509e89bd25/vmlinux-c52b9710.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a623a4c52eb5/bzImage-c52b9710.xz

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

------------[ cut here ]------------
sysfs group 'power' not found for kobject 'bnep0'
WARNING: CPU: 1 PID: 4630 at fs/sysfs/group.c:281 sysfs_remove_group+0x179/0x2a0 fs/sysfs/group.c:279
Modules linked in:
CPU: 1 PID: 4630 Comm: kbnepd bnep0 Not tainted 5.15.156-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/27/2024
RIP: 0010:sysfs_remove_group+0x179/0x2a0 fs/sysfs/group.c:279
Code: 8b 36 4c 89 e0 48 c1 e8 03 80 3c 28 00 74 08 4c 89 e7 e8 9a b7 cc ff 49 8b 14 24 48 c7 c7 40 ba 99 8a 4c 89 f6 e8 f7 9a 4e ff <0f> 0b 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 b1 f2 82 ff
RSP: 0018:ffffc900040078e0 EFLAGS: 00010246
RAX: 55496f4760b07500 RBX: ffff88807baca638 RCX: ffff888023f49dc0
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: dffffc0000000000 R08: ffffffff8166862c R09: ffffed10173667a8
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88807baca608
R13: 1ffffffff15f53f4 R14: ffffffff8afa9f80 R15: ffff8880189f61d0
FS: 0000000000000000(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f9f491ab3b0 CR3: 000000001a750000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
device_del+0x2f1/0xbd0 drivers/base/core.c:3574
unregister_netdevice_many+0x13a6/0x18f0 net/core/dev.c:11120
unregister_netdevice_queue net/core/dev.c:11026 [inline]
unregister_netdevice include/linux/netdevice.h:3012 [inline]
unregister_netdev+0x19b/0x210 net/core/dev.c:11152
bnep_session+0x2ac0/0x2ca0 net/bluetooth/bnep/core.c:524
kthread+0x3f6/0x4f0 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:300
</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