Hello,
syzbot found the following issue on:
HEAD commit: f6d5cb9e Linux 4.19.142
git tree: linux-4.19.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=163e3d8e900000
kernel config:
https://syzkaller.appspot.com/x/.config?x=30067df04d3254aa
dashboard link:
https://syzkaller.appspot.com/bug?extid=072b2b7eb682bc673fa8
compiler: gcc (GCC) 10.1.0-syz 20200507
Unfortunately, I don't have any reproducer for this issue yet.
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+072b2b...@syzkaller.appspotmail.com
kasan: CONFIG_KASAN_INLINE enabled
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
CPU: 1 PID: 13287 Comm: syz-executor.2 Not tainted 4.19.142-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:vgem_fence_attach_ioctl+0x27d/0x640 drivers/gpu/drm/vgem/vgem_fence.c:184
Code: 03 80 3c 02 00 0f 85 9b 03 00 00 4c 8b b5 10 01 00 00 48 b8 00 00 00 00 00 fc ff df 49 8d be e0 00 00 00 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 7f 03 00 00 4c 89 ea 4d 8b b6 e0 00 00 00 48 b8
RSP: 0018:ffff88804c07faf0 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: ffff888091708300 RCX: 1ffff1100980ff4b
RDX: 000000000000001c RSI: ffffffff815addbf RDI: 00000000000000e0
RBP: ffff888094162d40 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff888097418c80
R13: ffff888091708304 R14: 0000000000000000 R15: ffff888097418d18
FS: 00007f7b81ab5700(0000) GS:ffff8880ae700000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000001590004 CR3: 000000003fa85000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
drm_ioctl_kernel+0x208/0x2a0 drivers/gpu/drm/drm_ioctl.c:757
drm_ioctl+0x507/0x9c0 drivers/gpu/drm/drm_ioctl.c:857
vfs_ioctl fs/ioctl.c:46 [inline]
file_ioctl fs/ioctl.c:501 [inline]
do_vfs_ioctl+0xcdb/0x12e0 fs/ioctl.c:688
ksys_ioctl+0x9b/0xc0 fs/ioctl.c:705
__do_sys_ioctl fs/ioctl.c:712 [inline]
__se_sys_ioctl fs/ioctl.c:710 [inline]
__x64_sys_ioctl+0x6f/0xb0 fs/ioctl.c:710
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45d5b9
Code: 5d b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 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 0f 83 2b b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f7b81ab4c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 000000000000c4c0 RCX: 000000000045d5b9
RDX: 0000000020000140 RSI: 00000000c10c5541 RDI: 0000000000000005
RBP: 000000000118cf80 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118cf4c
R13: 00007ffdfdc37f9f R14: 00007f7b81ab59c0 R15: 000000000118cf4c
Modules linked in:
---[ end trace 9519bf0edcd482d7 ]---
RIP: 0010:vgem_fence_attach_ioctl+0x27d/0x640 drivers/gpu/drm/vgem/vgem_fence.c:184
Code: 03 80 3c 02 00 0f 85 9b 03 00 00 4c 8b b5 10 01 00 00 48 b8 00 00 00 00 00 fc ff df 49 8d be e0 00 00 00 48 89 fa 48 c1 ea 03 <80> 3c 02 00 0f 85 7f 03 00 00 4c 89 ea 4d 8b b6 e0 00 00 00 48 b8
RSP: 0018:ffff88804c07faf0 EFLAGS: 00010202
RAX: dffffc0000000000 RBX: ffff888091708300 RCX: 1ffff1100980ff4b
RDX: 000000000000001c RSI: ffffffff815addbf RDI: 00000000000000e0
gfs2: not a GFS2 filesystem
RBP: ffff888094162d40 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: ffff888097418c80
R13: ffff888091708304 R14: 0000000000000000 R15: ffff888097418d18
FS: 00007f7b81ab5700(0000) GS:ffff8880ae600000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
gfs2: not a GFS2 filesystem
CR2: 00007f1d666bc020 CR3: 000000003fa85000 CR4: 00000000001406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
---
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.