From: syzbot <syzbot+aa8212f63ea8ffaf3bfa@syzkaller.appspotmail.com>
To: bwinther@cisco.com, hverkuil-cisco@xs4all.nl, hverkuil@xs4all.nl,
keescook@chromium.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org, mchehab@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: BUG: unable to handle kernel paging request in tpg_fill_plane_buffer
Date: Tue, 25 Dec 2018 04:37:04 -0800 [thread overview]
Message-ID: <0000000000008ba970057dd7f809@google.com> (raw)
In-Reply-To: <0000000000005b7c64057ba003fb@google.com>
syzbot has found a reproducer for the following crash on:
HEAD commit: 6a1d293238c1 Add linux-next specific files for 20181224
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=17afe9c7400000
kernel config: https://syzkaller.appspot.com/x/.config?x=f9369d117d073843
dashboard link: https://syzkaller.appspot.com/bug?extid=aa8212f63ea8ffaf3bfa
compiler: gcc (GCC) 8.0.1 20180413 (experimental)
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11d0363b400000
IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+aa8212f63ea8ffaf3bfa@syzkaller.appspotmail.com
IPv6: ADDRCONF(NETDEV_UP): veth1: link is not ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth1: link becomes ready
IPv6: ADDRCONF(NETDEV_CHANGE): veth0: link becomes ready
8021q: adding VLAN 0 to HW filter on device team0
8021q: adding VLAN 0 to HW filter on device team0
BUG: unable to handle kernel paging request at ffffc900073cf340
#PF error: [WRITE]
PGD 1da93a067 P4D 1da93a067 PUD 1da93b067 PMD 1bad61067 PTE 0
Oops: 0002 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 10163 Comm: vivid-000-vid-c Not tainted
4.20.0-rc7-next-20181224 #188
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
RIP: 0010:memcpy_erms+0x6/0x10 arch/x86/lib/memcpy_64.S:55
Code: 90 90 90 90 eb 1e 0f 1f 00 48 89 f8 48 89 d1 48 c1 e9 03 83 e2 07 f3
48 a5 89 d1 f3 a4 c3 66 0f 1f 44 00 00 48 89 f8 48 89 d1 <f3> a4 c3 0f 1f
80 00 00 00 00 48 89 f8 48 83 fa 20 72 7e 40 38 fe
kobject: 'loop0' (00000000cecb8b38): kobject_uevent_env
RSP: 0018:ffff8881d455f4f8 EFLAGS: 00010246
RAX: ffffc900073cf340 RBX: 00000000000000f8 RCX: 00000000000000f8
RDX: 00000000000000f8 RSI: ffffc90001da3000 RDI: ffffc900073cf340
RBP: ffff8881d455f518 R08: fffff52000e79e87 R09: fffff52000e79e87
R10: fffff52000e79e86 R11: ffffc900073cf437 R12: ffffc900073cf340
R13: ffffc90001da3000 R14: dffffc0000000000 R15: ffff8881cb5a5e60
FS: 0000000000000000(0000) GS:ffff8881dac00000(0000) knlGS:0000000000000000
kobject: 'loop0' (00000000cecb8b38): fill_kobj_path: path
= '/devices/virtual/block/loop0'
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc900073cf340 CR3: 00000001c0ef1000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
memcpy include/linux/string.h:352 [inline]
tpg_fill_plane_pattern drivers/media/common/v4l2-tpg/v4l2-tpg-core.c:2382
[inline]
tpg_fill_plane_buffer+0x193f/0x44c0
drivers/media/common/v4l2-tpg/v4l2-tpg-core.c:2481
vivid_fillbuff+0x1c87/0x6620
drivers/media/platform/vivid/vivid-kthread-cap.c:467
vivid_thread_vid_cap_tick
drivers/media/platform/vivid/vivid-kthread-cap.c:718 [inline]
vivid_thread_vid_cap+0xf00/0x2ce0
drivers/media/platform/vivid/vivid-kthread-cap.c:836
kthread+0x35a/0x440 kernel/kthread.c:246
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:352
Modules linked in:
CR2: ffffc900073cf340
---[ end trace 5df23b5ab40374c3 ]---
RIP: 0010:memcpy_erms+0x6/0x10 arch/x86/lib/memcpy_64.S:55
Code: 90 90 90 90 eb 1e 0f 1f 00 48 89 f8 48 89 d1 48 c1 e9 03 83 e2 07 f3
48 a5 89 d1 f3 a4 c3 66 0f 1f 44 00 00 48 89 f8 48 89 d1 <f3> a4 c3 0f 1f
80 00 00 00 00 48 89 f8 48 83 fa 20 72 7e 40 38 fe
RSP: 0018:ffff8881d455f4f8 EFLAGS: 00010246
RAX: ffffc900073cf340 RBX: 00000000000000f8 RCX: 00000000000000f8
RDX: 00000000000000f8 RSI: ffffc90001da3000 RDI: ffffc900073cf340
RBP: ffff8881d455f518 R08: fffff52000e79e87 R09: fffff52000e79e87
R10: fffff52000e79e86 R11: ffffc900073cf437 R12: ffffc900073cf340
R13: ffffc90001da3000 R14: dffffc0000000000 R15: ffff8881cb5a5e60
FS: 0000000000000000(0000) GS:ffff8881dac00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc900073cf340 CR3: 00000001c0ef1000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
next prev parent reply other threads:[~2018-12-25 12:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 7:01 BUG: unable to handle kernel paging request in tpg_fill_plane_buffer syzbot
2018-12-25 12:37 ` syzbot [this message]
2019-04-10 4:44 ` 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=0000000000008ba970057dd7f809@google.com \
--to=syzbot+aa8212f63ea8ffaf3bfa@syzkaller.appspotmail.com \
--cc=bwinther@cisco.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=hverkuil@xs4all.nl \
--cc=keescook@chromium.org \
--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 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.