[v6.6] WARNING in dpm_sysfs_add

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: dbcb8d8e4163 Linux 6.6.100
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=10863fd4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=293251cfa8d8100
dashboard link: https://syzkaller.appspot.com/bug?extid=dc2f8802d52a73a49d90
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d0b56817a2c3/disk-dbcb8d8e.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f0d646b2f7fa/vmlinux-dbcb8d8e.xz
kernel image: https://storage.googleapis.com/syzbot-assets/1e0b752a5011/bzImage-dbcb8d8e.xz

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

------------[ cut here ]------------
sysfs group 'power' not found for kobject 'ueagle-atm!eagleII.fw'
WARNING: CPU: 1 PID: 5878 at fs/sysfs/group.c:284 sysfs_remove_group+0x178/0x2a0 fs/sysfs/group.c:282
Modules linked in:
CPU: 1 PID: 5878 Comm: kworker/1:5 Not tainted 6.6.100-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
Workqueue: events request_firmware_work_func
RIP: 0010:sysfs_remove_group+0x178/0x2a0 fs/sysfs/group.c:282
Code: 48 8b 1b 4c 89 f8 48 c1 e8 03 80 3c 28 00 74 08 4c 89 ff e8 4a d2 c9 ff 49 8b 17 48 c7 c7 80 b3 ba 8a 48 89 de e8 88 01 3d ff <0f> 0b 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 22 8c 72 ff
RSP: 0018:ffffc90004a5f888 EFLAGS: 00010246
RAX: 6ab60c68a92b3500 RBX: ffffffff8b214da0 RCX: ffff888022e2da00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: dffffc0000000000 R08: ffffc90004a5f587 R09: 1ffff9200094beb0
R10: dffffc0000000000 R11: fffff5200094beb1 R12: 1ffffffff16429b8
R13: 1ffff11005e8362a R14: ffff8880303826c8 R15: ffff88802f41b008
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f4cf3583178 CR3: 0000000062370000 CR4: 00000000003506e0
Call Trace:
<TASK>
dpm_sysfs_add+0x202/0x270 drivers/base/power/sysfs.c:734
device_add+0x56a/0xc20 drivers/base/core.c:3643
fw_load_sysfs_fallback drivers/base/firmware_loader/fallback.c:82 [inline]
fw_load_from_user_helper drivers/base/firmware_loader/fallback.c:158 [inline]
firmware_fallback_sysfs+0x2e9/0x940 drivers/base/firmware_loader/fallback.c:234
_request_firmware+0xed9/0x1510 drivers/base/firmware_loader/main.c:936
request_firmware_work_func+0xb0/0x1b0 drivers/base/firmware_loader/main.c:1189
process_one_work kernel/workqueue.c:2634 [inline]
process_scheduled_works+0xa45/0x15b0 kernel/workqueue.c:2711
worker_thread+0xa55/0xfc0 kernel/workqueue.c:2792
kthread+0x2fa/0x390 kernel/kthread.c:388
ret_from_fork+0x48/0x80 arch/x86/kernel/process.c:152
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:293
</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.