[v6.1] WARNING in dpm_sysfs_add

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 0bc96de781b4 Linux 6.1.148
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1185d7a2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=5c8a5866886424a8
dashboard link: https://syzkaller.appspot.com/bug?extid=5f02e8f764f0060728f2
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/04c58ffc4a8a/disk-0bc96de7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/01cad248945e/vmlinux-0bc96de7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fc5395191c77/bzImage-0bc96de7.xz

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

usb 5-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: 5081 at fs/sysfs/group.c:280 sysfs_remove_group+0x174/0x290 fs/sysfs/group.c:278
Modules linked in:
CPU: 1 PID: 5081 Comm: kworker/1:14 Not tainted 6.1.148-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Workqueue: events request_firmware_work_func
RIP: 0010:sysfs_remove_group+0x174/0x290 fs/sysfs/group.c:278
Code: 48 8b 1b 4c 89 f8 48 c1 e8 03 80 3c 28 00 74 08 4c 89 ff e8 1e 02 cc ff 49 8b 17 48 c7 c7 a0 6a 9c 8a 48 89 de e8 ec 11 48 ff <0f> 0b 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 56 e5 7b ff
RSP: 0018:ffffc9001c90f8c8 EFLAGS: 00010246
RAX: b31311e222cf8000 RBX: ffffffff8b02fd00 RCX: ffff88807acabb80
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: dffffc0000000000 R08: dffffc0000000000 R09: fffff52003921ea9
R10: fffff52003921ea9 R11: 1ffff92003921ea8 R12: 1ffffffff1605fa4
R13: 1ffff11004eebe2a R14: ffff888059763740 R15: ffff88802775f008
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fd92aa6fe30 CR3: 000000002ef27000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
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:3654
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+0x2e5/0x930 drivers/base/firmware_loader/fallback.c:234
_request_firmware+0xcad/0x1290 drivers/base/firmware_loader/main.c:884
request_firmware_work_func+0xac/0x1b0 drivers/base/firmware_loader/main.c:1135
process_one_work+0x898/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1250 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</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]

syzbot has found a reproducer for the following issue on:

HEAD commit: 0bc96de781b4 Linux 6.1.148
git tree: linux-6.1.y

console output: https://syzkaller.appspot.com/x/log.txt?x=14798c42580000

kernel config: https://syzkaller.appspot.com/x/.config?x=5c8a5866886424a8
dashboard link: https://syzkaller.appspot.com/bug?extid=5f02e8f764f0060728f2
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1785aa34580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17ad3fa2580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/04c58ffc4a8a/disk-0bc96de7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/01cad248945e/vmlinux-0bc96de7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/fc5395191c77/bzImage-0bc96de7.xz

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

usb 1-1: Direct firmware load for ueagle-atm/eagleII.fw failed with error -2
usb 1-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: 0 PID: 7 at fs/sysfs/group.c:280 sysfs_remove_group+0x174/0x290 fs/sysfs/group.c:278
Modules linked in:
CPU: 0 PID: 7 Comm: kworker/0:0 Not tainted 6.1.148-syzkaller #0

Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Workqueue: events request_firmware_work_func
RIP: 0010:sysfs_remove_group+0x174/0x290 fs/sysfs/group.c:278
Code: 48 8b 1b 4c 89 f8 48 c1 e8 03 80 3c 28 00 74 08 4c 89 ff e8 1e 02 cc ff 49 8b 17 48 c7 c7 a0 6a 9c 8a 48 89 de e8 ec 11 48 ff <0f> 0b 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 56 e5 7b ff

RSP: 0018:ffffc900000c78c8 EFLAGS: 00010246
RAX: 7225459dee655d00 RBX: ffffffff8b02fd00 RCX: ffff88813fe83b80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002
RBP: dffffc0000000000 R08: dffffc0000000000 R09: fffff52000018eb9
R10: fffff52000018eb9 R11: 1ffff92000018eb8 R12: 1ffffffff1605fa4
R13: 1ffff1100d24a42a R14: ffff88807d942570 R15: ffff888069252008
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000

CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 000000c006a8c000 CR3: 000000007e9ae000 CR4: 00000000003506f0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
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:3654
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+0x2e5/0x930 drivers/base/firmware_loader/fallback.c:234
_request_firmware+0xcad/0x1290 drivers/base/firmware_loader/main.c:884
request_firmware_work_func+0xac/0x1b0 drivers/base/firmware_loader/main.c:1135
process_one_work+0x898/0x1160 kernel/workqueue.c:2292
worker_thread+0xaa2/0x1250 kernel/workqueue.c:2439
kthread+0x29d/0x330 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>


---

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.