Message-ID: <000000000000dc4656062058a165@google.com>
Date: Fri, 23 Aug 2024 05:08:25 -0700
From: syzbot <syzbot+d7d1fc7e21835ca19219@...kaller.appspotmail.com>
To: clm@...com, dsterba@...e.com, josef@...icpanda.com, 
	linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org, 
	syzkaller-bugs@...glegroups.com
Subject: [syzbot] [btrfs?] WARNING in __btrfs_check_leaf

Hello,

syzbot found the following issue on:

HEAD commit:    872cf28b8df9 Merge tag 'platform-drivers-x86-v6.11-4' of g..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=154c5825980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=4fc2afd52fd008bb
dashboard link: https://syzkaller.appspot.com/bug?extid=d7d1fc7e21835ca19219
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c63409516c62/disk-872cf28b.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/79b2b8c52d3a/vmlinux-872cf28b.xz
kernel image: https://storage.googleapis.com/syzbot-assets/27cb9df9c339/bzImage-872cf28b.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+d7d1fc7e21835ca19219@...kaller.appspotmail.com

------------[ cut here ]------------
WARNING: CPU: 0 PID: 6069 at fs/btrfs/tree-checker.c:1545 check_extent_item fs/btrfs/tree-checker.c:1545 [inline]
WARNING: CPU: 0 PID: 6069 at fs/btrfs/tree-checker.c:1545 check_leaf_item fs/btrfs/tree-checker.c:1880 [inline]
WARNING: CPU: 0 PID: 6069 at fs/btrfs/tree-checker.c:1545 __btrfs_check_leaf+0x3544/0x6410 fs/btrfs/tree-checker.c:2039
Modules linked in:
CPU: 0 UID: 0 PID: 6069 Comm: syz-executor Not tainted 6.11.0-rc4-syzkaller-00033-g872cf28b8df9 #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024
RIP: 0010:check_extent_item fs/btrfs/tree-checker.c:1545 [inline]
RIP: 0010:check_leaf_item fs/btrfs/tree-checker.c:1880 [inline]
RIP: 0010:__btrfs_check_leaf+0x3544/0x6410 fs/btrfs/tree-checker.c:2039
Code: 83 d4 00 00 00 e8 cc ba c4 fd 48 8b 44 24 58 48 89 84 24 f8 00 00 00 0f b6 44 24 68 41 89 c6 e9 2a fa ff ff e8 ad ba c4 fd 90 <0f> 0b 90 e9 d6 fd ff ff 89 d9 80 e1 07 80 c1 03 38 c1 0f 8c 8a fb
RSP: 0018:ffffc900043467c0 EFLAGS: 00010293
RAX: ffffffff83ced003 RBX: 0000000000000000 RCX: ffff88802a168000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffc90004346dd8 R08: ffffffff83cecc97 R09: ffffffff83cecb50
R10: 0000000000000005 R11: ffff88802a168000 R12: dffffc0000000000
R13: 0000000000000fc7 R14: ffff888068f640bc R15: 0000000000000005
FS:  000055557e0c7500(0000) GS:ffff8880b9200000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f94d9b15f40 CR3: 00000000655da000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 btrfs_check_leaf+0x16/0x40 fs/btrfs/tree-checker.c:2055
 btree_csum_one_bio+0x41a/0x890 fs/btrfs/disk-io.c:299
 btrfs_bio_csum fs/btrfs/bio.c:538 [inline]
 btrfs_submit_chunk fs/btrfs/bio.c:741 [inline]
 btrfs_submit_bio+0x1140/0x1920 fs/btrfs/bio.c:772
 submit_eb_page fs/btrfs/extent_io.c:2008 [inline]
 btree_write_cache_pages+0x1200/0x1b10 fs/btrfs/extent_io.c:2058
 do_writepages+0x35d/0x870 mm/page-writeback.c:2683
 filemap_fdatawrite_wbc+0x125/0x180 mm/filemap.c:397
 __filemap_fdatawrite_range mm/filemap.c:430 [inline]
 filemap_fdatawrite_range+0x120/0x180 mm/filemap.c:448
 btrfs_write_marked_extents+0x27d/0x450 fs/btrfs/transaction.c:1152
 btrfs_write_and_wait_transaction fs/btrfs/transaction.c:1260 [inline]
 btrfs_commit_transaction+0x1de1/0x3740 fs/btrfs/transaction.c:2522
 sync_filesystem+0x1c8/0x230 fs/sync.c:66
 generic_shutdown_super+0x72/0x2d0 fs/super.c:621
 kill_anon_super+0x3b/0x70 fs/super.c:1237
 btrfs_kill_super+0x41/0x50 fs/btrfs/super.c:2121
 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
 resume_user_mode_work include/linux/resume_user_mode.h:50 [inline]
 exit_to_user_mode_loop kernel/entry/common.c:114 [inline]
 exit_to_user_mode_prepare include/linux/entry-common.h:328 [inline]
 __syscall_exit_to_user_mode_work kernel/entry/common.c:207 [inline]
 syscall_exit_to_user_mode+0x168/0x370 kernel/entry/common.c:218
 do_syscall_64+0x100/0x230 arch/x86/entry/common.c:89
 entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7f08f8b7b1a7
Code: a8 ff ff ff f7 d8 64 89 01 48 83 c8 ff c3 0f 1f 44 00 00 31 f6 e9 09 00 00 00 66 0f 1f 84 00 00 00 00 00 b8 a6 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 01 c3 48 c7 c2 a8 ff ff ff f7 d8 64 89 02 b8
RSP: 002b:00007ffe63317018 EFLAGS: 00000246 ORIG_RAX: 00000000000000a6
RAX: 0000000000000000 RBX: 0000000000000000 RCX: 00007f08f8b7b1a7
RDX: 0000000000000000 RSI: 0000000000000009 RDI: 00007ffe633170d0
RBP: 00007ffe633170d0 R08: 0000000000000000 R09: 0000000000000000
R10: 00000000ffffffff R11: 0000000000000246 R12: 00007ffe63318150
R13: 00007f08f8be77b4 R14: 0000000000022fcb R15: 00007ffe63318190
 </TASK>


---
This report is generated by a bot. It may contain errors.
See https://goo.gl/tpsmEJ for more information about syzbot.
syzbot engineers can be reached at syzkaller@...glegroups.com.

syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

Powered by blists - more mailing lists