syzbot

 sign-in | mailing list | source | docs
🐞 Open [717] 🐞 Fixed [181] 🐞 Invalid [640] 📈 Kernel Health 📈 Bug Lifetimes 📈 Fuzzing 📈 Crashes 💬 Send us feedback

general protection fault in loop_validate_file

Status: upstream: reported C repro on 2019/08/28 22:28
Reported-by: syzbot+e081281da3b470ee9d84@syzkaller.appspotmail.com
First crash: 1696d, last: 413d
Fix bisection: failed (error log, bisect log)
  
▶ ▼ Similar bugs (6)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
android-44 general protection fault in loop_validate_file syz 20 1915d 1833d 0/2 public: reported syz repro on 2019/04/14 00:02
android-414 general protection fault in loop_validate_file 4 1922d 1833d 0/1 auto-closed as invalid on 2019/07/13 08:46
upstream general protection fault in loop_validate_file block C 19 1948d 2132d 0/26 closed as dup on 2018/06/18 14:51
android-49 general protection fault in loop_validate_file syz 28 1689d 1832d 0/3 public: reported syz repro on 2019/04/14 09:28
upstream general protection fault in loop_validate_file (2) block 3 1857d 1859d 11/26 fixed on 2019/04/01 10:28
android-414 general protection fault in loop_validate_file (2) syz 6 1687d 1733d 0/1 public: reported syz repro on 2019/07/22 13:25
▶ ▼ Last patch testing requests (1)
Created Duration User Patch Repo Result
2022/11/09 05:30 9m retest repro linux-4.14.y report log
▶ ▼ Fix bisection attempts (8)
Created Duration User Patch Repo Result
2020/07/08 08:13 0m bisect fix linux-4.14.y error job log (0)
2020/06/08 05:50 25m bisect fix linux-4.14.y job log (0) log
2020/05/09 05:24 25m bisect fix linux-4.14.y job log (0) log
2020/04/09 04:59 24m bisect fix linux-4.14.y job log (0) log
2020/03/10 04:31 28m bisect fix linux-4.14.y job log (0) log
2020/02/09 04:05 25m bisect fix linux-4.14.y job log (0) log
2020/01/10 03:33 31m bisect fix linux-4.14.y job log (0) log
2019/12/09 00:07 30m bisect fix linux-4.14.y job log (0) log

Sample crash report:
IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
hrtimer: interrupt took 24701 ns
kasan: CONFIG_KASAN_INLINE enabled
kobject: 'loop4' (ffff8880a4b1d460): kobject_uevent_env
kasan: GPF could be caused by NULL-ptr deref or user memory access
general protection fault: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
kobject: 'loop4' (ffff8880a4b1d460): fill_kobj_path: path = '/devices/virtual/block/loop4'
CPU: 1 PID: 6787 Comm: syz-executor777 Not tainted 4.14.141 #37
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
task: ffff88808fbf2180 task.stack: ffff888087d08000
RIP: 0010:loop_validate_file+0x206/0x2d0 drivers/block/loop.c:633
RSP: 0018:ffff888087d0fbc0 EFLAGS: 00010202
RAX: 0000000000000037 RBX: ffff8880a77b6218 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffff8880a77e0700 RDI: 00000000000001b8
RBP: ffff888087d0fbe0 R08: ffff88808fbf2180 R09: 0000000000000001
R10: 0000000000000000 R11: ffff88808fbf2180 R12: 0000000000000000
R13: ffff8880a77e0700 R14: dffffc0000000000 R15: ffff888219561c90
FS:  00007f1c27602700(0000) GS:ffff8880aef00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f1c27601db8 CR3: 0000000085fbb000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 loop_set_fd drivers/block/loop.c:897 [inline]
 lo_ioctl+0xaa6/0x1ce0 drivers/block/loop.c:1407
 __blkdev_driver_ioctl block/ioctl.c:297 [inline]
 blkdev_ioctl+0x96b/0x1860 block/ioctl.c:594
 block_ioctl+0xde/0x120 fs/block_dev.c:1881
 vfs_ioctl fs/ioctl.c:46 [inline]
 file_ioctl fs/ioctl.c:500 [inline]
 do_vfs_ioctl+0x7ae/0x1060 fs/ioctl.c:684
 SYSC_ioctl fs/ioctl.c:701 [inline]
 SyS_ioctl+0x8f/0xc0 fs/ioctl.c:692
 do_syscall_64+0x1e8/0x640 arch/x86/entry/common.c:292
 entry_SYSCALL_64_after_hwframe+0x42/0xb7
RIP: 0033:0x44dc49
RSP: 002b:00007f1c27601ce8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
RAX: ffffffffffffffda RBX: 00000000006e6a18 RCX: 000000000044dc49
RDX: 0000000000000006 RSI: 0000000000004c00 RDI: 0000000000000004
RBP: 00000000006e6a10 R08: 00007f1c27602700 R09: 0000000000000000
R10: 00007f1c27602700 R11: 0000000000000246 R12: 00000000006e6a1c
R13: 00007fff92f63faf R14: 00007f1c276029c0 R15: 0000000000000001
Code: 00 00 48 89 f8 48 c1 e8 03 42 80 3c 30 00 0f 85 d4 00 00 00 4d 8b a4 24 f0 00 00 00 49 8d bc 24 b8 01 00 00 48 89 f8 48 c1 e8 03 <42> 80 3c 30 00 0f 85 a8 00 00 00 4d 8b a4 24 b8 01 00 00 4c 89 
RIP: loop_validate_file+0x206/0x2d0 drivers/block/loop.c:633 RSP: ffff888087d0fbc0
---[ end trace fa376e453dbfae2f ]---

Crashes (9):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2019/09/04 10:16 linux-4.14.y 01fd1694b93c 526709ff .config console log report syz C ci2-linux-4-14
2023/03/03 15:44 linux-4.14.y 7878a41b6cc1 f8902b57 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 general protection fault in loop_validate_file
2022/12/23 22:03 linux-4.14.y c4215ee4771b 9da18ae8 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-4-14 general protection fault in loop_validate_file
2022/05/22 01:27 linux-4.14.y dffb5c6ff09c 7268fa62 .config console log report info ci2-linux-4-14 general protection fault in loop_validate_file
2020/09/27 10:56 linux-4.14.y cbfa1702aaf6 5dd8aee8 .config console log report info ci2-linux-4-14
2019/12/11 03:32 linux-4.14.y a844dc4c5442 101194eb .config console log report ci2-linux-4-14
2019/09/23 19:21 linux-4.14.y f6e27dbb1afa c68252d2 .config console log report ci2-linux-4-14
2019/09/07 03:30 linux-4.14.y 414510bc00a5 a60cb4cd .config console log report ci2-linux-4-14
2019/08/28 21:27 linux-4.14.y b5260801526c 1eb076e9 .config console log report ci2-linux-4-14
* Struck through repros no longer work on HEAD.