syzbot


WARNING in btrfs_sync_log

Status: upstream: reported C repro on 2022/10/16 20:36
Subsystems: btrfs
[Documentation on labels]
Reported-by: syzbot+4406ed3884d139266b67@syzkaller.appspotmail.com
First crash: 554d, last: 39d
Cause bisection: failed (error log, bisect log)
  
Fix bisection: the issue occurs on the latest tested release (bisect log)
  
Discussions (1)
Title Replies (including bot) Last reply
[syzbot] WARNING in btrfs_sync_log 0 (2) 2022/11/01 17:41
Similar bugs (3)
Kernel Title Repro Cause bisect Fix bisect Count Last Reported Patched Status
linux-5.15 WARNING in btrfs_sync_log (2) origin:lts-only C error 4 148d 222d 0/3 upstream: reported C repro on 2023/09/09 20:33
linux-4.19 WARNING in btrfs_sync_log btrfs 1 437d 437d 0/1 upstream: reported on 2023/02/06 19:49
linux-5.15 WARNING in btrfs_sync_log 3 361d 373d 0/3 auto-obsoleted due to no activity on 2023/08/21 23:02
Fix bisection attempts (13)
Created Duration User Patch Repo Result
2024/04/11 19:36 2h58m bisect fix upstream job log (0)
2024/03/10 08:00 1h26m bisect fix upstream job log (0) log
2024/02/01 22:25 1h20m bisect fix upstream job log (0) log
2023/12/30 03:25 1h41m bisect fix upstream job log (0) log
2023/11/29 13:30 1h18m bisect fix upstream job log (0) log
2023/10/29 01:38 1h21m bisect fix upstream job log (0) log
2023/09/27 14:23 1h29m bisect fix upstream job log (0) log
2023/07/22 07:10 3h41m bisect fix upstream job log (0) log
2023/06/10 00:22 36m bisect fix upstream job log (0) log
2023/05/10 11:35 1h00m bisect fix upstream job log (0) log
2023/04/06 22:14 47m bisect fix upstream job log (0) log
2023/03/07 21:09 1h04m bisect fix upstream job log (0) log
2023/02/05 20:21 47m bisect fix upstream job log (0) log

Sample crash report:
------------[ cut here ]------------
BTRFS: Transaction aborted (error -12)
WARNING: CPU: 0 PID: 3653 at fs/btrfs/tree-log.c:3081 btrfs_sync_log+0x1ebd/0x2d40 fs/btrfs/tree-log.c:3081
Modules linked in:
CPU: 0 PID: 3653 Comm: syz-executor166 Not tainted 6.1.0-rc2-syzkaller-00105-gb229b6ca5abb #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/11/2022
RIP: 0010:btrfs_sync_log+0x1ebd/0x2d40 fs/btrfs/tree-log.c:3081
Code: bb 8d 99 06 49 be 00 00 00 00 00 fc ff df 4c 8b 64 24 40 eb 19 e8 c3 92 ef fd 48 c7 c7 e0 11 dc 8a 89 de 31 c0 e8 13 31 b7 fd <0f> 0b b3 01 44 0f b6 c3 4c 89 e7 48 c7 c6 60 12 dc 8a ba 09 0c 00
RSP: 0018:ffffc9000402ee80 EFLAGS: 00010246
RAX: 0c3fac46eef79b00 RBX: 00000000fffffff4 RCX: ffff88807ac10000
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffffc9000402f310 R08: ffffffff816b8dfd R09: fffff52000805d89
R10: fffff52000805d89 R11: 1ffff92000805d88 R12: ffff8880736f05e8
R13: 00000000fffffff4 R14: dffffc0000000000 R15: ffff8880736f0638
FS:  00005555555c9300(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000561f344b24f0 CR3: 0000000075ec1000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 btrfs_sync_file+0xdf4/0x1140 fs/btrfs/file.c:2242
 generic_write_sync include/linux/fs.h:2883 [inline]
 btrfs_do_write_iter+0xa6f/0x1370 fs/btrfs/file.c:1975
 do_iter_write+0x6c2/0xc20 fs/read_write.c:861
 iter_file_splice_write+0x7fc/0xfc0 fs/splice.c:686
 do_splice_from fs/splice.c:764 [inline]
 direct_splice_actor+0xe6/0x1c0 fs/splice.c:931
 splice_direct_to_actor+0x4e4/0xc00 fs/splice.c:886
 do_splice_direct+0x279/0x3d0 fs/splice.c:974
 do_sendfile+0x5fb/0xf80 fs/read_write.c:1255
 __do_sys_sendfile64 fs/read_write.c:1323 [inline]
 __se_sys_sendfile64+0x14f/0x1b0 fs/read_write.c:1309
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f4524cb5fe9
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 c0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007ffdb426e408 EFLAGS: 00000246 ORIG_RAX: 0000000000000028
RAX: ffffffffffffffda RBX: 0000000000000002 RCX: 00007f4524cb5fe9
RDX: 0000000000000000 RSI: 0000000000000008 RDI: 0000000000000007
RBP: 00007ffdb426e430 R08: 0000000000000002 R09: 00007ffdb426e440
R10: 0000000080000009 R11: 0000000000000246 R12: 0000000000000009
R13: 00007f4524cfe6c0 R14: 00007ffdb426e450 R15: 0000000000000002
 </TASK>

Crashes (6):
Time Kernel Commit Syzkaller Config Log Report Syz repro C repro VM info Assets (help?) Manager Title
2022/11/01 17:40 upstream b229b6ca5abb a1d8560a .config strace log report syz C [disk image] [vmlinux] [kernel image] [mounted in repro] ci2-upstream-fs WARNING in btrfs_sync_log
2022/11/03 04:04 upstream b229b6ca5abb 08977f5d .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-kasan-gce-root WARNING in btrfs_sync_log
2022/11/01 16:42 upstream b229b6ca5abb a1d8560a .config console log report info [disk image] [vmlinux] [kernel image] ci2-upstream-fs WARNING in btrfs_sync_log
2022/10/12 20:27 upstream 493ffd6605b2 16a9c9e0 .config console log report info [disk image] [vmlinux] ci2-upstream-fs WARNING in btrfs_sync_log
2023/01/06 13:33 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 247f34f7b803 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 WARNING in btrfs_sync_log
2023/01/06 12:59 git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-kernelci 247f34f7b803 1dac8c7a .config console log report info [disk image] [vmlinux] [kernel image] ci-upstream-gce-arm64 WARNING in btrfs_sync_log
* Struck through repros no longer work on HEAD.