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: 173d, last: 59d
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 Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-6.1 kernel BUG in jfs_flush_journal 1 217d 217d 0/3 auto-obsoleted due to no activity on 2024/07/26 08:47
upstream kernel BUG in jfs_flush_journal jfs 2 613d 610d 0/28 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] PREEMPT SMP KASAN PTI
CPU: 1 UID: 0 PID: 5218 Comm: syz-executor Not tainted 6.11.0-syzkaller-08833-gde5cb0dcb74c #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
RIP: 0010:jfs_flush_journal+0xeba/0xec0 fs/jfs/jfs_logmgr.c:1588
Code: e8 eb 0b 8e 08 e8 16 22 69 fe 48 c7 c7 e0 40 43 8c 48 c7 c6 e0 3b 43 8c ba 34 06 00 00 48 c7 c1 20 41 43 8c e8 a7 ff 8a 08 90 <0f> 0b 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc90003d47980 EFLAGS: 00010246
RAX: 0000000000000040 RBX: ffff88807fb4d1a8 RCX: ad6121119ef71b00
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc90003d47ab0 R08: ffffffff8174722c R09: 1ffff920007a8ecc
R10: dffffc0000000000 R11: fffff520007a8ecd R12: 1ffff920007a8f3c
R13: dffffc0000000000 R14: ffff88807fb4d000 R15: ffff88807fb4d000
FS:  0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fffc6020b20 CR3: 00000000244ae000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 jfs_umount+0x170/0x3a0 fs/jfs/jfs_umount.c:58
 jfs_put_super+0x8a/0x190 fs/jfs/super.c:194
 generic_shutdown_super+0x139/0x2d0 fs/super.c:642
 kill_block_super+0x44/0x90 fs/super.c:1696
 deactivate_locked_super+0xc4/0x130 fs/super.c:473
 cleanup_mnt+0x41f/0x4b0 fs/namespace.c:1373
 task_work_run+0x24f/0x310 kernel/task_work.c:228
 exit_task_work include/linux/task_work.h:40 [inline]
 do_exit+0xa2f/0x28e0 kernel/exit.c:939
 do_group_exit+0x207/0x2c0 kernel/exit.c:1088
 __do_sys_exit_group kernel/exit.c:1099 [inline]
 __se_sys_exit_group kernel/exit.c:1097 [inline]
 __x64_sys_exit_group+0x3f/0x40 kernel/exit.c:1097
 x64_sys_call+0x2634/0x2640 arch/x86/include/generated/asm/syscalls_64.h:232
 do_syscall_x64 arch/x86/entry/common.c:52 [inline]
 do_syscall_64+0xf3/0x230 arch/x86/entry/common.c:83
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7ffaa697def9
Code: Unable to access opcode bytes at 0x7ffaa697decf.
RSP: 002b:00007ffe61606758 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
RAX: ffffffffffffffda RBX: 00007ffaa69f0a39 RCX: 00007ffaa697def9
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000001
RBP: 0000000000000002 R08: 00007ffe616044f7 R09: 00007ffe61607a10
R10: 0000000000000000 R11: 0000000000000246 R12: 00007ffe61607a10
R13: 00007ffaa69f0a14 R14: 00005555870434a8 R15: 00007ffe61608ad0
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:jfs_flush_journal+0xeba/0xec0 fs/jfs/jfs_logmgr.c:1588
Code: e8 eb 0b 8e 08 e8 16 22 69 fe 48 c7 c7 e0 40 43 8c 48 c7 c6 e0 3b 43 8c ba 34 06 00 00 48 c7 c1 20 41 43 8c e8 a7 ff 8a 08 90 <0f> 0b 0f 1f 40 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc90003d47980 EFLAGS: 00010246
RAX: 0000000000000040 RBX: ffff88807fb4d1a8 RCX: ad6121119ef71b00
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc90003d47ab0 R08: ffffffff8174722c R09: 1ffff920007a8ecc
R10: dffffc0000000000 R11: fffff520007a8ecd R12: 1ffff920007a8f3c
R13: dffffc0000000000 R14: ffff88807fb4d000 R15: ffff88807fb4d000
FS:  0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005654dc753058 CR3: 000000005c560000 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/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
* Struck through repros no longer work on HEAD.