syzbot

 sign-in | mailing list | source | docs
🐞 Open [717]
🐞 Fixed [181]
🐞 Invalid [640]
≡ Crashes
Kernel Health Bugs/Month Bug Lifetimes Fuzzing
💬 Send us feedback

WARNING in btrfs_commit_transaction

Status: upstream: reported C repro on 2022/02/21 07:21
Subsystems: btrfs
[Documentation on labels]
Reported-by: syzbot+8e8818a1efc5f1b96f96@syzkaller.appspotmail.com
First crash: 991d, last: 619d
▶ ▼ Similar bugs (6)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
upstream WARNING in btrfs_commit_transaction btrfs C inconclusive done 3 643d 737d 22/28 fixed on 2023/02/24 13:50
linux-4.19 WARNING in btrfs_commit_transaction (2) 1 700d 700d 0/1 auto-obsoleted due to no activity on 2023/04/08 10:50
linux-6.1 WARNING in btrfs_commit_transaction origin:upstream C 16 3d09h 394d 0/3 upstream: reported C repro on 2023/10/11 08:58
linux-4.19 WARNING in btrfs_commit_transaction 1 1313d 1313d 0/1 auto-closed as invalid on 2021/08/03 10:34
linux-5.15 WARNING in btrfs_commit_transaction origin:lts-only C done 43 5d05h 571d 0/3 upstream: reported C repro on 2023/04/17 01:21
upstream WARNING in btrfs_commit_transaction (2) btrfs C done 307 1d13h 582d 0/28 upstream: reported C repro on 2023/04/06 02:24
▶ ▼ Fix bisection attempts (10)
Created Duration User Patch Repo Result
2023/02/28 07:40 30m bisect fix linux-4.14.y OK (0) job log log
2023/01/20 11:09 24m bisect fix linux-4.14.y OK (0) job log log
2022/10/27 18:06 22m bisect fix linux-4.14.y OK (0) job log log
2022/09/20 04:07 23m bisect fix linux-4.14.y OK (0) job log log
2022/08/20 19:49 21m bisect fix linux-4.14.y OK (0) job log log
2022/07/21 19:23 25m bisect fix linux-4.14.y OK (0) job log log
2022/06/21 18:48 28m bisect fix linux-4.14.y OK (0) job log log
2022/05/22 18:25 23m bisect fix linux-4.14.y OK (0) job log log
2022/04/22 17:53 31m bisect fix linux-4.14.y OK (0) job log log
2022/03/23 07:24 21m bisect fix linux-4.14.y OK (0) job log log

Sample crash report:
 submit_bio+0x234/0x390 block/blk-core.c:2303
------------[ cut here ]------------
WARNING: CPU: 0 PID: 8009 at fs/btrfs/transaction.c:1883 cleanup_transaction.cold+0x14/0x7ab fs/btrfs/transaction.c:1883
Kernel panic - not syncing: panic_on_warn set ...

 submit_bio_wait+0xe8/0x140 block/bio.c:1012
 blkdev_issue_flush+0x218/0x320 block/blk-flush.c:531
 ext4_sync_fs+0x46f/0x7e0 fs/ext4/super.c:5078
 sync_fs_one_sb fs/sync.c:80 [inline]
 sync_fs_one_sb+0xb1/0xe0 fs/sync.c:77
 iterate_supers+0x124/0x490 fs/super.c:613
 sys_sync+0x9a/0x130 fs/sync.c:115
 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
 entry_SYSCALL_64_after_hwframe+0x5e/0xd3
RIP: 0033:0x7fdebca0f759
RSP: 002b:00007ffe067d7cd8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 00000000000f4240 RCX: 00007fdebca0f759
RDX: 0000000000000ce0 RSI: 000000000000f8fe RDI: 00007ffe067d7ce0
RBP: 00007ffe067d7ce0 R08: 0000000000000001 R09: 0000000000000035
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffe067d7d20 R14: 0000000000006f86 R15: 00007ffe067d7d1c
CPU: 0 PID: 8009 Comm: syz-executor154 Not tainted 4.14.304-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/12/2023
Call Trace:
 __dump_stack lib/dump_stack.c:17 [inline]
 dump_stack+0x1b2/0x281 lib/dump_stack.c:58
 panic+0x1f9/0x42d kernel/panic.c:183
 __warn.cold+0x20/0x44 kernel/panic.c:547
 report_bug+0x208/0x250 lib/bug.c:183
 fixup_bug arch/x86/kernel/traps.c:177 [inline]
 fixup_bug arch/x86/kernel/traps.c:172 [inline]
 do_error_trap+0x195/0x2d0 arch/x86/kernel/traps.c:295
 invalid_op+0x1b/0x40 arch/x86/entry/entry_64.S:967
RIP: 0010:cleanup_transaction.cold+0x14/0x7ab fs/btrfs/transaction.c:1883
RSP: 0018:ffff8880b309fb98 EFLAGS: 00010286
RAX: 0000000000000026 RBX: ffff8880b1a3cb00 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff878bd020 RDI: ffffed1016613f69
RBP: ffff88808dfd1f18 R08: 0000000000000026 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000000 R12: 1ffff11016613f7a
R13: 00000000fffffff4 R14: ffff88808dfd1f78 R15: ffff88808dfd1f48
 btrfs_commit_transaction+0x1735/0x2210 fs/btrfs/transaction.c:2341
 btrfs_sync_fs+0xe9/0x430 fs/btrfs/super.c:1217
 sync_fs_one_sb fs/sync.c:80 [inline]
 sync_fs_one_sb+0xb1/0xe0 fs/sync.c:77
 iterate_supers+0x124/0x490 fs/super.c:613
 sys_sync+0x9a/0x130 fs/sync.c:115
 do_syscall_64+0x1d5/0x640 arch/x86/entry/common.c:292
 entry_SYSCALL_64_after_hwframe+0x5e/0xd3
RIP: 0033:0x7fdebca0f759
RSP: 002b:00007ffe067d7cd8 EFLAGS: 00000246 ORIG_RAX: 00000000000000a2
RAX: ffffffffffffffda RBX: 00000000000f4240 RCX: 00007fdebca0f759
RDX: 0000000000000ce0 RSI: 000000000000f8fe RDI: 00007ffe067d7ce0
RBP: 00007ffe067d7ce0 R08: 0000000000000001 R09: 0000000000000035
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001
R13: 00007ffe067d7d20 R14: 00007ffe067d7e20 R15: 00007fdebca4b12f
Kernel Offset: disabled
Rebooting in 86400 seconds..

Crashes (2):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/01/26 21:20 linux-4.14.y 3949d1610004 9dfcf09c .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-4-14 WARNING in btrfs_commit_transaction
2022/02/21 07:21 linux-4.14.y a35d65bedfbc 3cd800e4 .config console log report syz C ci2-linux-4-14 WARNING in btrfs_commit_transaction
* Struck through repros no longer work on HEAD.