syzbot


kernel BUG in txAbort

Status: upstream: reported C repro on 2025/08/22 17:11
Bug presence: origin:upstream
[Documentation on labels]
Reported-by: syzbot+d1e49beb0590f426750b@syzkaller.appspotmail.com
First crash: 63d, last: 1d00h
Bug presence (1)
Date Name Commit Repro Result
2025/09/16 upstream (ToT) 46a51f4f5eda C [report] kernel BUG in txAbort
Similar bugs (4)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 kernel BUG in txAbort origin:upstream -1 C error 51 17d 544d 0/3 upstream: reported C repro on 2024/04/28 14:11
linux-6.1 kernel BUG in txAbort -1 1 884d 884d 0/3 auto-obsoleted due to no activity on 2023/09/01 20:47
linux-6.1 kernel BUG in txAbort (2) origin:upstream -1 C 58 10d 552d 0/3 upstream: reported C repro on 2024/04/20 09:23
upstream kernel BUG in txUnlock jfs -1 C error 34260 1h51m 1119d 0/29 upstream: reported C repro on 2022/10/01 14:27
Fix bisection attempts (1)
Created Duration User Patch Repo Result
2025/10/24 01:57 1h40m bisect fix linux-6.6.y OK (0) job log log

Sample crash report:
ERROR: (device loop0): diWrite: ixpxd invalid
BUG at fs/jfs/jfs_txnmgr.c:2795 assert(mp->nohomeok)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_txnmgr.c:2795!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 5990 Comm: syz.0.21 Not tainted syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:LogSyncRelease fs/jfs/jfs_txnmgr.c:2795 [inline]
RIP: 0010:txAbort+0x59a/0x5d0 fs/jfs/jfs_txnmgr.c:2621
Code: fe e9 3e ff ff ff e8 f5 60 84 fe 48 c7 c7 00 16 e4 8a 48 c7 c6 f9 11 e4 8a ba eb 0a 00 00 48 c7 c1 e0 29 e4 8a e8 d6 9b 61 07 <0f> 0b e8 cf 60 84 fe 48 c7 c7 00 16 e4 8a 48 c7 c6 f9 11 e4 8a ba
RSP: 0018:ffffc900035c7958 EFLAGS: 00010246
RAX: 0000000000000034 RBX: 0000000000000003 RCX: dbfb246968b87300
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffc900035c7667 R09: 1ffff920006b8ecc
R10: dffffc0000000000 R11: fffff520006b8ecd R12: 000000000000001b
R13: ffff88807f0300f8 R14: dffffc0000000000 R15: 0000000000000000
FS:  00007fdcf45fe6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055bf886d4950 CR3: 00000000728b1000 CR4: 00000000003506f0
Call Trace:
 <TASK>
 txCommit+0x4543/0x5250 fs/jfs/jfs_txnmgr.c:1354
 jfs_mkdir+0x833/0xa30 fs/jfs/namei.c:290
 vfs_mkdir+0x296/0x440 fs/namei.c:4113
 do_mkdirat+0x1d4/0x440 fs/namei.c:4136
 __do_sys_mkdirat fs/namei.c:4151 [inline]
 __se_sys_mkdirat fs/namei.c:4149 [inline]
 __x64_sys_mkdirat+0x89/0xa0 fs/namei.c:4149
 do_syscall_x64 arch/x86/entry/common.c:51 [inline]
 do_syscall_64+0x55/0xb0 arch/x86/entry/common.c:81
 entry_SYSCALL_64_after_hwframe+0x68/0xd2
RIP: 0033:0x7fdcf4f8d417
Code: 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 b8 02 01 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fdcf45fde68 EFLAGS: 00000246 ORIG_RAX: 0000000000000102
RAX: ffffffffffffffda RBX: 00007fdcf45fdef0 RCX: 00007fdcf4f8d417
RDX: 00000000000001ff RSI: 0000200000000240 RDI: 00000000ffffff9c
RBP: 0000200000000200 R08: 00002000000000c0 R09: 0000000000000000
R10: 0000200000000200 R11: 0000000000000246 R12: 0000200000000240
R13: 00007fdcf45fdeb0 R14: 0000000000000000 R15: 0000000000000000
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:LogSyncRelease fs/jfs/jfs_txnmgr.c:2795 [inline]
RIP: 0010:txAbort+0x59a/0x5d0 fs/jfs/jfs_txnmgr.c:2621
Code: fe e9 3e ff ff ff e8 f5 60 84 fe 48 c7 c7 00 16 e4 8a 48 c7 c6 f9 11 e4 8a ba eb 0a 00 00 48 c7 c1 e0 29 e4 8a e8 d6 9b 61 07 <0f> 0b e8 cf 60 84 fe 48 c7 c7 00 16 e4 8a 48 c7 c6 f9 11 e4 8a ba
RSP: 0018:ffffc900035c7958 EFLAGS: 00010246
RAX: 0000000000000034 RBX: 0000000000000003 RCX: dbfb246968b87300
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffc900035c7667 R09: 1ffff920006b8ecc
R10: dffffc0000000000 R11: fffff520006b8ecd R12: 000000000000001b
R13: ffff88807f0300f8 R14: dffffc0000000000 R15: 0000000000000000
FS:  00007fdcf45fe6c0(0000) GS:ffff8880b8e00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055bf886d4950 CR3: 00000000728b1000 CR4: 00000000003506f0

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/09/15 06:06 linux-6.6.y 60a9e718726f e2beed91 .config console log report syz / log C [disk image] [vmlinux] [kernel image] [mounted in repro (corrupt fs)] ci2-linux-6-6-kasan kernel BUG in txAbort
2025/09/16 23:51 linux-6.6.y 60a9e718726f e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan kernel BUG in txAbort
2025/09/15 04:55 linux-6.6.y 60a9e718726f e2beed91 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan kernel BUG in txAbort
2025/08/22 17:11 linux-6.6.y bb9c90ab9c5a bf27483f .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-6-6-kasan kernel BUG in txAbort
* Struck through repros no longer work on HEAD.