syzbot


WARNING in btrfs_sync_log (2)

Status: upstream: reported C repro on 2023/09/09 20:33
Bug presence: origin:lts-only
[Documentation on labels]
Reported-by: syzbot+527d0ac92e795965bcf1@syzkaller.appspotmail.com
First crash: 438d, last: 41d
Bug presence (2)
Date Name Commit Repro Result
2023/09/10 linux-5.15.y (ToT) aff03380bda4 C [report] WARNING in btrfs_sync_log
2023/09/10 upstream (ToT) 535a265d7f0d C Didn't crash
Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-4.19 WARNING in btrfs_sync_log btrfs 1 653d 653d 0/1 upstream: reported on 2023/02/06 19:49
upstream WARNING in btrfs_sync_log btrfs C error inconclusive 6 256d 766d 25/28 fixed on 2024/05/22 09:57
linux-5.15 WARNING in btrfs_sync_log 3 577d 589d 0/3 auto-obsoleted due to no activity on 2023/08/21 23:02
Last patch testing requests (1)
Created Duration User Patch Repo Result
2024/10/11 16:47 11m retest repro linux-5.15.y report log
Fix bisection attempts (8)
Created Duration User Patch Repo Result
2024/10/10 23:44 1m fix candidate upstream error job log
2024/08/09 12:32 11m fix candidate upstream error job log
2024/07/08 00:49 1m fix candidate upstream error job log
2024/04/26 07:25 2m fix candidate upstream error job log
2024/03/20 20:32 1m fix candidate upstream error job log
2024/01/05 14:23 53m fix candidate upstream error job log
2023/11/24 08:15 1m fix candidate upstream error job log
2023/10/18 12:29 1m fix candidate upstream error job log

Sample crash report:
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
 el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
------------[ cut here ]------------
WARNING: CPU: 1 PID: 3973 at fs/btrfs/tree-log.c:3210 btrfs_sync_log+0x15f0/0x2294 fs/btrfs/tree-log.c:3210
Modules linked in:
CPU: 1 PID: 3973 Comm: syz-executor272 Not tainted 5.15.131-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/26/2023
pstate: 60400005 (nZCv daif +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
pc : btrfs_sync_log+0x15f0/0x2294 fs/btrfs/tree-log.c:3210
lr : btrfs_sync_log+0x15f0/0x2294 fs/btrfs/tree-log.c:3210
sp : ffff80001ca17300
x29: ffff80001ca17760 x28: ffff0000dbdfb160 x27: 1fffe0001b7bf62c
x26: 00000000fffffff4 x25: 0000000000000000 x24: ffff0000c789a000
x23: dfff800000000000 x22: 00000000fffffff4 x21: 0000000000000009
x20: ffff0000c789a338 x19: 00000000fffffff4 x18: 0000000000000001
x17: ff80800008334dcc x16: ffff8000119649dc x15: ffff800008334dcc
x14: 00000000ffffffff x13: ffffffffffffffff x12: 0000000000000000
x11: ff8080000832c874 x10: 0000000000000000 x9 : cad2696e4cfe3900
x8 : cad2696e4cfe3900 x7 : 0000000000000001 x6 : 0000000000000001
x5 : ffff80001ca16a78 x4 : ffff8000149dfd00 x3 : ffff80000854cdec
x2 : 0000000000000001 x1 : 0000000100000000 x0 : 0000000000000026
Call trace:
 btrfs_sync_log+0x15f0/0x2294 fs/btrfs/tree-log.c:3210
 btrfs_sync_file+0x924/0xe60 fs/btrfs/file.c:2349
 vfs_fsync_range+0x168/0x188 fs/sync.c:188
 generic_write_sync include/linux/fs.h:2913 [inline]
 btrfs_file_write_iter+0x758/0xad8 fs/btrfs/file.c:2093
 call_write_iter include/linux/fs.h:2103 [inline]
 new_sync_write fs/read_write.c:507 [inline]
 vfs_write+0x87c/0xb3c fs/read_write.c:594
 ksys_write+0x15c/0x26c fs/read_write.c:647
 __do_sys_write fs/read_write.c:659 [inline]
 __se_sys_write fs/read_write.c:656 [inline]
 __arm64_sys_write+0x7c/0x90 fs/read_write.c:656
 __invoke_syscall arch/arm64/kernel/syscall.c:38 [inline]
 invoke_syscall+0x98/0x2b8 arch/arm64/kernel/syscall.c:52
 el0_svc_common+0x138/0x258 arch/arm64/kernel/syscall.c:142
 do_el0_svc+0x58/0x14c arch/arm64/kernel/syscall.c:181
 el0_svc+0x7c/0x1f0 arch/arm64/kernel/entry-common.c:596
 el0t_64_sync_handler+0x84/0xe4 arch/arm64/kernel/entry-common.c:614
 el0t_64_sync+0x1a0/0x1a4 arch/arm64/kernel/entry.S:584
irq event stamp: 84906
hardirqs last  enabled at (84905): [<ffff80000832aa0c>] __up_console_sem+0xb4/0x100 kernel/printk/printk.c:257
hardirqs last disabled at (84906): [<ffff800011960070>] el1_dbg+0x24/0x80 arch/arm64/kernel/entry-common.c:387
softirqs last  enabled at (84880): [<ffff800008020ccc>] softirq_handle_end kernel/softirq.c:401 [inline]
softirqs last  enabled at (84880): [<ffff800008020ccc>] __do_softirq+0xb5c/0xe20 kernel/softirq.c:587
softirqs last disabled at (84849): [<ffff8000081b56a0>] do_softirq_own_stack include/asm-generic/softirq_stack.h:10 [inline]
softirqs last disabled at (84849): [<ffff8000081b56a0>] invoke_softirq kernel/softirq.c:439 [inline]
softirqs last disabled at (84849): [<ffff8000081b56a0>] __irq_exit_rcu+0x28c/0x534 kernel/softirq.c:637
---[ end trace 48a262ef670547d1 ]---
BTRFS: error (device loop0) in btrfs_sync_log:3210: errno=-12 Out of memory
BTRFS info (device loop0): forced readonly

Crashes (4):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2023/09/09 21:05 linux-5.15.y aff03380bda4 6654cf89 .config console log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-linux-5-15-kasan-arm64 WARNING in btrfs_sync_log
2023/11/22 09:53 linux-5.15.y 2a910f4af54d cb976f63 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 WARNING in btrfs_sync_log
2023/09/24 18:33 linux-5.15.y b911329317b4 0b6a67ac .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 WARNING in btrfs_sync_log
2023/09/09 20:32 linux-5.15.y aff03380bda4 6654cf89 .config console log report info [disk image] [vmlinux] [kernel image] ci2-linux-5-15-kasan-arm64 WARNING in btrfs_sync_log
* Struck through repros no longer work on HEAD.