syzbot


BUG: unable to handle kernel paging request in txBeginAnon

Status: upstream: reported C repro on 2024/12/14 17:41
Bug presence: origin:upstream
Labels: missing-backport
[Documentation on labels]
Reported-by: syzbot+48bff48d621ab983e949@syzkaller.appspotmail.com
First crash: 200d, last: 11d
Fix bisection: failed (error log, bisect log)
  
Bug presence (3)
Date Name Commit Repro Result
2025/04/30 linux-6.1.y (ToT) 535ec20c5027 C [report] BUG: unable to handle kernel paging request in txBeginAnon
2024/12/15 upstream (ToT) 2d8308bf5b67 C [report] BUG: unable to handle kernel paging request in txBeginAnon
2025/04/30 upstream (ToT) 8bac8898fe39 C Didn't crash
Similar bugs (2)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream BUG: unable to handle kernel paging request in txBeginAnon jfs C inconclusive 43 115d 404d 28/29 fixed on 2025/06/10 16:19
linux-5.15 BUG: unable to handle kernel paging request in txBeginAnon missing-backport origin:upstream C error 15 2d10h 180d 0/3 upstream: reported C repro on 2025/01/04 14:54
Fix bisection attempts (3)
Created Duration User Patch Repo Result
2025/06/11 19:14 46m fix candidate upstream error job log
2025/02/25 20:21 1h10m bisect fix linux-6.1.y error job log
2025/01/25 14:19 1h53m bisect fix linux-6.1.y OK (0) job log log

Sample crash report:
 ... Log Wrap ... Log Wrap ... Log Wrap ...
 ... Log Wrap ... Log Wrap ... Log Wrap ...
jfs_dirty_inode called on read-only volume
Is remount racy?
Unable to handle kernel paging request at virtual address dfff800000000008
KASAN: null-ptr-deref in range [0x0000000000000040-0x0000000000000047]
Mem abort info:
  ESR = 0x0000000096000006
  EC = 0x25: DABT (current EL), IL = 32 bits
  SET = 0, FnV = 0
  EA = 0, S1PTW = 0
  FSC = 0x06: level 2 translation fault
Data abort info:
  ISV = 0, ISS = 0x00000006
  CM = 0, WnR = 0
[dfff800000000008] address between user and kernel address ranges
Internal error: Oops: 0000000096000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 1 PID: 4294 Comm: syz-executor238 Not tainted 6.1.141-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/07/2025
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : generic_test_bit include/asm-generic/bitops/generic-non-atomic.h:128 [inline]
pc : txBeginAnon+0xac/0x154 fs/jfs/jfs_txnmgr.c:465
lr : spin_lock include/linux/spinlock.h:351 [inline]
lr : txBeginAnon+0x78/0x154 fs/jfs/jfs_txnmgr.c:458
sp : ffff8000207f72a0
x29: ffff8000207f72a0 x28: ffff80001c4150e8 x27: ffff80001c414000
x26: ffff80001c415000 x25: 0000000000000008 x24: 0000000000000150
x23: dfff800000000000 x22: 0000000000000001 x21: 0000000000000000
x20: 0000000000000040 x19: ffff8000156308a0 x18: 0000000000000000
x17: ffff8000181a1000 x16: ffff8000082e6f68 x15: ffff800017c81fc0
x14: ffff0000d24bddd8 x13: ffff0000d24bde50 x12: ffff7000040fee3c
x11: 1ffff000040fee3c x10: 0000000000000004 x9 : fb9a1ada2f908a00
x8 : fb9a1ada2f908a00 x7 : 0000000000000000 x6 : 0000000000000000
x5 : 0000000000000020 x4 : 0000000000000000 x3 : ffff8000082e7088
x2 : 0000000000000001 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
 spin_lock include/linux/spinlock.h:351 [inline]
 txBeginAnon+0xac/0x154 fs/jfs/jfs_txnmgr.c:-1
 extAlloc+0xe4/0xd64 fs/jfs/jfs_extent.c:78
 jfs_get_block+0x2bc/0x8b8 fs/jfs/inode.c:248
 __block_write_begin_int+0x34c/0x13b8 fs/buffer.c:1991
 __block_write_begin fs/buffer.c:2041 [inline]
 block_write_begin+0x98/0x11c fs/buffer.c:2102
 jfs_write_begin+0x44/0x88 fs/jfs/inode.c:304
 generic_perform_write+0x230/0x4b0 mm/filemap.c:3846
 __generic_file_write_iter+0x168/0x37c mm/filemap.c:3974
 generic_file_write_iter+0xb4/0x2b0 mm/filemap.c:4006
 do_iter_readv_writev fs/read_write.c:-1 [inline]
 do_iter_write+0x530/0x91c fs/read_write.c:861
 vfs_writev fs/read_write.c:934 [inline]
 do_pwritev+0x1c8/0x2fc fs/read_write.c:1031
 __do_sys_pwritev2 fs/read_write.c:1090 [inline]
 __se_sys_pwritev2 fs/read_write.c:1081 [inline]
 __arm64_sys_pwritev2+0xd4/0x108 fs/read_write.c:1081
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2bc arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:140
 do_el0_svc+0x58/0x13c arch/arm64/kernel/syscall.c:204
 el0_svc+0x58/0x138 arch/arm64/kernel/entry-common.c:637
 el0t_64_sync_handler+0x84/0xf0 arch/arm64/kernel/entry-common.c:655
 el0t_64_sync+0x18c/0x190 arch/arm64/kernel/entry.S:585
Code: aa1803e0 97ffff75 aa1303e0 959d66f8 (38776b28) 
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
   0:	aa1803e0 	mov	x0, x24
   4:	97ffff75 	bl	0xfffffffffffffdd8
   8:	aa1303e0 	mov	x0, x19
   c:	959d66f8 	bl	0x6759bec
* 10:	38776b28 	ldrb	w8, [x25, x23] <-- trapping instruction

Crashes (13):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/06/22 16:08 linux-6.1.y 58485ff1a74f d6cdfb8a .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 BUG: unable to handle kernel paging request in txBeginAnon
2025/04/27 03:18 linux-6.1.y 535ec20c5027 c6b4fb39 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-1-kasan-arm64 BUG: unable to handle kernel paging request in txBeginAnon
2024/12/14 19:34 linux-6.1.y e4d90d63d385 7cbfbb3a .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan-arm64 BUG: unable to handle kernel paging request in txBeginAnon
2024/12/14 18:57 linux-6.1.y e4d90d63d385 7cbfbb3a .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan-arm64 BUG: unable to handle kernel paging request in txBeginAnon
2024/12/14 18:20 linux-6.1.y e4d90d63d385 7cbfbb3a .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-6-1-kasan-arm64 BUG: unable to handle kernel paging request in txBeginAnon
2025/04/27 03:28 linux-6.1.y 535ec20c5027 c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 BUG: unable to handle kernel paging request in txBeginAnon
2025/04/27 03:28 linux-6.1.y 535ec20c5027 c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 BUG: unable to handle kernel paging request in txBeginAnon
2025/04/27 02:57 linux-6.1.y 535ec20c5027 c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 BUG: unable to handle kernel paging request in txBeginAnon
2025/04/27 02:55 linux-6.1.y 535ec20c5027 c6b4fb39 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 BUG: unable to handle kernel paging request in txBeginAnon
2024/12/14 17:41 linux-6.1.y e4d90d63d385 7cbfbb3a .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan-arm64 BUG: unable to handle kernel paging request in txBeginAnon
2025/05/10 18:41 linux-6.1.y 02b72ccb5f9d 77908e5f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan KASAN: null-ptr-deref Read in txBeginAnon
2025/05/05 00:26 linux-6.1.y b6736e03756f b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan KASAN: null-ptr-deref Read in txBeginAnon
2025/05/05 00:26 linux-6.1.y b6736e03756f b0714e37 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-1-kasan KASAN: null-ptr-deref Read in txBeginAnon
* Struck through repros no longer work on HEAD.