syzbot


general protection fault in metapage_write_folio

Status: upstream: reported C repro on 2024/10/08 18:13
Subsystems: jfs
[Documentation on labels]
Reported-by: syzbot+d7ffeb5538fe5c793f74@syzkaller.appspotmail.com
First crash: 436d, last: 57m
Cause bisection: introduced by (bisect log) :
commit 35474d52c6056976e675e9130d755cdb749ded5a
Author: Matthew Wilcox (Oracle) <willy@infradead.org>
Date: Wed Apr 17 17:56:46 2024 +0000

  jfs: Convert metapage_writepage to metapage_write_folio

Crash: BUG: unable to handle kernel NULL pointer dereference in metapage_write_folio (log)
Repro: syz .config
  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [jfs?] general protection fault in metapage_write_folio 0 (1) 2024/10/08 18:13
Last patch testing requests (10)
Created Duration User Patch Repo Result
2025/10/27 02:20 27m retest repro linux-next report log
2025/10/27 02:20 24m retest repro linux-next OK log
2025/10/27 02:20 22m retest repro linux-next report log
2025/10/27 02:20 19m retest repro upstream report log
2025/08/01 02:27 25m retest repro linux-next error
2025/08/01 02:27 3h20m retest repro linux-next report log
2025/08/01 02:27 24m retest repro linux-next report log
2025/06/11 03:20 18m retest repro upstream report log
2025/06/11 03:20 25m retest repro upstream report log
2025/06/11 03:20 16m retest repro upstream report log

Sample crash report:
Oops: general protection fault, probably for non-canonical address 0xdffffc0000000000: 0000 [#1] SMP KASAN PTI
KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007]
CPU: 0 UID: 0 PID: 122 Comm: jfsCommit Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/25/2025
RIP: 0010:metapage_write_folio+0xa8/0xca0 fs/jfs/jfs_metapage.c:428
Code: e8 bd 45 82 fe 4d 8d 74 24 18 4c 89 f0 48 c1 e8 03 42 80 3c 38 00 74 08 4c 89 f7 e8 42 04 e4 fe 4d 8b 36 4c 89 f0 48 c1 e8 03 <42> 80 3c 38 00 74 08 4c 89 f7 e8 29 04 e4 fe 49 8b 1e 4d 8d 74 24
RSP: 0018:ffffc900031df7a0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 1ffffd40002b6ebe RCX: ffff88801df68000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc900031df8b0 R08: ffffea00015b75f7 R09: 1ffffd40002b6ebe
R10: dffffc0000000000 R11: fffff940002b6ebf R12: ffffea00015b75c0
R13: 0000000000000081 R14: 0000000000000000 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff888126df7000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f66d4016000 CR3: 000000003a8f0000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 metapage_write_one+0x24c/0x450 fs/jfs/jfs_metapage.c:818
 release_metapage+0x5b9/0xab0 fs/jfs/jfs_metapage.c:884
 txUnlock+0x509/0xdc0 fs/jfs/jfs_txnmgr.c:948
 txLazyCommit fs/jfs/jfs_txnmgr.c:2683 [inline]
 jfs_lazycommit+0x52e/0xa10 fs/jfs/jfs_txnmgr.c:2734
 kthread+0x711/0x8a0 kernel/kthread.c:463
 ret_from_fork+0x4bc/0x870 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:metapage_write_folio+0xa8/0xca0 fs/jfs/jfs_metapage.c:428
Code: e8 bd 45 82 fe 4d 8d 74 24 18 4c 89 f0 48 c1 e8 03 42 80 3c 38 00 74 08 4c 89 f7 e8 42 04 e4 fe 4d 8b 36 4c 89 f0 48 c1 e8 03 <42> 80 3c 38 00 74 08 4c 89 f7 e8 29 04 e4 fe 49 8b 1e 4d 8d 74 24
RSP: 0018:ffffc900031df7a0 EFLAGS: 00010246
RAX: 0000000000000000 RBX: 1ffffd40002b6ebe RCX: ffff88801df68000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc900031df8b0 R08: ffffea00015b75f7 R09: 1ffffd40002b6ebe
R10: dffffc0000000000 R11: fffff940002b6ebf R12: ffffea00015b75c0
R13: 0000000000000081 R14: 0000000000000000 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff888126df7000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f66d4016000 CR3: 000000003a8f0000 CR4: 00000000003526f0
----------------
Code disassembly (best guess):
   0:	e8 bd 45 82 fe       	call   0xfe8245c2
   5:	4d 8d 74 24 18       	lea    0x18(%r12),%r14
   a:	4c 89 f0             	mov    %r14,%rax
   d:	48 c1 e8 03          	shr    $0x3,%rax
  11:	42 80 3c 38 00       	cmpb   $0x0,(%rax,%r15,1)
  16:	74 08                	je     0x20
  18:	4c 89 f7             	mov    %r14,%rdi
  1b:	e8 42 04 e4 fe       	call   0xfee40462
  20:	4d 8b 36             	mov    (%r14),%r14
  23:	4c 89 f0             	mov    %r14,%rax
  26:	48 c1 e8 03          	shr    $0x3,%rax
* 2a:	42 80 3c 38 00       	cmpb   $0x0,(%rax,%r15,1) <-- trapping instruction
  2f:	74 08                	je     0x39
  31:	4c 89 f7             	mov    %r14,%rdi
  34:	e8 29 04 e4 fe       	call   0xfee40462
  39:	49 8b 1e             	mov    (%r14),%rbx
  3c:	4d                   	rex.WRB
  3d:	8d                   	.byte 0x8d
  3e:	74 24                	je     0x64

Crashes (230):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/11/13 12:07 upstream e927c520e1ba 07e030de .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs general protection fault in metapage_write_folio
2025/10/04 07:27 upstream 9b0d551bcc05 49379ee0 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs general protection fault in metapage_write_folio
2025/06/25 22:19 upstream 92ca6c498a5e 26d77996 .config strace log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs general protection fault in metapage_write_folio
2025/06/25 21:45 upstream 92ca6c498a5e 26d77996 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs general protection fault in metapage_write_folio
2025/02/03 03:53 upstream 69b8923f5003 568559e4 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs general protection fault in metapage_write_folio
2025/10/09 03:09 upstream cd5a0afbdf80 7e2882b3 .config console log report syz / log C [disk image (non-bootable)] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci-snapshot-upstream-root general protection fault in metapage_write_folio
2025/05/15 08:45 upstream c94d59a126cb d6b2ee52 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs general protection fault in metapage_write_folio
2024/10/23 13:18 upstream c2ee9f594da8 15fa2979 .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci2-upstream-fs general protection fault in metapage_write_folio
2024/10/05 19:42 upstream 27cc6fdf7201 d7906eff .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci2-upstream-fs general protection fault in metapage_write_folio
2024/10/06 04:46 linux-next c02d24a5af66 d7906eff .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] ci-upstream-linux-next-kasan-gce-root general protection fault in metapage_write_folio
2024/10/06 03:06 linux-next c02d24a5af66 d7906eff .config console log report syz / log [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] [mounted in repro #3] ci-upstream-linux-next-kasan-gce-root general protection fault in metapage_write_folio
2025/12/15 07:01 upstream 8f0b4cce4481 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/12/14 06:39 upstream 9d9c1cfec01c d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/12/12 08:05 upstream d358e5254674 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/12/02 08:27 upstream 1d18101a644e d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/11/29 02:45 upstream e538109ac71d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/11/25 10:44 upstream ac3fd01e4c1e 64219f15 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/11/14 04:22 upstream 2ccec5944606 07e030de .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/11/13 17:43 upstream 2ccec5944606 07e030de .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/11/13 10:56 upstream e927c520e1ba 07e030de .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/11/13 07:18 upstream e927c520e1ba 07e030de .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/11/13 05:43 upstream e927c520e1ba 07e030de .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/11/13 04:18 upstream e927c520e1ba 07e030de .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/11/13 01:40 upstream 24172e0d7990 07e030de .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/11/12 21:10 upstream 24172e0d7990 07e030de .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/11/12 13:57 upstream 24172e0d7990 07e030de .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/11/12 12:10 upstream 24172e0d7990 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/11/12 06:43 upstream 24172e0d7990 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/11/12 06:29 upstream 24172e0d7990 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/11/11 01:11 upstream 4ea7c1717f3f 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/11/09 15:47 upstream 439fc29dfd3b 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/11/09 10:58 upstream 7bb4d6512545 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/10/04 05:49 upstream 9b0d551bcc05 49379ee0 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/09/14 04:49 upstream 5cd64d4f9268 e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/08/30 10:24 upstream fb679c832b64 807a3b61 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/08/29 00:40 upstream 07d9df80082b d401b9d7 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/07/18 00:16 upstream e2291551827f 0d1223f1 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs general protection fault in metapage_write_folio
2025/07/06 11:51 upstream 1f988d0788f5 4f67c4ae .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-badwrites-root general protection fault in metapage_write_folio
2025/06/30 09:59 upstream d0b3b7b22dfa fc9d8ee5 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root general protection fault in metapage_write_folio
2025/12/11 10:30 upstream d358e5254674 d1b870e1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root general protection fault in metapage_write_folio
2025/12/09 05:05 upstream a110f942672c d1b870e1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root general protection fault in metapage_write_folio
2025/11/28 17:06 upstream e538109ac71d d1b870e1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root general protection fault in metapage_write_folio
2025/11/18 14:00 upstream e7c375b18160 ef766cd7 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root general protection fault in metapage_write_folio
2025/11/16 23:25 upstream 7254a2b52279 f7988ea4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root general protection fault in metapage_write_folio
2025/11/10 22:30 upstream 4ea7c1717f3f 4e1406b4 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root general protection fault in metapage_write_folio
2025/10/27 06:44 upstream dbfc6422a34d c0460fcd .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root general protection fault in metapage_write_folio
2025/10/27 06:44 upstream dbfc6422a34d c0460fcd .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root general protection fault in metapage_write_folio
2025/09/20 16:49 upstream cd89d487374c 67c37560 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root general protection fault in metapage_write_folio
2025/08/26 13:23 upstream fab1beda7597 bf27483f .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root general protection fault in metapage_write_folio
2025/08/24 09:49 upstream 8d245acc1e88 bf27483f .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root general protection fault in metapage_write_folio
2025/08/23 11:14 upstream 6debb6904172 bf27483f .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root general protection fault in metapage_write_folio
2025/08/08 18:46 upstream bec077162bd0 56444e07 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root general protection fault in metapage_write_folio
2025/08/07 02:49 upstream cca7a0aae895 9a42d6b1 .config console log report [disk image (non-bootable)] [vmlinux] [kernel image] ci-snapshot-upstream-root general protection fault in metapage_write_folio
2024/10/10 21:43 linux-next 0cca97bf2364 8fbfc0c8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-linux-next-kasan-gce-root general protection fault in metapage_write_folio
2024/10/06 06:10 linux-next c02d24a5af66 d7906eff .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro #1] [mounted in repro #2] [mounted in repro #3] ci-upstream-linux-next-kasan-gce-root general protection fault in metapage_write_folio
2025/12/13 01:49 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 05c93f3395ed d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 BUG: unable to handle kernel paging request in metapage_write_folio
2025/12/10 15:48 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 05c93f3395ed d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 BUG: unable to handle kernel paging request in metapage_write_folio
2025/10/13 01:09 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci bf45a62baffc ff1712fe .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 BUG: unable to handle kernel paging request in metapage_write_folio
2025/10/08 09:04 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci bf45a62baffc 7e2882b3 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 BUG: unable to handle kernel paging request in metapage_write_folio
2025/09/10 20:48 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci c199ef1fa61a fdeaa69b .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 BUG: unable to handle kernel paging request in metapage_write_folio
2025/09/02 00:32 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8f5ae30d69d7 807a3b61 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 BUG: unable to handle kernel paging request in metapage_write_folio
2025/08/31 23:47 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 8f5ae30d69d7 807a3b61 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 BUG: unable to handle kernel paging request in metapage_write_folio
* Struck through repros no longer work on HEAD.