From: syzbot <syzbot+95f2e2439b97575ec3c0@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
rafael@kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in firmware_fallback_sysfs
Date: Wed, 24 Mar 2021 21:04:19 -0700 [thread overview]
Message-ID: <00000000000084315305be5482b9@google.com> (raw)
In-Reply-To: <0000000000007ad39e05bcb1a38d@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 20f1b5f9 Add linux-next specific files for 20210324
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1506414ed00000
kernel config: https://syzkaller.appspot.com/x/.config?x=31aa577aa2dca78c
dashboard link: https://syzkaller.appspot.com/bug?extid=95f2e2439b97575ec3c0
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14e50426d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1388dfe6d00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+95f2e2439b97575ec3c0@syzkaller.appspotmail.com
sysfs group 'power' not found for kobject 'ueagle-atm!eagleI.fw'
WARNING: CPU: 1 PID: 36 at fs/sysfs/group.c:279 sysfs_remove_group+0x126/0x170 fs/sysfs/group.c:279
Modules linked in:
CPU: 1 PID: 36 Comm: kworker/1:1 Not tainted 5.12.0-rc4-next-20210324-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: events request_firmware_work_func
RIP: 0010:sysfs_remove_group+0x126/0x170 fs/sysfs/group.c:279
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 e0 7d 7c 89 e8 9d cc d9 06 <0f> 0b eb 98 e8 f1 23 c9 ff e9 01 ff ff ff 48 89 df e8 e4 23 c9 ff
RSP: 0018:ffffc90000e6faa0 EFLAGS: 00010282
RAX: 0000000000000000 RBX: ffffffff89da8900 RCX: 0000000000000000
RDX: ffff888011e01c80 RSI: ffffffff815c3fd5 RDI: fffff520001cdf46
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: ffffffff815bd77e R11: 0000000000000000 R12: ffff8880276ac008
R13: ffffffff89da8ea0 R14: ffff8880133e6878 R15: ffff8880133e68c0
FS: 0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f2c3971a0c8 CR3: 000000001cf2a000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
dpm_sysfs_remove+0x97/0xb0 drivers/base/power/sysfs.c:837
device_del+0x20c/0xd40 drivers/base/core.c:3398
fw_load_sysfs_fallback drivers/base/firmware_loader/fallback.c:543 [inline]
fw_load_from_user_helper drivers/base/firmware_loader/fallback.c:581 [inline]
firmware_fallback_sysfs+0x9ff/0xe20 drivers/base/firmware_loader/fallback.c:657
_request_firmware+0xa80/0xe80 drivers/base/firmware_loader/main.c:833
request_firmware_work_func+0xdd/0x230 drivers/base/firmware_loader/main.c:1079
process_one_work+0x98d/0x1600 kernel/workqueue.c:2275
worker_thread+0x64c/0x1120 kernel/workqueue.c:2421
kthread+0x3b1/0x4a0 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294
next prev parent reply other threads:[~2021-03-25 4:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 8:20 WARNING in firmware_fallback_sysfs syzbot
2021-03-25 4:04 ` syzbot [this message]
2023-11-06 17:09 ` [syzbot] syz-test syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=00000000000084315305be5482b9@google.com \
--to=syzbot+95f2e2439b97575ec3c0@syzkaller.appspotmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox