[v5.15] WARNING in dpm_sysfs_add

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 7e89efd3ae1c Linux 5.15.164
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=13ecfbc9980000
kernel config: https://syzkaller.appspot.com/x/.config?x=ef3d6716c47442fa
dashboard link: https://syzkaller.appspot.com/bug?extid=d93f99ae06b8daf80c7c
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/39cf3e32ff98/disk-7e89efd3.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/5832802d8e4b/vmlinux-7e89efd3.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fe6dc074e0ff/bzImage-7e89efd3.xz

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

usb 2-1: Direct firmware load for ueagle-atm/adi930.fw failed with error -2
usb 2-1: Falling back to sysfs fallback for: ueagle-atm/adi930.fw
------------[ cut here ]------------
sysfs group 'power' not found for kobject 'ueagle-atm!adi930.fw'
WARNING: CPU: 0 PID: 4250 at fs/sysfs/group.c:281 sysfs_remove_group+0x179/0x2a0 fs/sysfs/group.c:279
Modules linked in:
CPU: 0 PID: 4250 Comm: kworker/0:15 Not tainted 5.15.164-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
Workqueue: events request_firmware_work_func
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 2a b1 cc ff 49 8b 14 24 48 c7 c7 c0 bc 99 8a 4c 89 f6 e8 c7 7f 4e ff <0f> 0b 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 21 dd 82 ff
RSP: 0018:ffffc90003437978 EFLAGS: 00010246
RAX: bcc4061fcba92000 RBX: ffff888063e00038 RCX: ffff888022ef9dc0
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: dffffc0000000000 R08: ffffffff8166892c R09: ffffed10173467a8
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888063e00008
R13: 1ffffffff15f5e9c R14: ffffffff8afaf4c0 R15: ffff88806370ed98
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4cfaa472d8 CR3: 0000000023c2f000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
dpm_sysfs_add+0x203/0x270 drivers/base/power/sysfs.c:734
device_add+0x702/0xfd0 drivers/base/core.c:3369
fw_load_sysfs_fallback drivers/base/firmware_loader/fallback.c:507 [inline]
fw_load_from_user_helper drivers/base/firmware_loader/fallback.c:583 [inline]
firmware_fallback_sysfs+0x3f0/0xc90 drivers/base/firmware_loader/fallback.c:659
_request_firmware+0xbb1/0x1200 drivers/base/firmware_loader/main.c:848
request_firmware_work_func+0x126/0x270 drivers/base/firmware_loader/main.c:1097
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2310
worker_thread+0xaca/0x1280 kernel/workqueue.c:2457
kthread+0x3f6/0x4f0 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</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 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

[syzbot]

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