syzbot


BUG: unable to handle kernel paging request in write_inode_now

Status: upstream: reported C repro on 2023/04/26 14:54
Reported-by: syzbot+93da6e97a594c63ac165@syzkaller.appspotmail.com
First crash: 773d, last: 49d
Fix bisection: failed (error log, bisect log)
  
Bug presence (1)
Date Name Commit Repro Result
2025/05/26 upstream (ToT) 0ff41df1cb26 C Didn't crash
Last patch testing requests (8)
Created Duration User Patch Repo Result
2025/05/25 07:32 17m retest repro linux-5.15.y OK log
2025/05/25 07:32 17m retest repro linux-5.15.y OK log
2025/05/15 19:51 15m retest repro linux-5.15.y OK log
2025/05/15 19:51 23m retest repro linux-5.15.y OK log
2025/03/15 14:58 1h59m retest repro linux-5.15.y report log
2025/03/15 14:58 22m retest repro linux-5.15.y report log
2025/03/15 14:58 19m retest repro linux-5.15.y report log
2025/03/01 00:47 21m retest repro linux-5.15.y report log
Fix bisection attempts (9)
Created Duration User Patch Repo Result
2025/05/22 05:13 19m bisect fix linux-5.15.y error job log
2025/04/19 14:00 2h24m bisect fix linux-5.15.y OK (0) job log log
2024/03/30 04:50 2h55m bisect fix linux-5.15.y OK (0) job log log
2024/02/28 15:20 2h12m bisect fix linux-5.15.y OK (0) job log log
2024/01/19 14:59 2h40m bisect fix linux-5.15.y OK (0) job log log
2023/12/12 08:36 2h05m bisect fix linux-5.15.y OK (0) job log log
2023/11/11 08:21 2h14m bisect fix linux-5.15.y OK (0) job log log
2023/10/09 04:55 2h19m fix candidate upstream OK (0) job log log
2023/07/22 14:04 2h31m bisect fix linux-5.15.y OK (0) job log log

Sample crash report:
loop2: detected capacity change from 0 to 4096
ntfs3: loop2: Different NTFS' sector size (1024) and media sector size (512)
BUG: unable to handle page fault for address: fffff521005f9f2f
#PF: supervisor read access in kernel mode
#PF: error_code(0x0000) - not-present page
PGD 23ffee067 P4D 23ffee067 PUD 0 
Oops: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 13595 Comm: syz.2.2179 Not tainted 5.15.179-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 02/12/2025
RIP: 0010:write_inode_now+0x9b/0x2f0 fs/fs-writeback.c:2789
Code: 10 f3 f3 f3 f3 e8 f5 ec 9d ff 48 8d 7c 24 48 ba 58 00 00 00 31 f6 e8 e4 e0 e7 ff 4c 89 f8 48 c1 e8 03 49 89 de 48 89 44 24 10 <80> 3c 18 00 74 08 4c 89 ff e8 97 df e7 ff 48 bb ff ff ff ff ff ff
RSP: 0018:ffffc90002fcf940 EFLAGS: 00010a06
RAX: 1ffff920005f9f30 RBX: dffffc00ffffffff RCX: 0000000000000000
RDX: 0000000000000058 RSI: 0000000000000000 RDI: ffffc90002fcf9e0
RBP: ffffc90002fcfa48 R08: dffffc0000000000 R09: ffffc90002fcf988
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000001
R13: ffff8880746f1fd0 R14: dffffc00ffffffff R15: ffffc90002fcf980
FS:  00007f400ee496c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffff521005f9f2f CR3: 000000004ade4000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 iput_final fs/inode.c:1756 [inline]
 iput+0x5ce/0x8b0 fs/inode.c:1795
 ntfs_fill_super+0x3b43/0x4340 fs/ntfs3/super.c:1185
 get_tree_bdev+0x3fe/0x620 fs/super.c:1325
 vfs_get_tree+0x88/0x270 fs/super.c:1530
 do_new_mount+0x2ba/0xb40 fs/namespace.c:3012
 do_mount fs/namespace.c:3355 [inline]
 __do_sys_mount fs/namespace.c:3563 [inline]
 __se_sys_mount+0x2d5/0x3c0 fs/namespace.c:3540
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3b/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f4010fe190a
Code: d8 64 89 02 48 c7 c0 ff ff ff ff eb a6 e8 de 1a 00 00 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f400ee48e68 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f400ee48ef0 RCX: 00007f4010fe190a
RDX: 0000400000000000 RSI: 0000400000000980 RDI: 00007f400ee48eb0
RBP: 0000400000000000 R08: 00007f400ee48ef0 R09: 0000000002204014
R10: 0000000002204014 R11: 0000000000000246 R12: 0000400000000980
R13: 00007f400ee48eb0 R14: 000000000001f88b R15: 0000400000000780
 </TASK>
Modules linked in:
CR2: fffff521005f9f2f
---[ end trace f06b785eafa4e767 ]---
RIP: 0010:write_inode_now+0x9b/0x2f0 fs/fs-writeback.c:2789
Code: 10 f3 f3 f3 f3 e8 f5 ec 9d ff 48 8d 7c 24 48 ba 58 00 00 00 31 f6 e8 e4 e0 e7 ff 4c 89 f8 48 c1 e8 03 49 89 de 48 89 44 24 10 <80> 3c 18 00 74 08 4c 89 ff e8 97 df e7 ff 48 bb ff ff ff ff ff ff
RSP: 0018:ffffc90002fcf940 EFLAGS: 00010a06
RAX: 1ffff920005f9f30 RBX: dffffc00ffffffff RCX: 0000000000000000
RDX: 0000000000000058 RSI: 0000000000000000 RDI: ffffc90002fcf9e0
RBP: ffffc90002fcfa48 R08: dffffc0000000000 R09: ffffc90002fcf988
R10: 0000000000000000 R11: dffffc0000000001 R12: 0000000000000001
R13: ffff8880746f1fd0 R14: dffffc00ffffffff R15: ffffc90002fcf980
FS:  00007f400ee496c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: fffff521005f9f2f CR3: 000000004ade4000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
----------------
Code disassembly (best guess):
   0:	10 f3                	adc    %dh,%bl
   2:	f3 f3 f3 e8 f5 ec 9d 	repz repz repz call 0xff9decff
   9:	ff
   a:	48 8d 7c 24 48       	lea    0x48(%rsp),%rdi
   f:	ba 58 00 00 00       	mov    $0x58,%edx
  14:	31 f6                	xor    %esi,%esi
  16:	e8 e4 e0 e7 ff       	call   0xffe7e0ff
  1b:	4c 89 f8             	mov    %r15,%rax
  1e:	48 c1 e8 03          	shr    $0x3,%rax
  22:	49 89 de             	mov    %rbx,%r14
  25:	48 89 44 24 10       	mov    %rax,0x10(%rsp)
* 2a:	80 3c 18 00          	cmpb   $0x0,(%rax,%rbx,1) <-- trapping instruction
  2e:	74 08                	je     0x38
  30:	4c 89 ff             	mov    %r15,%rdi
  33:	e8 97 df e7 ff       	call   0xffe7dfcf
  38:	48                   	rex.W
  39:	bb ff ff ff ff       	mov    $0xffffffff,%ebx
  3e:	ff                   	(bad)
  3f:	ff                   	.byte 0xff

Crashes (35):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/03/16 23:21 linux-5.15.y 0c935c049b5c e2826670 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2025/02/14 16:06 linux-5.15.y c16c81c81336 1022af74 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2025/02/05 07:41 linux-5.15.y c16c81c81336 5896748e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2025/01/30 02:21 linux-5.15.y 003148680b79 136953f1 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2025/01/27 06:26 linux-5.15.y 003148680b79 9fbd772e .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2025/01/20 18:23 linux-5.15.y 4735586da88e 6e87cfa2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2025/01/17 15:34 linux-5.15.y 4735586da88e 953d1c45 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2025/01/12 20:53 linux-5.15.y 4735586da88e 6dbc6a9b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2025/01/08 00:28 linux-5.15.y 91786f140358 f3558dbf .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2024/11/28 05:28 linux-5.15.y 0a51d2d4527b 5df23865 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2024/10/08 10:53 linux-5.15.y 3a5928702e71 402f1df0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2024/09/30 19:09 linux-5.15.y 3a5928702e71 bbd4e0a4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2024/09/12 11:42 linux-5.15.y 3a5928702e71 60e1a995 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2024/08/19 22:38 linux-5.15.y fa93fa65db6e 9f0ab3fb .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2024/07/26 22:42 linux-5.15.y 7c6d66f0266f 46eb10b7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2024/06/15 02:08 linux-5.15.y c61bd26ae81a f429ab00 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2024/05/22 14:58 linux-5.15.y 83655231580b 4d098039 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2024/05/15 22:52 linux-5.15.y 284087d4f7d5 94b087b1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2024/05/10 02:30 linux-5.15.y 284087d4f7d5 de979bc2 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2024/05/06 12:03 linux-5.15.y 284087d4f7d5 d884b519 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2024/05/04 07:55 linux-5.15.y 284087d4f7d5 610f2a54 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2024/04/27 18:05 linux-5.15.y b925f60c6ee7 07b455f9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2024/04/22 16:51 linux-5.15.y c52b9710c83d 36c961ad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2024/04/22 13:40 linux-5.15.y c52b9710c83d 36c961ad .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2024/04/19 07:10 linux-5.15.y c52b9710c83d af24b050 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2024/04/09 19:37 linux-5.15.y 9465fef4ae35 171ec371 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2024/04/03 13:28 linux-5.15.y 9465fef4ae35 7925100d .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2023/12/19 09:19 linux-5.15.y d0fc081c6241 3ad490ea .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2023/09/10 14:26 linux-5.15.y aff03380bda4 6654cf89 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2023/08/13 02:35 linux-5.15.y 24c4de4069cb 39990d51 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2023/06/11 18:27 linux-5.15.y 7349e40704a0 49519f06 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2023/05/23 22:05 linux-5.15.y 9d6bde853685 4bce1a3e .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2023/08/23 22:47 linux-5.15.y f6f7927ac664 b81ca3f6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2023/05/10 06:38 linux-5.15.y 8a7f2a5c5aa1 1964022b .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
2023/04/26 14:53 linux-5.15.y f48aeeaaa64c 8d843721 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan BUG: unable to handle kernel paging request in write_inode_now
* Struck through repros no longer work on HEAD.