BUG: unable to handle kernel paging request in tpg_fill_plane_buffer

37 views
Skip to first unread message

syzbot

unread,
Nov 27, 2018, 2:01:05 AM11/27/18
to bwin...@cisco.com, hver...@xs4all.nl, kees...@chromium.org, linux-...@vger.kernel.org, linux...@vger.kernel.org, mch...@kernel.org, syzkall...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 6f8b52ba442c Merge tag 'hwmon-for-v4.20-rc5' of git://git...
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15fd354d400000
kernel config: https://syzkaller.appspot.com/x/.config?x=c94f9f0c0363db4b
dashboard link: https://syzkaller.appspot.com/bug?extid=aa8212f63ea8ffaf3bfa
compiler: gcc (GCC) 8.0.1 20180413 (experimental)

Unfortunately, I don't have any reproducer for this crash yet.

IMPORTANT: if you fix the bug, please add the following tag to the commit:
Reported-by: syzbot+aa8212...@syzkaller.appspotmail.com

BUG: unable to handle kernel paging request at ffffc90005b5c340
PGD 1da95a067 P4D 1da95a067 PUD 1da95b067 PMD 1c4863067 PTE 0
Oops: 0002 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 5439 Comm: vivid-000-vid-c Not tainted 4.20.0-rc4+ #130
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:54
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:ffff888150467518 EFLAGS: 00010246
RAX: ffffc90005b5c340 RBX: 0000000000000080 RCX: 0000000000000080
RDX: 0000000000000080 RSI: ffffc90001da3000 RDI: ffffc90005b5c340
RBP: ffff888150467538 R08: fffff52000b6b878 R09: fffff52000b6b868
R10: fffff52000b6b877 R11: ffffc90005b5c3bf R12: ffffc90005b5c340
R13: ffffc90001da3000 R14: dffffc0000000000 R15: ffff8881cb2c5e50
FS: 0000000000000000(0000) GS:ffff8881dae00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc90005b5c340 CR3: 00000001846a4000 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+0x1d0d/0x68e0
drivers/media/platform/vivid/vivid-kthread-cap.c:473
vivid_thread_vid_cap_tick
drivers/media/platform/vivid/vivid-kthread-cap.c:709 [inline]
vivid_thread_vid_cap+0xbc1/0x2650
drivers/media/platform/vivid/vivid-kthread-cap.c:813
kthread+0x35a/0x440 kernel/kthread.c:246
ret_from_fork+0x3a/0x50 arch/x86/entry/entry_64.S:352
Modules linked in:
CR2: ffffc90005b5c340
---[ end trace 22cabf1d47b26daf ]---
RIP: 0010:memcpy_erms+0x6/0x10 arch/x86/lib/memcpy_64.S:54
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:ffff888150467518 EFLAGS: 00010246
RAX: ffffc90005b5c340 RBX: 0000000000000080 RCX: 0000000000000080
RDX: 0000000000000080 RSI: ffffc90001da3000 RDI: ffffc90005b5c340
RBP: ffff888150467538 R08: fffff52000b6b878 R09: fffff52000b6b868
R10: fffff52000b6b877 R11: ffffc90005b5c3bf R12: ffffc90005b5c340
R13: ffffc90001da3000 R14: dffffc0000000000 R15: ffff8881cb2c5e50
FS: 0000000000000000(0000) GS:ffff8881dae00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc90005b5c340 CR3: 00000001846a4000 CR4: 00000000001406f0
kobject: 'loop0' (00000000664d120c): kobject_uevent_env
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
kobject: 'loop0' (00000000664d120c): fill_kobj_path: path
= '/devices/virtual/block/loop0'
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
This bug 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 syzk...@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#bug-status-tracking for how to communicate with
syzbot.

syzbot

unread,
Dec 25, 2018, 7:37:05 AM12/25/18
to bwin...@cisco.com, hverkui...@xs4all.nl, hver...@xs4all.nl, kees...@chromium.org, linux-...@vger.kernel.org, linux...@vger.kernel.org, mch...@kernel.org, syzkall...@googlegroups.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+aa8212...@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

syzbot

unread,
Apr 10, 2019, 12:44:01 AM4/10/19
to bwin...@cisco.com, hans.v...@cisco.com, helen...@collabora.com, hverkui...@xs4all.nl, hver...@xs4all.nl, kees...@chromium.org, linux-...@vger.kernel.org, linux...@vger.kernel.org, mch...@kernel.org, mch...@s-opensource.com, syzkall...@googlegroups.com
syzbot has bisected this bug to:

commit f2fe89061d79706eca5c47e4efdc09bbc171e74a
Author: Helen Koike <helen...@collabora.com>
Date: Fri Apr 7 17:55:19 2017 +0000

[media] vimc: Virtual Media Controller core, capture and sensor

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14b9542d200000
start commit: 6a1d2932 Add linux-next specific files for 20181224
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=16b9542d200000
console output: https://syzkaller.appspot.com/x/log.txt?x=12b9542d200000
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11d0363b400000

Reported-by: syzbot+aa8212...@syzkaller.appspotmail.com
Fixes: f2fe89061d79 ("[media] vimc: Virtual Media Controller core, capture
and sensor")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

syzbot

unread,
Dec 17, 2022, 10:07:37 PM12/17/22
to syzkall...@googlegroups.com
Auto-closing this bug as obsolete.
No recent activity, existing reproducers are no longer triggering the issue.
Reply all
Reply to author
Forward
0 new messages