From: syzbot <syzbot+b064fbd5fc8b2cfae49d@syzkaller.appspotmail.com>
To: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
rafael@kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in fw_load_sysfs_fallback
Date: Sun, 11 Apr 2021 08:08:12 -0700 [thread overview]
Message-ID: <0000000000000c3f5405bfb3c458@google.com> (raw)
In-Reply-To: <00000000000020424005bf118296@google.com>
syzbot has found a reproducer for the following issue on:
HEAD commit: 52e44129 Merge branch 'for-5.12-fixes' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=17f1d196d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=f91155ccddaf919c
dashboard link: https://syzkaller.appspot.com/bug?extid=b064fbd5fc8b2cfae49d
compiler: Debian clang version 11.0.1-2
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12a536a6d00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11339dd9d00000
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+b064fbd5fc8b2cfae49d@syzkaller.appspotmail.com
------------[ cut here ]------------
sysfs group 'power' not found for kobject 'ueagle-atm!adi930.fw'
WARNING: CPU: 0 PID: 5 at fs/sysfs/group.c:281 sysfs_remove_group+0x16e/0x280 fs/sysfs/group.c:279
Modules linked in:
CPU: 0 PID: 5 Comm: kworker/0:0 Not tainted 5.12.0-rc6-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+0x16e/0x280 fs/sysfs/group.c:279
Code: 89 e0 48 c1 e8 03 42 80 3c 28 00 74 08 4c 89 e7 e8 37 92 cb ff 49 8b 14 24 48 c7 c7 40 1a c2 89 4c 89 f6 31 c0 e8 b2 87 56 ff <0f> 0b 5b 41 5c 41 5d 41 5e 41 5f 5d c3 e8 40 a3 87 ff 49 8d 5e 20
RSP: 0018:ffffc90000ca7a90 EFLAGS: 00010246
RAX: f97192423f200500 RBX: ffff8880351a4038 RCX: ffff888011528000
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: 1ffffffff1459c30 R08: ffffffff8160b932 R09: ffffed1017385fe8
R10: ffffed1017385fe8 R11: 0000000000000000 R12: ffff8880351a4008
R13: dffffc0000000000 R14: ffffffff8a2ce140 R15: ffff888035bbc3a0
FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007ffcb4541b47 CR3: 000000001d137000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
device_del+0x26a/0xa90 drivers/base/core.c:3398
fw_load_sysfs_fallback+0x53e/0x720 drivers/base/firmware_loader/fallback.c:543
fw_load_from_user_helper+0x242/0x320 drivers/base/firmware_loader/fallback.c:581
_request_firmware+0x2c5/0x4c0 drivers/base/firmware_loader/main.c:831
request_firmware_work_func+0xb8/0x1e0 drivers/base/firmware_loader/main.c:1077
process_one_work+0x789/0xfd0 kernel/workqueue.c:2275
worker_thread+0xac1/0x1300 kernel/workqueue.c:2421
kthread+0x39a/0x3c0 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294
prev parent reply other threads:[~2021-04-11 15:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 13:33 [syzbot] WARNING in fw_load_sysfs_fallback syzbot
2021-04-11 15:08 ` syzbot [this message]
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=0000000000000c3f5405bfb3c458@google.com \
--to=syzbot+b064fbd5fc8b2cfae49d@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.