BUG: unable to handle kernel paging request in tpg_fill_plane_buffer

13 views
Skip to first unread message

syzbot

unread,
Aug 14, 2019, 8:24:06 PM8/14/19
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: 893af1c7 Linux 4.19.66
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=16a1eae2600000
kernel config: https://syzkaller.appspot.com/x/.config?x=d5fac5a8617b8643
dashboard link: https://syzkaller.appspot.com/bug?extid=ea604414a8a6dc515e27
compiler: gcc (GCC) 9.0.0 20181231 (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+ea6044...@syzkaller.appspotmail.com

BUG: unable to handle kernel paging request at ffffc9001425a000
PGD 12c256067 P4D 12c256067 PUD 21bc31067 PMD a4e58067 PTE 0
Oops: 0002 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 18635 Comm: vivid-001-vid-c Not tainted 4.19.66 #40
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS
Google 01/01/2011
kobject: 'loop3' (000000002cd2538d): kobject_uevent_env
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:ffff888059ae77f8 EFLAGS: 00010246
kobject: 'loop3' (000000002cd2538d): fill_kobj_path: path
= '/devices/virtual/block/loop3'
RAX: ffffc9001425a000 RBX: dffffc0000000000 RCX: 0000000000000280
RDX: 0000000000000280 RSI: ffffc90002172000 RDI: ffffc9001425a000
RBP: ffff888059ae7818 R08: fffff5200284b450 R09: 0000000000000000
R10: fffff5200284b44f R11: ffffc9001425a27f R12: 0000000000000280
R13: ffffc9001425a000 R14: ffffc90002172000 R15: ffff8882187d54d8
FS: 0000000000000000(0000) GS:ffff8880ae900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc9001425a000 CR3: 0000000092b61000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
memcpy include/linux/string.h:348 [inline]
tpg_fill_plane_pattern drivers/media/common/v4l2-tpg/v4l2-tpg-core.c:2365
[inline]
tpg_fill_plane_buffer+0x10f7/0x2f00
drivers/media/common/v4l2-tpg/v4l2-tpg-core.c:2446
vivid_fillbuff+0x1958/0x6420
drivers/media/platform/vivid/vivid-kthread-cap.c:473
vivid_thread_vid_cap_tick
drivers/media/platform/vivid/vivid-kthread-cap.c:707 [inline]
vivid_thread_vid_cap+0x9a7/0x20f0
drivers/media/platform/vivid/vivid-kthread-cap.c:805
kthread+0x354/0x420 kernel/kthread.c:246
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Modules linked in:
CR2: ffffc9001425a000
---[ end trace bdb8b28f0ce1d7a5 ]---
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:ffff888059ae77f8 EFLAGS: 00010246
RAX: ffffc9001425a000 RBX: dffffc0000000000 RCX: 0000000000000280
RDX: 0000000000000280 RSI: ffffc90002172000 RDI: ffffc9001425a000
RBP: ffff888059ae7818 R08: fffff5200284b450 R09: 0000000000000000
R10: fffff5200284b44f R11: ffffc9001425a27f R12: 0000000000000280
R13: ffffc9001425a000 R14: ffffc90002172000 R15: ffff8882187d54d8
FS: 0000000000000000(0000) GS:ffff8880ae900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffffc9001425a000 CR3: 0000000092b61000 CR4: 00000000001426e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
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#status for how to communicate with syzbot.

syzbot

unread,
Sep 11, 2020, 1:35:16 AM9/11/20
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages