syzbot


kernel BUG in jfs_flush_journal (2)

Status: upstream: reported on 2024/06/04 21:13
Subsystems: jfs
[Documentation on labels]
Reported-by: syzbot+e66452054e1f161e8d29@syzkaller.appspotmail.com
First crash: 439d, last: 16d
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] [jfs?] kernel BUG in jfs_flush_journal (2) 0 (1) 2024/06/04 21:13
Similar bugs (2)
Kernel Title Rank 🛈 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 kernel BUG in jfs_flush_journal -1 1 484d 484d 0/3 auto-obsoleted due to no activity on 2024/07/26 08:47
upstream kernel BUG in jfs_flush_journal jfs -1 2 880d 877d 0/29 auto-obsoleted due to no activity on 2023/07/16 07:52

Sample crash report:
BUG at fs/jfs/jfs_logmgr.c:1588 assert(list_empty(&log->cqueue))
------------[ cut here ]------------
kernel BUG at fs/jfs/jfs_logmgr.c:1588!
Oops: invalid opcode: 0000 [#1] SMP KASAN PTI
CPU: 1 UID: 0 PID: 7338 Comm: syz.4.212 Tainted: G        W           6.16.0-syzkaller-01056-gae388edd4a8f #0 PREEMPT_{RT,(full)} 
Tainted: [W]=WARN
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
RIP: 0010:jfs_flush_journal+0xeb2/0xed0 fs/jfs/jfs_logmgr.c:1588
Code: e9 07 f6 ff ff e8 de af 89 fe 48 c7 c7 a0 8d 43 8b 48 c7 c6 a0 88 43 8b ba 34 06 00 00 48 c7 c1 e0 8d 43 8b e8 9f c9 f2 fd 90 <0f> 0b f3 0f 1e fa e8 b3 af 89 fe bf 02 00 00 00 e8 79 63 5b fe e9
RSP: 0018:ffffc90004b27b20 EFLAGS: 00010246
RAX: 0000000000000040 RBX: dffffc0000000000 RCX: c1eaf3149ee18000
RDX: ffffc9000dc5a000 RSI: 00000000000051cb RDI: 00000000000051cc
RBP: ffffc90004b27c60 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffff52000964f09 R12: 00000000000000c7
R13: ffff8880629f1218 R14: ffff8880629f1000 R15: ffff8880629f12d8
FS:  00007f9a97fe66c0(0000) GS:ffff8881269fa000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fe193891440 CR3: 000000005c06c000 CR4: 00000000003526f0
Call Trace:
 <TASK>
 jfs_umount_rw+0x75/0x130 fs/jfs/jfs_umount.c:134
 jfs_reconfigure+0x6f6/0xa00 fs/jfs/super.c:421
 reconfigure_super+0x227/0x890 fs/super.c:1077
 do_remount fs/namespace.c:3314 [inline]
 path_mount+0xd18/0xfe0 fs/namespace.c:4112
 do_mount fs/namespace.c:4133 [inline]
 __do_sys_mount fs/namespace.c:4344 [inline]
 __se_sys_mount+0x317/0x410 fs/namespace.c:4321
 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
 do_syscall_64+0xfa/0x3b0 arch/x86/entry/syscall_64.c:94
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f9a9a17e9a9
Code: ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 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 a8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f9a97fe6038 EFLAGS: 00000246 ORIG_RAX: 00000000000000a5
RAX: ffffffffffffffda RBX: 00007f9a9a3a5fa0 RCX: 00007f9a9a17e9a9
RDX: 0000000000000000 RSI: 0000200000000100 RDI: 0000000000000000
RBP: 00007f9a9a200d69 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000021 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000000 R14: 00007f9a9a3a5fa0 R15: 00007ffe01bf11f8
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:jfs_flush_journal+0xeb2/0xed0 fs/jfs/jfs_logmgr.c:1588
Code: e9 07 f6 ff ff e8 de af 89 fe 48 c7 c7 a0 8d 43 8b 48 c7 c6 a0 88 43 8b ba 34 06 00 00 48 c7 c1 e0 8d 43 8b e8 9f c9 f2 fd 90 <0f> 0b f3 0f 1e fa e8 b3 af 89 fe bf 02 00 00 00 e8 79 63 5b fe e9
RSP: 0018:ffffc90004b27b20 EFLAGS: 00010246
RAX: 0000000000000040 RBX: dffffc0000000000 RCX: c1eaf3149ee18000
RDX: ffffc9000dc5a000 RSI: 00000000000051cb RDI: 00000000000051cc
RBP: ffffc90004b27c60 R08: 0000000000000000 R09: 0000000000000000
R10: dffffc0000000000 R11: fffff52000964f09 R12: 00000000000000c7
R13: ffff8880629f1218 R14: ffff8880629f1000 R15: ffff8880629f12d8
FS:  00007f9a97fe66c0(0000) GS:ffff8881269fa000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fe193891440 CR3: 000000005c06c000 CR4: 00000000003526f0

Crashes (11):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2025/07/29 12:44 upstream ae388edd4a8f c4a95487 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in jfs_flush_journal
2025/05/01 18:59 upstream 4f79eaa2ceac 51b137cd .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in jfs_flush_journal
2025/01/20 11:33 upstream ffd294d346d1 f2cb035c .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in jfs_flush_journal
2024/12/03 04:33 upstream cdd30ebb1b9f 578925bc .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in jfs_flush_journal
2024/09/23 01:50 upstream de5cb0dcb74c 6f888b75 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in jfs_flush_journal
2024/08/21 02:45 upstream 521b1e7f4cf0 9f0ab3fb .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in jfs_flush_journal
2024/08/17 18:22 upstream e5fa841af679 dbc93b08 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in jfs_flush_journal
2024/08/03 23:04 upstream 17712b7ea075 1786a2a8 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root kernel BUG in jfs_flush_journal
2024/07/01 16:55 upstream 22a40d14b572 b294e901 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in jfs_flush_journal
2024/05/31 21:06 upstream d8ec19857b09 0c378259 .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs kernel BUG in jfs_flush_journal
2025/03/16 20:19 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci a5618886fdab e2826670 .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 kernel BUG in jfs_flush_journal
* Struck through repros no longer work on HEAD.