From: syzbot <syzbot+8e740e8a74e295b37726@syzkaller.appspotmail.com>
To: hverkuil@xs4all.nl, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, mchehab@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: [syzbot] WARNING in vivid_cap_update_frame_period
Date: Wed, 17 Nov 2021 13:33:32 -0800 [thread overview]
Message-ID: <000000000000305e3b05d102cbc4@google.com> (raw)
Hello,
syzbot found the following issue on:
HEAD commit: 66f4beaa6c1d Merge branch 'linus' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14f43b9eb00000
kernel config: https://syzkaller.appspot.com/x/.config?x=a262045c4c15a9e0
dashboard link: https://syzkaller.appspot.com/bug?extid=8e740e8a74e295b37726
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+8e740e8a74e295b37726@syzkaller.appspotmail.com
------------[ cut here ]------------
WARNING: CPU: 1 PID: 29933 at drivers/media/test-drivers/vivid/vivid-kthread-cap.c:664 vivid_cap_update_frame_period+0x16d/0x1f0 drivers/media/test-drivers/vivid/vivid-kthread-cap.c:664
Modules linked in:
CPU: 1 PID: 29933 Comm: vivid-001-vid-c Not tainted 5.15.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:vivid_cap_update_frame_period+0x16d/0x1f0 drivers/media/test-drivers/vivid/vivid-kthread-cap.c:664
Code: 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 75 79 48 89 ab d8 a0 00 00 48 83 c4 08 5b 5d 41 5c 41 5d c3 e8 e3 bf 4d fb <0f> 0b 48 b8 00 00 00 00 00 fc ff df 4c 89 ea 48 c1 ea 03 0f b6 14
RSP: 0018:ffffc90017c37e48 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff8881489b0000 RCX: 0000000000000000
RDX: ffff88807d831d00 RSI: ffffffff862a068d RDI: 0000000000000003
RBP: 000000a336db2200 R08: 0000000000000000 R09: 0000000000000001
R10: ffffffff862a05a9 R11: 0000000000000000 R12: 0000000000000000
R13: ffff8881489b9344 R14: ffff8881489b0000 R15: ffff8881489b0000
FS: 0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000555556fb1708 CR3: 000000006ff99000 CR4: 00000000003526e0
Call Trace:
<TASK>
vivid_thread_vid_cap+0x1ab/0xaf0 drivers/media/test-drivers/vivid/vivid-kthread-cap.c:816
kthread+0x405/0x4f0 kernel/kthread.c:327
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 29933 Comm: vivid-001-vid-c Not tainted 5.15.0-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
<TASK>
__dump_stack lib/dump_stack.c:88 [inline]
dump_stack_lvl+0xcd/0x134 lib/dump_stack.c:106
panic+0x2b0/0x6dd kernel/panic.c:232
__warn.cold+0x35/0x44 kernel/panic.c:603
report_bug+0x1bd/0x210 lib/bug.c:199
handle_bug+0x3c/0x60 arch/x86/kernel/traps.c:239
exc_invalid_op+0x14/0x40 arch/x86/kernel/traps.c:259
asm_exc_invalid_op+0x12/0x20 arch/x86/include/asm/idtentry.h:566
RIP: 0010:vivid_cap_update_frame_period+0x16d/0x1f0 drivers/media/test-drivers/vivid/vivid-kthread-cap.c:664
Code: 00 00 00 fc ff df 48 89 fa 48 c1 ea 03 80 3c 02 00 75 79 48 89 ab d8 a0 00 00 48 83 c4 08 5b 5d 41 5c 41 5d c3 e8 e3 bf 4d fb <0f> 0b 48 b8 00 00 00 00 00 fc ff df 4c 89 ea 48 c1 ea 03 0f b6 14
RSP: 0018:ffffc90017c37e48 EFLAGS: 00010293
RAX: 0000000000000000 RBX: ffff8881489b0000 RCX: 0000000000000000
RDX: ffff88807d831d00 RSI: ffffffff862a068d RDI: 0000000000000003
RBP: 000000a336db2200 R08: 0000000000000000 R09: 0000000000000001
R10: ffffffff862a05a9 R11: 0000000000000000 R12: 0000000000000000
R13: ffff8881489b9344 R14: ffff8881489b0000 R15: ffff8881489b0000
vivid_thread_vid_cap+0x1ab/0xaf0 drivers/media/test-drivers/vivid/vivid-kthread-cap.c:816
kthread+0x405/0x4f0 kernel/kthread.c:327
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295
</TASK>
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
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.
reply other threads:[~2021-11-17 21:33 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=000000000000305e3b05d102cbc4@google.com \
--to=syzbot+8e740e8a74e295b37726@syzkaller.appspotmail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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
all inboxes | Powered by JetHome®