Hello,
syzbot found the following issue on:
HEAD commit: 42616e0f09fb Linux 6.1.15
git tree: linux-6.1.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=16f99d92c80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=690b9ff41783cd73
dashboard link:
https://syzkaller.appspot.com/bug?extid=2f9f34d8ac9500d5fa13
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/db869f2ed2bd/disk-42616e0f.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/37951bbe5829/vmlinux-42616e0f.xz
kernel image:
https://storage.googleapis.com/syzbot-assets/23aa1a75ce0f/bzImage-42616e0f.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+2f9f34...@syzkaller.appspotmail.com
get_vaddr_frames() cannot follow VM_IO mapping
WARNING: CPU: 1 PID: 5191 at drivers/media/common/videobuf2/frame_vector.c:59 get_vaddr_frames+0x1db/0x220 drivers/media/common/videobuf2/frame_vector.c:59
Modules linked in:
CPU: 1 PID: 5191 Comm: syz-executor.1 Not tainted 6.1.15-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
RIP: 0010:get_vaddr_frames+0x1db/0x220 drivers/media/common/videobuf2/frame_vector.c:59
Code: 8c 1a ff ff ff 4c 89 e7 e8 82 85 d2 fa e9 0d ff ff ff e8 48 7a 7c fa c6 05 10 e1 30 07 01 48 c7 c7 80 8f a7 8b e8 65 dc 44 fa <0f> 0b e9 4a ff ff ff 44 89 e1 80 e1 07 80 c1 03 38 c1 0f 8c 1e ff
RSP: 0018:ffffc9000503f4a8 EFLAGS: 00010246
RAX: 247ba05aaa5f7400 RBX: 1ffff92002a00000 RCX: 0000000000040000
RDX: ffffc900063a1000 RSI: 0000000000018134 RDI: 0000000000018135
RBP: 0000000000080000 R08: ffffffff816dec4c R09: fffff52000a07e4d
R10: 0000000000000000 R11: dffffc0000000001 R12: ffffc90015000004
R13: dffffc0000000000 R14: 0000000000000000 R15: 00000000fffffff2
FS: 00007f4eb204d700(0000) GS:ffff8880b9b00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fe9d85ad988 CR3: 000000004883a000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
vb2_create_framevec+0x4a/0xb0 drivers/media/common/videobuf2/videobuf2-memops.c:50
vb2_vmalloc_get_userptr+0xe7/0x400 drivers/media/common/videobuf2/videobuf2-vmalloc.c:88
__prepare_userptr drivers/media/common/videobuf2/videobuf2-core.c:1194 [inline]
__buf_prepare+0xc22/0x4460 drivers/media/common/videobuf2/videobuf2-core.c:1436
vb2_core_qbuf+0x2b4/0x1360 drivers/media/common/videobuf2/videobuf2-core.c:1738
vb2_qbuf+0x184/0x240 drivers/media/common/videobuf2/videobuf2-v4l2.c:816
v4l2_m2m_qbuf+0x1e0/0x7a0 drivers/media/v4l2-core/v4l2-mem2mem.c:773
__video_do_ioctl+0xa3a/0xe30 drivers/media/v4l2-core/v4l2-ioctl.c:3037
video_usercopy+0xa79/0x10c0 drivers/media/v4l2-core/v4l2-ioctl.c:3384
v4l2_ioctl+0x181/0x1d0 drivers/media/v4l2-core/v4l2-dev.c:364
vfs_ioctl fs/ioctl.c:51 [inline]
__do_sys_ioctl fs/ioctl.c:870 [inline]
__se_sys_ioctl+0xf1/0x160 fs/ioctl.c:856
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f4eb128c0f9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f4eb204d168 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00007f4eb13abf80 RCX: 00007f4eb128c0f9
RDX: 0000000020000180 RSI: 00000000c058560f RDI: 0000000000000003
RBP: 00007f4eb12e7ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007ffc474e4f9f R14: 00007f4eb204d300 R15: 0000000000022000
</TASK>
---
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.