[moderation] [fs?] WARNING in dpm_sysfs_add (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 42dc814987c1 Merge tag 'media/v6.6-2' of git://git.kernel...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14dcdc82680000
kernel config: https://syzkaller.appspot.com/x/.config?x=6afd1052711e24b0
dashboard link: https://syzkaller.appspot.com/bug?extid=77ae78646bee8a004136
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
CC: [gre...@linuxfoundation.org linux-...@vger.kernel.org linux-...@vger.kernel.org raf...@kernel.org]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/530544666ea0/disk-42dc8149.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/a19006db85b9/vmlinux-42dc8149.xz
kernel image: https://storage.googleapis.com/syzbot-assets/6045b59e8e2f/bzImage-42dc8149.xz

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

sysfs group 'power' not found for kobject 'ueagle-atm!adi930.fw'
WARNING: CPU: 1 PID: 55 at fs/sysfs/group.c:282 sysfs_remove_group+0x12a/0x170 fs/sysfs/group.c:282
Modules linked in:
CPU: 1 PID: 55 Comm: kworker/1:2 Not tainted 6.6.0-rc2-syzkaller-00048-g42dc814987c1 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/04/2023
Workqueue: events request_firmware_work_func
RIP: 0010:sysfs_remove_group+0x12a/0x170 fs/sysfs/group.c:282
Code: 48 89 d9 49 8b 14 24 48 b8 00 00 00 00 00 fc ff df 48 c1 e9 03 80 3c 01 00 75 37 48 8b 33 48 c7 c7 40 54 a0 8a e8 86 87 37 ff <0f> 0b eb 98 e8 4d 0a c7 ff e9 01 ff ff ff 48 89 df e8 40 0a c7 ff
RSP: 0018:ffffc9000130f980 EFLAGS: 00010286
RAX: 0000000000000000 RBX: ffffffff8b1271e0 RCX: 0000000000000000
RDX: ffff888014efbb80 RSI: ffffffff814df146 RDI: 0000000000000001
RBP: 0000000000000000 R08: 0000000000000001 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000001 R12: ffff88803d9cb008
R13: ffffffff8b127780 R14: 1ffff92000261f3f R15: ffff88803d9cb050
FS: 0000000000000000(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f44dd80e000 CR3: 0000000034825000 CR4: 0000000000350ee0
Call Trace:
<TASK>
dpm_sysfs_add+0x1e6/0x280 drivers/base/power/sysfs.c:734
device_add+0x9db/0x1aa0 drivers/base/core.c:3584
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+0x2e2/0xb90 drivers/base/firmware_loader/fallback.c:234
_request_firmware+0xe5a/0x12a0 drivers/base/firmware_loader/main.c:909
request_firmware_work_func+0xeb/0x240 drivers/base/firmware_loader/main.c:1160
process_one_work+0x884/0x15c0 kernel/workqueue.c:2630
process_scheduled_works kernel/workqueue.c:2703 [inline]
worker_thread+0x8b9/0x1290 kernel/workqueue.c:2784
kthread+0x33c/0x440 kernel/kthread.c:388
ret_from_fork+0x45/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x11/0x20 arch/x86/entry/entry_64.S:304
</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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite bug's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the bug is a duplicate of another bug, 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.