linux-kernel - [syzbot] [btrfs?] kernel BUG in btrfs_get_extent_inline_ref

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [day] [month] [year] [list]
Message-ID: <67538918.050a0220.a30f1.014a.GAE@google.com>
Date: Fri, 06 Dec 2024 15:30:32 -0800
From: syzbot <syzbot+4983e68a6d77180bfe33@...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?] kernel BUG in btrfs_get_extent_inline_ref_type

Hello,

syzbot found the following issue on:

HEAD commit:    e70140ba0d2b Get rid of 'remove_new' relic from platform d..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=156a0330580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=91c852e3d1d7c1a6
dashboard link: https://syzkaller.appspot.com/bug?extid=4983e68a6d77180bfe33
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/8a904c062768/disk-e70140ba.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/e4c464adbbce/vmlinux-e70140ba.xz
kernel image: https://storage.googleapis.com/syzbot-assets/7a1fb1b0c526/bzImage-e70140ba.xz

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

assertion failed: btrfs_fs_incompat(fs_info, SIMPLE_QUOTA), in fs/btrfs/extent-tree.c:344
------------[ cut here ]------------
kernel BUG at fs/btrfs/extent-tree.c:344!
Oops: invalid opcode: 0000 [#1] PREEMPT SMP KASAN PTI
CPU: 0 UID: 0 PID: 83 Comm: kworker/u8:5 Not tainted 6.13.0-rc1-syzkaller-00001-ge70140ba0d2b #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024
Workqueue: events_unbound btrfs_async_reclaim_metadata_space
RIP: 0010:btrfs_get_extent_inline_ref_type+0x42c/0x480 fs/btrfs/extent-tree.c:344
Code: 4d fd 90 0f 0b e8 c4 52 e6 fd 48 c7 c7 a0 b0 4a 8c 48 c7 c6 00 b1 4a 8c 48 c7 c2 c0 ae 4a 8c b9 58 01 00 00 e8 15 e3 4d fd 90 <0f> 0b e8 9d 52 e6 fd 48 c7 c7 a0 b0 4a 8c 48 c7 c6 60 b1 4a 8c 48
RSP: 0018:ffffc900015970c0 EFLAGS: 00010246
RAX: 0000000000000059 RBX: 00000000000003c5 RCX: f7095654c42f1300
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff817f070c R09: 1ffff920002b2db4
R10: dffffc0000000000 R11: fffff520002b2db5 R12: 00000000000000ac
R13: ffff888029a91a40 R14: dffffc0000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f653c3ff000 CR3: 000000002a19a000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
 <TASK>
 lookup_inline_extent_backref+0x7ad/0x1a00 fs/btrfs/extent-tree.c:882
 lookup_extent_backref fs/btrfs/extent-tree.c:1064 [inline]
 __btrfs_free_extent+0x443/0x3a10 fs/btrfs/extent-tree.c:3095
 btrfs_run_delayed_refs_for_head fs/btrfs/extent-tree.c:2007 [inline]
 __btrfs_run_delayed_refs+0x102a/0x4310 fs/btrfs/extent-tree.c:2077
 btrfs_run_delayed_refs+0xe3/0x2c0 fs/btrfs/extent-tree.c:2189
 flush_space+0x2f7/0xcf0
 btrfs_async_reclaim_metadata_space+0x28e/0x350 fs/btrfs/space-info.c:1105
 process_one_work kernel/workqueue.c:3229 [inline]
 process_scheduled_works+0xa66/0x1840 kernel/workqueue.c:3310
 worker_thread+0x870/0xd30 kernel/workqueue.c:3391
 kthread+0x2f0/0x390 kernel/kthread.c:389
 ret_from_fork+0x4b/0x80 arch/x86/kernel/process.c:147
 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244
 </TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:btrfs_get_extent_inline_ref_type+0x42c/0x480 fs/btrfs/extent-tree.c:344
Code: 4d fd 90 0f 0b e8 c4 52 e6 fd 48 c7 c7 a0 b0 4a 8c 48 c7 c6 00 b1 4a 8c 48 c7 c2 c0 ae 4a 8c b9 58 01 00 00 e8 15 e3 4d fd 90 <0f> 0b e8 9d 52 e6 fd 48 c7 c7 a0 b0 4a 8c 48 c7 c6 60 b1 4a 8c 48
RSP: 0018:ffffc900015970c0 EFLAGS: 00010246
RAX: 0000000000000059 RBX: 00000000000003c5 RCX: f7095654c42f1300
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: ffffffff817f070c R09: 1ffff920002b2db4
R10: dffffc0000000000 R11: fffff520002b2db5 R12: 00000000000000ac
R13: ffff888029a91a40 R14: dffffc0000000000 R15: 0000000000000000
FS:  0000000000000000(0000) GS:ffff8880b8600000(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f653c3ff000 CR3: 000000002a19a000 CR4: 00000000003526f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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