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
[Documentation on labels]
Reported-by: syzbot+48bff48d621ab983e949@syzkaller.appspotmail.com
First crash: 7d08h, last: 7d06h
Bug presence (1)
Date Name Commit Repro Result
2024/12/15 upstream (ToT) 2d8308bf5b67 C [report] BUG: unable to handle kernel paging request in txBeginAnon
Similar bugs (1)
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 27 45m 211d 0/28 upstream: reported C repro on 2024/05/24 21:06

Sample crash report:
lbmIODone: I/O error in JFS log
*** Log Format Error ! ***
lmLogInit: exit(-22)
lmLogOpen: exit(-22)
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: 4301 Comm: syz-executor338 Not tainted 6.1.119-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
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 : ffff800021007240
x29: ffff800021007240 x28: ffff80001cdde108 x27: ffff80001cddd000
x26: ffff80001cdde000 x25: 0000000000000008 x24: 0000000000000150
x23: dfff800000000000 x22: 0000000000000001 x21: 0000000000000000
x20: 0000000000000040 x19: ffff8000160357a0 x18: ffff800021006f40
x17: ffff800018b6a000 x16: ffff8000083192b4 x15: ffff80001864af80
x14: 0000000084a3eeff x13: dfff800000000000 x12: ffff700004200e30
x11: 1ffff00004200e30 x10: 0000000000000004 x9 : a2506ae9d5aa6600
x8 : a2506ae9d5aa6600 x7 : 0000000000000000 x6 : 0000000000000000
x5 : ffff800018ca6bf0 x4 : 0000000000000008 x3 : ffff8000083193e4
x2 : 0000000000000001 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
 txBeginAnon+0xac/0x154
 extAlloc+0xe8/0xdec fs/jfs/jfs_extent.c:78
 jfs_get_block+0x340/0xb98 fs/jfs/inode.c:248
 __block_write_begin_int+0x340/0x13b4 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+0x278/0x55c mm/filemap.c:3845
 __generic_file_write_iter+0x168/0x388 mm/filemap.c:3973
 generic_file_write_iter+0xb8/0x2b4 mm/filemap.c:4005
 do_iter_write+0x534/0x964 fs/read_write.c:861
 vfs_writev fs/read_write.c:934 [inline]
 do_pwritev+0x1ec/0x334 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/0x168 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 97ffff65 aa1303e0 959329b1 (38776b28) 
---[ end trace 0000000000000000 ]---
----------------
Code disassembly (best guess):
   0:	aa1803e0 	mov	x0, x24
   4:	97ffff65 	bl	0xfffffffffffffd98
   8:	aa1303e0 	mov	x0, x19
   c:	959329b1 	bl	0x64ca6d0
* 10:	38776b28 	ldrb	w8, [x25, x23] <-- trapping instruction

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
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
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
* Struck through repros no longer work on HEAD.