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: 171d, last: 7h09m
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 (6)
Created Duration User Patch Repo Result
2025/12/17 14:30 12m retest repro upstream error
2025/12/17 14:30 17m retest repro upstream report log
2025/12/17 14:30 15m retest repro upstream report log
2025/12/17 14:30 13m retest repro upstream report log
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: 1 UID: 0 PID: 122 Comm: jfsCommit Not tainted syzkaller #0 PREEMPT_{RT,(full)} 
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/13/2026
RIP: 0010:folio_flags include/linux/page-flags.h:360 [inline]
RIP: 0010:folio_trylock include/linux/pagemap.h:1133 [inline]
RIP: 0010:folio_lock include/linux/pagemap.h:1169 [inline]
RIP: 0010:release_metapage+0x9e/0xab0 fs/jfs/jfs_metapage.c:870
Code: 04 00 00 e8 b4 04 77 fe 48 c7 c7 f3 e1 36 8d be 90 04 00 00 e8 d3 b2 47 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 c2 68 db fe 4c 8b 3b 4c 89 fe
RSP: 0018:ffffc900039d76d8 EFLAGS: 00010202
RAX: 0000000000000000 RBX: 0000000000000008 RCX: 0000000000000046
RDX: 0000000000000000 RSI: ffffffff8d592237 RDI: ffffffff8b85e800
RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed100b1e89d2 R12: 0000000000000000
R13: dffffc0000000000 R14: ffff888058f44e68 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8881266c9000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000000000 CR3: 000000003c434000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 xtTruncate+0xecd/0x2f20 fs/jfs/jfs_xtree.c:-1
 jfs_free_zero_link+0x35b/0x4c0 fs/jfs/namei.c:759
 jfs_evict_inode+0x363/0x440 fs/jfs/inode.c:159
 evict+0x61e/0xb10 fs/inode.c:837
 txLazyCommit fs/jfs/jfs_txnmgr.c:2665 [inline]
 jfs_lazycommit+0x3ef/0xa10 fs/jfs/jfs_txnmgr.c:2734
 kthread+0x726/0x8b0 kernel/kthread.c:463
 ret_from_fork+0x51b/0xa40 arch/x86/kernel/process.c:158
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:246
 </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:1133 [inline]
RIP: 0010:folio_lock include/linux/pagemap.h:1169 [inline]
RIP: 0010:release_metapage+0x9e/0xab0 fs/jfs/jfs_metapage.c:870
Code: 04 00 00 e8 b4 04 77 fe 48 c7 c7 f3 e1 36 8d be 90 04 00 00 e8 d3 b2 47 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 c2 68 db fe 4c 8b 3b 4c 89 fe
RSP: 0018:ffffc900039d76d8 EFLAGS: 00010202
RAX: 0000000000000000 RBX: 0000000000000008 RCX: 0000000000000046
RDX: 0000000000000000 RSI: ffffffff8d592237 RDI: ffffffff8b85e800
RBP: 0000000000000001 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: ffffed100b1e89d2 R12: 0000000000000000
R13: dffffc0000000000 R14: ffff888058f44e68 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8881266c9000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000200000000000 CR3: 000000003c434000 CR4: 00000000003526f0
----------------
Code disassembly (best guess):
   0:	04 00                	add    $0x0,%al
   2:	00 e8                	add    %ch,%al
   4:	b4 04                	mov    $0x4,%ah
   6:	77 fe                	ja     0x6
   8:	48 c7 c7 f3 e1 36 8d 	mov    $0xffffffff8d36e1f3,%rdi
   f:	be 90 04 00 00       	mov    $0x490,%esi
  14:	e8 d3 b2 47 fe       	call   0xfe47b2ec
  19:	2e 2e 2e 31 c0       	cs cs cs xor %eax,%eax
  1e:	49 8d 5c 24 08       	lea    0x8(%r12),%rbx
  23:	48 89 dd             	mov    %rbx,%rbp
  26:	48 c1 ed 03          	shr    $0x3,%rbp
* 2a:	42 80 7c 2d 00 00    	cmpb   $0x0,0x0(%rbp,%r13,1) <-- trapping instruction
  30:	74 08                	je     0x3a
  32:	48 89 df             	mov    %rbx,%rdi
  35:	e8 c2 68 db fe       	call   0xfedb68fc
  3a:	4c 8b 3b             	mov    (%rbx),%r15
  3d:	4c 89 fe             	mov    %r15,%rsi

Crashes (42):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2026/01/28 01:50 upstream 1f97d9dcf536 3029c699 .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/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
2026/01/28 13:53 upstream 1f97d9dcf536 004c195c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2026/01/28 00:45 upstream 1f97d9dcf536 3029c699 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2026/01/28 00:44 upstream 1f97d9dcf536 3029c699 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2026/01/28 00:41 upstream 1f97d9dcf536 3029c699 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2026/01/28 00:41 upstream 1f97d9dcf536 3029c699 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2026/01/28 00:41 upstream 1f97d9dcf536 3029c699 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2026/01/28 00:40 upstream 1f97d9dcf536 3029c699 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2026/01/26 21:33 upstream 63804fed149a a4c52dd6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2026/01/26 18:00 upstream 63804fed149a a4c52dd6 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2026/01/26 03:41 upstream 023777797472 55756628 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2026/01/26 03:03 upstream 023777797472 55756628 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2026/01/25 10:19 upstream 5dbeeb268b63 40acda8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2026/01/24 17:34 upstream 62085877ae65 40acda8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2026/01/24 16:27 upstream 62085877ae65 40acda8a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2026/01/21 18:24 upstream 6c790212c588 8fc37797 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2026/01/16 17:55 upstream 983d014aafb1 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2026/01/08 21:19 upstream 79b95d74470d d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2026/01/08 14:21 upstream f0b9d8eb98df d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2026/01/07 07:33 upstream f0b9d8eb98df d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2026/01/04 09:27 upstream aacb0a6d604a d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2025/12/31 15:01 upstream c8ebd433459b d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2025/12/30 10:25 upstream 8640b74557fc d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2025/12/25 04:43 upstream ccd1cdca5cd4 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs stack segment fault in release_metapage
2025/12/20 01:59 upstream dd9b004b7ff3 d6526ea3 .config console log report info [disk image] [vmlinux] [kernel image] 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.