syzbot


kernel BUG in txEnd

Status: fixed on 2024/01/30 15:47
Subsystems: jfs
[Documentation on labels]
Reported-by: syzbot+3699edf4da1e736b317b@syzkaller.appspotmail.com
Fix commit: 6f861765464f fs: Block writes to mounted block devices
First crash: 312d, last: 97d
Cause bisection: the issue happens on the oldest tested release (bisect log)
Crash: kernel BUG in txEnd (log)
Repro: C syz .config
  
Fix bisection: fixed by (bisect log) :
commit 6f861765464f43a71462d52026fbddfc858239a5
Author: Jan Kara <jack@suse.cz>
Date: Wed Nov 1 17:43:10 2023 +0000

  fs: Block writes to mounted block devices

  
Discussions (2)
Title Replies (including bot) Last reply
Re: [syzbot] [jfs?] kernel BUG in txEnd (2) 1 (1) 2024/02/20 03:00
[syzbot] [jfs?] kernel BUG in txEnd 1 (3) 2024/01/15 11:30
Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream kernel BUG in txEnd (2) jfs C 2 29d 73d 0/26 upstream: reported C repro on 2024/02/13 15:23
linux-6.1 kernel BUG in txEnd origin:upstream C 1 23d 224d 0/3 upstream: reported C repro on 2023/09/16 10:44
linux-5.15 kernel BUG in txEnd origin:upstream C 1 8d21h 264d 0/3 upstream: reported C repro on 2023/08/06 15:29
Last patch testing requests (8)
Created Duration User Patch Repo Result
2024/01/11 10:16 23m retest repro upstream OK log
2023/12/12 13:38 13m retest repro upstream report log
2023/11/28 04:22 14m retest repro upstream report log
2023/11/28 04:22 20m retest repro linux-next OK log
2023/11/02 08:28 11m retest repro upstream report log
2023/10/03 11:10 13m retest repro upstream report log
2023/09/15 18:18 15m retest repro linux-next report log
2023/08/24 06:10 43m retest repro upstream report log
Fix bisection attempts (2)
Created Duration User Patch Repo Result
2024/01/12 20:28 4h59m bisect fix upstream job log (1)
2023/07/25 01:39 2h52m bisect fix upstream job log (0) log
Cause bisection attempts (2)
Created Duration User Patch Repo Result
2023/08/26 22:22 8h17m bisect upstream job log (0) log
2023/06/20 12:14 8h25m bisect upstream error job log (0)
marked invalid by nogikh@google.com

Sample crash report:
ERROR: (device loop0): remounting filesystem as read-only
BUG at fs/jfs/jfs_txnmgr.c:528 assert(tblk->next == 0)
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_txnmgr.c:528!
invalid opcode: 0000 [#1] PREEMPT SMP KASAN
CPU: 0 PID: 5054 Comm: syz-executor238 Not tainted 6.7.0-syzkaller-12824-g9d64bf433c53 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 11/17/2023
RIP: 0010:txEnd+0x583/0x5a0 fs/jfs/jfs_txnmgr.c:528
Code: e9 59 fb ff ff e8 1d 54 87 fe 48 c7 c1 00 71 0b 8b ba 10 02 00 00 48 c7 c6 80 6b 0b 8b 48 c7 c7 c0 6b 0b 8b e8 2e 17 6a fe 90 <0f> 0b 48 89 ef e8 f3 b7 de fe e9 40 fd ff ff e8 c9 b7 de fe e9 2e
RSP: 0018:ffffc900030ff818 EFLAGS: 00010282
RAX: 0000000000000036 RBX: ffffc90002641110 RCX: ffffffff8169e3f9
RDX: 0000000000000000 RSI: ffffffff816a68c2 RDI: 0000000000000005
RBP: 0000000000000001 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000039 R12: ffff888020beb000
R13: 0000000000000001 R14: ffffffff8d73fa40 R15: ffffc90002641112
FS:  0000555556b23380(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3afa795ed8 CR3: 000000002b779000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 jfs_truncate_nolock+0x1f5/0x2f0 fs/jfs/inode.c:391
 jfs_truncate+0xeb/0x170 fs/jfs/inode.c:412
 jfs_setattr+0x2ca/0x760 fs/jfs/file.c:119
 notify_change+0x742/0x11c0 fs/attr.c:499
 do_truncate+0x15c/0x220 fs/open.c:66
 handle_truncate fs/namei.c:3299 [inline]
 do_open fs/namei.c:3645 [inline]
 path_openat+0x24b6/0x2990 fs/namei.c:3798
 do_filp_open+0x1de/0x430 fs/namei.c:3825
 do_sys_openat2+0x176/0x1e0 fs/open.c:1404
 do_sys_open fs/open.c:1419 [inline]
 __do_sys_open fs/open.c:1427 [inline]
 __se_sys_open fs/open.c:1423 [inline]
 __x64_sys_open+0x154/0x1e0 fs/open.c:1423
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xd3/0x250 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x63/0x6b
RIP: 0033:0x7f23295aea59
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 17 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffd2b987868 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 0000000000000000 RCX: 00007f23295aea59
RDX: 0000000000000000 RSI: 000000000014527e RDI: 0000000020000040
RBP: 00007f23296275f0 R08: 0000000000005dea R09: 0000555556b244c0
R10: 00007ffd2b987730 R11: 0000000000000246 R12: 00007ffd2b987890
R13: 00007ffd2b987ab8 R14: 431bde82d7b634db R15: 00007f23295f703b
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:txEnd+0x583/0x5a0 fs/jfs/jfs_txnmgr.c:528
Code: e9 59 fb ff ff e8 1d 54 87 fe 48 c7 c1 00 71 0b 8b ba 10 02 00 00 48 c7 c6 80 6b 0b 8b 48 c7 c7 c0 6b 0b 8b e8 2e 17 6a fe 90 <0f> 0b 48 89 ef e8 f3 b7 de fe e9 40 fd ff ff e8 c9 b7 de fe e9 2e
RSP: 0018:ffffc900030ff818 EFLAGS: 00010282
RAX: 0000000000000036 RBX: ffffc90002641110 RCX: ffffffff8169e3f9
RDX: 0000000000000000 RSI: ffffffff816a68c2 RDI: 0000000000000005
RBP: 0000000000000001 R08: 0000000000000005 R09: 0000000000000000
R10: 0000000000000001 R11: 0000000000000039 R12: ffff888020beb000
R13: 0000000000000001 R14: ffffffff8d73fa40 R15: ffffc90002641112
FS:  0000555556b23380(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f3afa795ed8 CR3: 000000002b779000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400

Crashes (6):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2024/01/20 17:38 upstream 9d64bf433c53 9bd8dcda .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-selinux-root kernel BUG in txEnd
2023/11/14 03:57 upstream b85ea95d0864 cb976f63 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-smack-root kernel BUG in txEnd
2023/06/20 11:14 upstream 692b7dc87ca6 09ffe269 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-kasan-gce-root kernel BUG in txEnd
2023/06/20 12:04 upstream 692b7dc87ca6 09ffe269 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs kernel BUG in txEnd
2023/08/31 17:52 linux-next a47fc304d2b6 84803932 .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci-upstream-linux-next-kasan-gce-root kernel BUG in txEnd
2023/06/20 10:57 upstream 692b7dc87ca6 09ffe269 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root kernel BUG in txEnd
* Struck through repros no longer work on HEAD.