syzbot


stack segment fault in release_metapage

Status: upstream: reported C repro on 2025/08/20 09:22
Subsystems: jfs
[Documentation on labels]
Reported-by: syzbot+43706fd1eb4c8dccdfe6@syzkaller.appspotmail.com
First crash: 117d, last: 3d02h
Cause bisection: failed (error log, bisect log)
  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [jfs?] stack segment fault in release_metapage 0 (1) 2025/08/20 09:22
Last patch testing requests (2)
Created Duration User Patch Repo Result
2025/09/15 17:10 13m retest repro upstream report log
2025/09/15 17:10 13m retest repro upstream report log
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2025/10/21 00:38 1h37m bisect fix upstream OK (0) job log log

Sample crash report:
Oops: stack segment: 0000 [#1] SMP KASAN PTI
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:folio_flags include/linux/page-flags.h:360 [inline]
RIP: 0010:folio_trylock include/linux/pagemap.h:1114 [inline]
RIP: 0010:folio_lock include/linux/pagemap.h:1150 [inline]
RIP: 0010:release_metapage+0x9e/0xab0 fs/jfs/jfs_metapage.c:870
Code: 04 00 00 e8 64 bc 81 fe 48 c7 c7 20 d2 e0 8c be 7d 04 00 00 e8 13 ff 53 fe 2e 2e 2e 31 c0 49 8d 5c 24 08 48 89 dd 48 c1 ed 03 <42> 80 7c 2d 00 00 74 08 48 89 df e8 d2 4e e3 fe 4c 8b 3b 4c 89 fe
RSP: 0018:ffffc900039a7698 EFLAGS: 00010202
RAX: 0000000000000000 RBX: 0000000000000008 RCX: 6a81ba0887be9900
RDX: ffff88801dbe5a00 RSI: ffffffff8cfbaf1f RDI: ffffffff8b3e7e80
RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed10084e09d2 R12: 0000000000000000
R13: dffffc0000000000 R14: ffff888042704e68 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff888126d88000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f1c30b3beb8 CR3: 00000000237a4000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 xtTruncate+0xe84/0x2e70 fs/jfs/jfs_xtree.c:-1
 jfs_free_zero_link+0x33a/0x4a0 fs/jfs/namei.c:759
 jfs_evict_inode+0x363/0x440 fs/jfs/inode.c:159
 evict+0x5f4/0xae0 fs/inode.c:837
 txLazyCommit fs/jfs/jfs_txnmgr.c:2665 [inline]
 jfs_lazycommit+0x3f1/0xa10 fs/jfs/jfs_txnmgr.c:2734
 kthread+0x711/0x8a0 kernel/kthread.c:463
 ret_from_fork+0x52d/0xa60 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:folio_flags include/linux/page-flags.h:360 [inline]
RIP: 0010:folio_trylock include/linux/pagemap.h:1114 [inline]
RIP: 0010:folio_lock include/linux/pagemap.h:1150 [inline]
RIP: 0010:release_metapage+0x9e/0xab0 fs/jfs/jfs_metapage.c:870
Code: 04 00 00 e8 64 bc 81 fe 48 c7 c7 20 d2 e0 8c be 7d 04 00 00 e8 13 ff 53 fe 2e 2e 2e 31 c0 49 8d 5c 24 08 48 89 dd 48 c1 ed 03 <42> 80 7c 2d 00 00 74 08 48 89 df e8 d2 4e e3 fe 4c 8b 3b 4c 89 fe
RSP: 0018:ffffc900039a7698 EFLAGS: 00010202
RAX: 0000000000000000 RBX: 0000000000000008 RCX: 6a81ba0887be9900
RDX: ffff88801dbe5a00 RSI: ffffffff8cfbaf1f RDI: ffffffff8b3e7e80
RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed10084e09d2 R12: 0000000000000000
R13: dffffc0000000000 R14: ffff888042704e68 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff888126e88000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055c0c1fdc138 CR3: 000000003151e000 CR4: 00000000003526f0
----------------
Code disassembly (best guess), 1 bytes skipped:
   0:	00 00                	add    %al,(%rax)
   2:	e8 64 bc 81 fe       	call   0xfe81bc6b
   7:	48 c7 c7 20 d2 e0 8c 	mov    $0xffffffff8ce0d220,%rdi
   e:	be 7d 04 00 00       	mov    $0x47d,%esi
  13:	e8 13 ff 53 fe       	call   0xfe53ff2b
  18:	2e 2e 2e 31 c0       	cs cs cs xor %eax,%eax
  1d:	49 8d 5c 24 08       	lea    0x8(%r12),%rbx
  22:	48 89 dd             	mov    %rbx,%rbp
  25:	48 c1 ed 03          	shr    $0x3,%rbp
* 29:	42 80 7c 2d 00 00    	cmpb   $0x0,0x0(%rbp,%r13,1) <-- trapping instruction
  2f:	74 08                	je     0x39
  31:	48 89 df             	mov    %rbx,%rdi
  34:	e8 d2 4e e3 fe       	call   0xfee34f0b
  39:	4c 8b 3b             	mov    (%rbx),%r15
  3c:	4c 89 fe             	mov    %r15,%rsi

Crashes (17):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/12/02 19:30 upstream 4a26e7032d7d d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs stack segment fault in release_metapage
2025/11/28 19:32 upstream e538109ac71d d6526ea3 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs stack segment fault in release_metapage
2025/11/26 04:45 upstream 8a2bcda5e139 64219f15 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs stack segment fault in release_metapage
2025/09/01 00:52 upstream 5c3b3264e585 807a3b61 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs stack segment fault in release_metapage
2025/08/20 09:21 upstream b19a97d57c15 79512909 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-upstream-fs stack segment fault in release_metapage
2025/11/16 08:49 upstream f824272b6e3f f7988ea4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2025/11/12 12:55 upstream 24172e0d7990 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2025/11/10 23:30 upstream 4ea7c1717f3f 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2025/11/10 15:19 upstream e9a6fb0bcdd7 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2025/11/10 12:46 upstream e9a6fb0bcdd7 4e1406b4 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2025/10/31 12:23 upstream d127176862a9 2c50b6a9 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2025/10/25 13:02 upstream d2818517e348 c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2025/10/24 04:51 upstream 266ee584e55e c0460fcd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2025/10/22 04:48 upstream 552c50713f27 252fbbad .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2025/08/21 16:20 upstream 068a56e56fa8 3e79b825 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2025/08/20 04:50 upstream b19a97d57c15 79512909 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2025/08/10 17:52 upstream 2b38afce25c4 32a0e5ed .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
* Struck through repros no longer work on HEAD.