From: syzbot <syzbot+8f06445357a052a92657@syzkaller.appspotmail.com>
To: dakr@redhat.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, mcgrof@kernel.org,
rafael@kernel.org, russ.weight@linux.dev,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] [kernel?] WARNING in firmware_fallback_sysfs (2)
Date: Fri, 09 Aug 2024 08:45:18 -0700 [thread overview]
Message-ID: <000000000000bce370061f4207cf@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: de9c2c66ad8e Linux 6.11-rc2
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14019861980000
kernel config: https://syzkaller.appspot.com/x/.config?x=e8a2eef9745ade09
dashboard link: https://syzkaller.appspot.com/bug?extid=8f06445357a052a92657
compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/2a5965e13719/disk-de9c2c66.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/52c0d9ae2edc/vmlinux-de9c2c66.xz
kernel image: https://storage.googleapis.com/syzbot-assets/3c8963098f5f/bzImage-de9c2c66.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8f06445357a052a92657@syzkaller.appspotmail.com
usb 1-1: Direct firmware load for v4l-pvrusb2-29xxx-01.fw failed with error -2
usb 1-1: Falling back to sysfs fallback for: v4l-pvrusb2-29xxx-01.fw
------------[ cut here ]------------
WARNING: CPU: 0 PID: 2036 at drivers/base/firmware_loader/fallback.c:148 fw_load_from_user_helper drivers/base/firmware_loader/fallback.c:148 [inline]
WARNING: CPU: 0 PID: 2036 at drivers/base/firmware_loader/fallback.c:148 firmware_fallback_sysfs+0x782/0x9e0 drivers/base/firmware_loader/fallback.c:238
Modules linked in:
CPU: 0 UID: 0 PID: 2036 Comm: pvrusb2-context Not tainted 6.11.0-rc2-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 06/27/2024
RIP: 0010:fw_load_from_user_helper drivers/base/firmware_loader/fallback.c:148 [inline]
RIP: 0010:firmware_fallback_sysfs+0x782/0x9e0 drivers/base/firmware_loader/fallback.c:238
Code: 1c 24 e9 4d fc ff ff e8 ec cb 9f fb c6 05 45 f0 0d 0a 01 48 c7 c7 80 83 86 8c e8 f9 1e bf 05 e9 72 fc ff ff e8 cf cb 9f fb 90 <0f> 0b 90 48 89 df 48 c7 c6 60 84 86 8c 4c 89 ea e8 29 85 c1 05 e9
RSP: 0018:ffffc90004daf730 EFLAGS: 00010293
RAX: ffffffff85f3ab21 RBX: ffff88805bb470a8 RCX: ffff8880258a8000
RDX: 0000000000000000 RSI: 00000000fffffff5 RDI: 0000000000000000
RBP: 000000000000003c R08: ffffffff85f3a530 R09: 1ffffffff26e5922
R10: dffffc0000000000 R11: fffffbfff26e5923 R12: 00000000fffffff5
R13: ffffffff8cddfb00 R14: 0000000000000001 R15: 0000000000001770
FS: 0000000000000000(0000) GS:ffff8880b9200000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020bc5000 CR3: 000000000e734000 CR4: 0000000000350ef0
Call Trace:
<TASK>
_request_firmware+0xcf5/0x12b0 drivers/base/firmware_loader/main.c:914
request_firmware+0x36/0x50 drivers/base/firmware_loader/main.c:963
pvr2_locate_firmware+0xb1/0x500 drivers/media/usb/pvrusb2/pvrusb2-hdw.c:1359
pvr2_upload_firmware1+0x1c6/0x950 drivers/media/usb/pvrusb2/pvrusb2-hdw.c:1426
pvr2_hdw_setup_low drivers/media/usb/pvrusb2/pvrusb2-hdw.c:2107 [inline]
pvr2_hdw_setup drivers/media/usb/pvrusb2/pvrusb2-hdw.c:2261 [inline]
pvr2_hdw_initialize+0x411/0x3d10 drivers/media/usb/pvrusb2/pvrusb2-hdw.c:2338
pvr2_context_check drivers/media/usb/pvrusb2/pvrusb2-context.c:111 [inline]
pvr2_context_thread_func+0x4b3/0xb50 drivers/media/usb/pvrusb2/pvrusb2-context.c:158
kthread+0x2f2/0x390 kernel/kthread.c:389
ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
</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 syzkaller@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
reply other threads:[~2024-08-09 15:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=000000000000bce370061f4207cf@google.com \
--to=syzbot+8f06445357a052a92657@syzkaller.appspotmail.com \
--cc=dakr@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=rafael@kernel.org \
--cc=russ.weight@linux.dev \
--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