Hello,
syzbot found the following issue on:
HEAD commit: 65afe34ac33d Linux 4.14.301
git tree: linux-4.14.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=17bb515b880000
kernel config:
https://syzkaller.appspot.com/x/.config?x=5dfc73e3d697d68d
dashboard link:
https://syzkaller.appspot.com/bug?extid=2dd0638c1cbaa8ad928b
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/cba1bf735bc1/disk-65afe34a.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/640415e88522/vmlinux-65afe34a.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/8c2d360d5af4/bzImage-65afe34a.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+2dd063...@syzkaller.appspotmail.com
get_vaddr_frames() cannot follow VM_IO mapping
overlayfs: fs on 'file0' does not support file handles, falling back to index=off.
overlayfs: fs on 'file0' does not support file handles, falling back to index=off.
------------[ cut here ]------------
WARNING: CPU: 0 PID: 11107 at mm/frame_vector.c:79 get_vaddr_frames.cold+0x18/0x1f mm/frame_vector.c:79
Kernel panic - not syncing: panic_on_warn set ...
CPU: 0 PID: 11107 Comm: syz-executor.3 Not tainted 4.14.301-syzkaller #0
overlayfs: fs on './file0' does not support file handles, falling back to index=off.
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
Call Trace:
__dump_stack lib/dump_stack.c:17 [inline]
dump_stack+0x1b2/0x281 lib/dump_stack.c:58
panic+0x1f9/0x42d kernel/panic.c:183
__warn.cold+0x20/0x44 kernel/panic.c:547
report_bug+0x208/0x250 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:177 [inline]
fixup_bug arch/x86/kernel/traps.c:172 [inline]
do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:967
RIP: 0010:get_vaddr_frames.cold+0x18/0x1f mm/frame_vector.c:79
RSP: 0018:ffff88805952f690 EFLAGS: 00010282
RAX: 000000000000002e RBX: ffff888059c45240 RCX: 0000000000000000
RDX: 00000000000009cc RSI: ffffffff814443b0 RDI: ffffed100b2a5ec8
RBP: 0000000000000096 R08: 000000000000002e R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 1ffff1100b2a5ed5
R13: 0000000020000000 R14: 0000000000000000 R15: ffff8880aaaff528
vb2_create_framevec+0x70/0xd0 drivers/media/v4l2-core/videobuf2-memops.c:56
vb2_vmalloc_get_userptr+0xcf/0x470 drivers/media/v4l2-core/videobuf2-vmalloc.c:90
__prepare_userptr+0x304/0x1040 drivers/media/v4l2-core/videobuf2-core.c:1033
__buf_prepare+0x3f6/0x4f0 drivers/media/v4l2-core/videobuf2-core.c:1258
vb2_core_qbuf+0x112/0xb60 drivers/media/v4l2-core/videobuf2-core.c:1386
vb2_qbuf+0x95/0xe0 drivers/media/v4l2-core/videobuf2-v4l2.c:570
v4l2_m2m_qbuf+0x66/0x150 drivers/media/v4l2-core/v4l2-mem2mem.c:403
v4l_qbuf drivers/media/v4l2-core/v4l2-ioctl.c:1881 [inline]
v4l_qbuf+0x88/0xb0 drivers/media/v4l2-core/v4l2-ioctl.c:1875
__video_do_ioctl+0x65b/0x6a0 drivers/media/v4l2-core/v4l2-ioctl.c:2738
video_usercopy+0xfd/0xe70 drivers/media/v4l2-core/v4l2-ioctl.c:2908
v4l2_ioctl+0x1bb/0x2f0 drivers/media/v4l2-core/v4l2-dev.c:360
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:500 [inline]
do_vfs_ioctl+0x75a/0xff0 fs/ioctl.c:684
SYSC_ioctl fs/ioctl.c:701 [inline]
SyS_ioctl+0x7f/0xb0 fs/ioctl.c:692
do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
entry_SYSCALL_64_after_hwframe+0x5e/0xd3
RIP: 0033:0x7f5f3487a0d9
RSP: 002b:00007f5f32dec168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f5f34999f80 RCX: 00007f5f3487a0d9
RDX: 0000000020000300 RSI: 00000000c058560f RDI: 0000000000000005
RBP: 00007f5f348d5ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fffb078076f R14: 00007f5f32dec300 R15: 0000000000022000
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
syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.