[v5.15] WARNING in dpm_sysfs_add (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1c700860e8bc Linux 5.15.185
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=150795d4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=db74c56dea20051
dashboard link: https://syzkaller.appspot.com/bug?extid=79fdc552f795fc6febfb
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/98c9bcd8fb21/disk-1c700860.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/75eaa3b1c3f3/vmlinux-1c700860.xz
kernel image: https://storage.googleapis.com/syzbot-assets/ed251e9d15fe/bzImage-1c700860.xz

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

usb 8-1: Direct firmware load for ueagle-atm/eagleII.fw failed with error -2
usb 8-1: Falling back to sysfs fallback for: ueagle-atm/eagleII.fw
------------[ cut here ]------------
sysfs group 'power' not found for kobject 'ueagle-atm!eagleII.fw'
WARNING: CPU: 1 PID: 21 at fs/sysfs/group.c:281 sysfs_remove_group+0x174/0x290 fs/sysfs/group.c:279
Modules linked in:
CPU: 1 PID: 21 Comm: kworker/1:0 Not tainted 5.15.185-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+0x174/0x290 fs/sysfs/group.c:279
Code: 48 8b 1b 4c 89 f8 48 c1 e8 03 80 3c 28 00 74 08 4c 89 ff e8 ce d3 d0 ff 49 8b 17 48 c7 c7 00 a0 19 8a 48 89 de e8 7c 41 aa 07 <0f> 0b 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 96 5b 8b ff
RSP: 0018:ffffc90000db79d8 EFLAGS: 00010246
RAX: fb3822e56b7b2900 RBX: ffffffff8a7bb300 RCX: ffff88813fe61dc0
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: dffffc0000000000 R08: dffffc0000000000 R09: ffffed10172267a8
R10: ffffed10172267a8 R11: 1ffff110172267a7 R12: 1ffffffff14f7664
R13: 1ffff1100f259c3c R14: ffff88805b5d8e80 R15: ffff8880792ce008
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007feeac9baeb8 CR3: 000000002a644000 CR4: 00000000003506e0
DR0: ffffffffffffffff DR1: 0000000000000047 DR2: 0000000000000005
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
dpm_sysfs_add+0x1fe/0x270 drivers/base/power/sysfs.c:734
device_add+0x715/0xfb0 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+0x3e9/0xbc0 drivers/base/firmware_loader/fallback.c:659
_request_firmware+0xc86/0x12b0 drivers/base/firmware_loader/main.c:876
request_firmware_work_func+0xac/0x1b0 drivers/base/firmware_loader/main.c:1127
process_one_work+0x863/0x1000 kernel/workqueue.c:2310
worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
kthread+0x436/0x520 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.