syzbot


kernel BUG in txUnlock

Status: upstream: reported C repro on 2023/01/01 13:47
Subsystems: jfs
[Documentation on labels]
Reported-by: syzbot+6fa8a6e778648d6afc8b@syzkaller.appspotmail.com
First crash: 530d, last: 467d
Similar bugs (4)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 kernel BUG in txUnlock origin:upstream C error 45 2h24m 376d 0/3 upstream: reported C repro on 2023/06/04 02:49
linux-4.19 kernel BUG in txUnlock jfs C error 7 495d 537d 0/1 upstream: reported C repro on 2022/12/24 18:38
upstream kernel BUG in txUnlock jfs C error 4465 49m 622d 0/27 upstream: reported C repro on 2022/10/01 14:27
linux-6.1 kernel BUG in txUnlock origin:upstream C 487 2h26m 376d 0/3 upstream: reported C repro on 2023/06/04 03:57
Fix bisection attempts (2)
Created Duration User Patch Repo Result
2023/03/05 00:43 51m bisect fix linux-4.14.y job log (0) log
2023/02/03 00:14 26m bisect fix linux-4.14.y job log (0) log

Sample crash report:
IPVS: ftp: loaded support on port[0] = 21
ERROR: (device loop0): txAbort: 
BUG at fs/jfs/jfs_txnmgr.c:939 assert(mp->nohomeok > 0)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_txnmgr.c:939!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
Modules linked in:
CPU: 0 PID: 1963 Comm: jfsCommit Not tainted 4.14.302-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/26/2022
task: ffff8880b0fc8100 task.stack: ffff8880b0fd0000
RIP: 0010:txUnlock.cold+0x24/0x72 fs/jfs/jfs_txnmgr.c:939
RSP: 0018:ffff8880b0fd7d80 EFLAGS: 00010286
RAX: 0000000000000037 RBX: ffffc900015b9090 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff878bd020 RDI: ffffed10161fafa6
RBP: ffff88809dfe92d0 R08: 0000000000000037 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000002
R13: 0000000000000000 R14: 0000000000000000 R15: dffffc0000000000
FS:  0000000000000000(0000) GS:ffff8880ba400000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000055ce5b082160 CR3: 00000000a1011000 CR4: 00000000003406f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 txLazyCommit fs/jfs/jfs_txnmgr.c:2727 [inline]
 jfs_lazycommit+0x5a6/0x8c0 fs/jfs/jfs_txnmgr.c:2777
 kthread+0x30d/0x420 kernel/kthread.c:232
 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:406
Code: 76 fa e8 3b ff ff ff e8 c3 da 4c fa 48 c7 c1 c0 c6 b6 87 ba ab 03 00 00 48 c7 c6 40 c6 b6 87 48 c7 c7 80 c6 b6 87 e8 2e b9 fa ff <0f> 0b e8 9d da 4c fa 48 c7 c1 00 c6 b6 87 ba a5 03 00 00 48 c7 
RIP: txUnlock.cold+0x24/0x72 fs/jfs/jfs_txnmgr.c:939 RSP: ffff8880b0fd7d80
---[ end trace f3217d54fe6f238d ]---

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/01/01 23:01 linux-4.14.y c4215ee4771b ab32d508 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-4-14 kernel BUG in txUnlock
2023/01/01 13:47 linux-4.14.y c4215ee4771b ab32d508 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-4-14 kernel BUG in txUnlock
* Struck through repros no longer work on HEAD.