[v6.6] WARNING in firmware_fallback_sysfs

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: c2603c511feb Linux 6.6.93
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=145d9e82580000
kernel config: https://syzkaller.appspot.com/x/.config?x=486bade17c8c30b9
dashboard link: https://syzkaller.appspot.com/bug?extid=86b0dea5aa810f02bf47
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/8754f950a6e7/disk-c2603c51.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/3b19332dbf63/vmlinux-c2603c51.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cb245e836038/bzImage-c2603c51.xz

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

------------[ cut here ]------------
sysfs group 'power' not found for kobject 'ueagle-atm!eagleII.fw'
WARNING: CPU: 1 PID: 14712 at fs/sysfs/group.c:284 sysfs_remove_group+0x178/0x2a0 fs/sysfs/group.c:282
Modules linked in:
CPU: 1 PID: 14712 Comm: kworker/1:0 Not tainted 6.6.93-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 ca d2 c9 ff 49 8b 17 48 c7 c7 40 bc ba 8a 48 89 de e8 b8 91 3b ff <0f> 0b 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 b2 2d 71 ff
RSP: 0018:ffffc9000c4a7800 EFLAGS: 00010246
RAX: 50fc9267d7c5e600 RBX: ffffffff8b2147e0 RCX: ffff88802b65da00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000002
RBP: dffffc0000000000 R08: ffff8880b8f28c13 R09: 1ffff110171e5182
R10: dffffc0000000000 R11: ffffed10171e5183 R12: 1ffffffff1642900
R13: 0000000000000001 R14: ffff88802d6a00f8 R15: ffff888024072008
FS: 0000000000000000(0000) GS:ffff8880b8f00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f31b3a937e8 CR3: 0000000031610000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
device_del+0x251/0x900 drivers/base/core.c:3847
fw_load_sysfs_fallback drivers/base/firmware_loader/fallback.c:120 [inline]
fw_load_from_user_helper drivers/base/firmware_loader/fallback.c:158 [inline]
firmware_fallback_sysfs+0x682/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]

syzbot has found a reproducer for the following issue on:

HEAD commit: 6282921b6825 Linux 6.6.94
git tree: linux-6.6.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1537b370580000
kernel config: https://syzkaller.appspot.com/x/.config?x=96da6b2210cda427

dashboard link: https://syzkaller.appspot.com/bug?extid=86b0dea5aa810f02bf47
compiler: Debian clang version 20.1.6 (++20250514063057+1e4d39e07757-1~exp1~20250514183223.118), Debian LLD 20.1.6

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=144a0b0c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10c02b0c580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/a3bf0d8e22b2/disk-6282921b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/d1d442f782d0/vmlinux-6282921b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/a8378f4b7e1b/bzImage-6282921b.xz

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

------------[ cut here ]------------
sysfs group 'power' not found for kobject 'ueagle-atm!eagleII.fw'

WARNING: CPU: 0 PID: 5774 at fs/sysfs/group.c:284 sysfs_remove_group+0x178/0x2a0 fs/sysfs/group.c:282
Modules linked in:
CPU: 0 PID: 5774 Comm: kworker/0:3 Not tainted 6.6.94-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 ea d0 c9 ff 49 8b 17 48 c7 c7 40 bc ba 8a 48 89 de e8 b8 8e 3b ff <0f> 0b 48 83 c4 08 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 a2 29 71 ff
RSP: 0018:ffffc90004497800 EFLAGS: 00010246
RAX: 83a4f13b36bc5600 RBX: ffffffff8b2148e0 RCX: ffff88802f9b1e00
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000002
RBP: dffffc0000000000 R08: ffffc90004497407 R09: 1ffff92000892e80
R10: dffffc0000000000 R11: fffff52000892e81 R12: 1ffffffff1642920
R13: 0000000000000001 R14: ffff88802f5b0ba0 R15: ffff8881472be008
FS: 0000000000000000(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000

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

CR2: 00007f4df4648280 CR3: 00000000315e3000 CR4: 00000000003506f0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
device_del+0x251/0x900 drivers/base/core.c:3847
fw_load_sysfs_fallback drivers/base/firmware_loader/fallback.c:120 [inline]
fw_load_from_user_helper drivers/base/firmware_loader/fallback.c:158 [inline]
firmware_fallback_sysfs+0x682/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>


---

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.