syzbot

 sign-in | mailing list | source | docs
🐞 Open [543] 🐞 Fixed [32] 🐞 Invalid [296] ⬇ Missing Backports [44] 📈 Kernel Health 📈 Bug Lifetimes 📈 Fuzzing 📈 Crashes 💬 Send us feedback

BUG: unable to handle kernel paging request in txBegin

Status: upstream: reported C repro on 2023/03/21 10:23
Bug presence: origin:upstream
Labels: missing-backport
[Documentation on labels]
Reported-by: syzbot+56a9533cc5dbe135edd8@syzkaller.appspotmail.com
First crash: 401d, last: 287d
Fix bisection: failed (error log, bisect log)
  
▶ ▼ Bug presence (3)
Date Name Commit Repro Result
2023/07/13 linux-5.15.y (ToT) d54cfc420586 C [report] BUG: unable to handle kernel paging request in txBegin
2023/05/10 upstream (ToT) ad2fd53a7870 C [report] BUG: unable to handle kernel paging request in txBegin
2023/07/13 upstream (ToT) eb26cbb1a754 C Didn't crash
▶ ▼ Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 BUG: unable to handle kernel paging request in txBegin origin:upstream C 4 12d 401d 0/3 upstream: reported C repro on 2023/03/21 08:56
upstream KASAN: null-ptr-deref Read in txBegin jfs C error 30 297d 431d 23/26 fixed on 2023/10/12 12:48
linux-4.14 general protection fault in txBegin jfs 1 481d 481d 0/1 upstream: reported on 2022/12/30 21:46
▶ ▼ Fix bisection attempts (7)
Created Duration User Patch Repo Result
2024/03/25 23:42 1h40m fix candidate upstream error job log (0)
2024/02/22 22:32 20m fix candidate upstream error job log (0)
2024/01/09 17:59 24m fix candidate upstream error job log (0)
2023/12/10 11:45 0m fix candidate upstream error job log (0)
2023/10/11 17:04 0m fix candidate upstream error job log (0)
2023/09/24 00:54 4m bisect fix linux-5.15.y error job log (0)
2023/04/20 21:33 47m bisect fix linux-5.15.y job log (0) log

Sample crash report:
loop0: detected capacity change from 0 to 32768
find_entry called with index = 0
read_mapping_page failed!
ERROR: (device loop0): txAbort: 
Unable to handle kernel paging request at virtual address dfff800000000008
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: 96000006 [#1] PREEMPT SMP
Modules linked in:
CPU: 0 PID: 4068 Comm: syz-executor375 Not tainted 5.15.103-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
pstate: 80400005 (Nzcv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : arch_test_bit include/asm-generic/bitops/non-atomic.h:118 [inline]
pc : txBegin+0x138/0x5e0 fs/jfs/jfs_txnmgr.c:366
lr : txBegin+0x104/0x5e0 fs/jfs/jfs_txnmgr.c:357
sp : ffff80001ce47840
x29: ffff80001ce47860 x28: dfff800000000000 x27: ffff80001ce47920
x26: 1ffff000029e19cc x25: 0000000000000040 x24: 0000000000000000
x23: ffff800014f18020 x22: ffff0000c1c2a630 x21: 0000000000000150
x20: 0000000000000008 x19: 0000000000000000 x18: 0000000000000000
x17: ff8080000a6111e0 x16: ffff800008307744 x15: ffff80000a6111e0
x14: 1ffff0000293806a x13: ffffffffffffffff x12: 0000000000000000
x11: ff808000098e5910 x10: 0000000000000000 x9 : ffff0000c82f3580
x8 : 1ffff000029e19cc x7 : ffff8000098e58e4 x6 : 0000000000000000
x5 : 0000000000000000 x4 : 0000000000000001 x3 : ffff800008307874
x2 : 0000000000000001 x1 : 0000000000000000 x0 : 0000000000000000
Call trace:
 txBegin+0x138/0x5e0 fs/jfs/jfs_txnmgr.c:362
 jfs_link+0x1ac/0x560 fs/jfs/namei.c:802
 vfs_link+0x598/0x74c fs/namei.c:4486
 do_linkat+0x2f4/0x898 fs/namei.c:4557
 __do_sys_linkat fs/namei.c:4585 [inline]
 __se_sys_linkat fs/namei.c:4582 [inline]
 __arm64_sys_linkat+0xe4/0x100 fs/namei.c:4582
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
 el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
Code: 9400012e aa1703e0 95990181 350002f8 (387c6a88) 
---[ end trace ae92164d26e2cc05 ]---
----------------
Code disassembly (best guess):
   0:	9400012e 	bl	0x4b8
   4:	aa1703e0 	mov	x0, x23
   8:	95990181 	bl	0x664060c
   c:	350002f8 	cbnz	w24, 0x68
* 10:	387c6a88 	ldrb	w8, [x20, x28] <-- trapping instruction

Crashes (3):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/03/21 10:23 linux-5.15.y 8020ae3c051d 7939252e .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in txBegin
2023/05/18 18:19 linux-5.15.y 9d6bde853685 3bb7af1d .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 BUG: unable to handle kernel paging request in txBegin
2023/06/09 01:41 linux-5.15.y d7af3e5ba454 058b3a5a .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan KASAN: null-ptr-deref Read in txBegin
* Struck through repros no longer work on HEAD.