[moderation] [btrfs?] BUG: corrupted list in btrfs_alloc_compr_folio

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: f338e7738378 Linux 7.0-rc4
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=167128da580000
kernel config: https://syzkaller.appspot.com/x/.config?x=d46eab0cfd31c214
dashboard link: https://syzkaller.appspot.com/bug?extid=e9032cb4c04d772305b3
compiler: Debian clang version 21.1.8 (++20251221033036+2078da43e25a-1~exp1~20251221153213.50), Debian LLD 21.1.8
CC: [c...@fb.com dst...@suse.com linux...@vger.kernel.org linux-...@vger.kernel.org]

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

Downloadable assets:
disk image (non-bootable): https://storage.googleapis.com/syzbot-assets/d900f083ada3/non_bootable_disk-f338e773.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/2567fb35ebfb/vmlinux-f338e773.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f9124de81ddb/bzImage-f338e773.xz

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

non-paged memory
list_del corruption. next->prev should be ffffea00010a25c8, but was ffffea00010a3788. (next=ffffea00010a3788)
------------[ cut here ]------------
kernel BUG at lib/list_debug.c:67!
Oops: invalid opcode: 0000 [#1] SMP KASAN NOPTI
CPU: 0 UID: 0 PID: 1095 Comm: kworker/u4:10 Not tainted syzkaller #0 PREEMPT(full)
Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.16.3-debian-1.16.3-2 04/01/2014
Workqueue: btrfs-delalloc btrfs_work_helper
RIP: 0010:__list_del_entry_valid_or_report+0x18a/0x190 lib/list_debug.c:65
Code: fc 13 54 fd 43 80 3c 2c 00 74 08 4c 89 ff e8 bd 06 77 fd 49 8b 56 08 48 c7 c7 40 da 27 8c 48 89 de 4c 89 f1 e8 37 47 6d fc 90 <0f> 0b cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc900056875f8 EFLAGS: 00010246
RAX: 000000000000006d RBX: ffffea00010a25c8 RCX: 5b2b99cb42e7cd00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: 0000000000000005 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffffbfff1cbd61c R12: 1ffffd40002146f2
R13: dffffc0000000000 R14: ffffea00010a3788 R15: ffffea00010a3790
FS: 0000000000000000(0000) GS:ffff88808ca55000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000020000004b000 CR3: 000000000e54c000 CR4: 0000000000352ef0
Call Trace:
<TASK>
__list_del_entry_valid include/linux/list.h:132 [inline]
__list_del_entry include/linux/list.h:223 [inline]
list_del_init include/linux/list.h:295 [inline]
btrfs_alloc_compr_folio+0xa6/0x200 fs/btrfs/compression.c:194
zlib_compress_bio+0x115e/0x2050 fs/btrfs/zlib.c:261
btrfs_compress_bio+0x2c5/0x6b0 fs/btrfs/compression.c:1023
compress_file_range+0x8df/0x19b0 fs/btrfs/inode.c:1023
btrfs_work_helper+0x38c/0xc80 fs/btrfs/async-thread.c:312
process_one_work kernel/workqueue.c:3276 [inline]
process_scheduled_works+0xb6e/0x18c0 kernel/workqueue.c:3359
worker_thread+0xa53/0xfc0 kernel/workqueue.c:3440
kthread+0x388/0x470 kernel/kthread.c:436
ret_from_fork+0x51e/0xb90 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
Modules linked in:
---[ end trace 0000000000000000 ]---
RIP: 0010:__list_del_entry_valid_or_report+0x18a/0x190 lib/list_debug.c:65
Code: fc 13 54 fd 43 80 3c 2c 00 74 08 4c 89 ff e8 bd 06 77 fd 49 8b 56 08 48 c7 c7 40 da 27 8c 48 89 de 4c 89 f1 e8 37 47 6d fc 90 <0f> 0b cc cc cc cc 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc900056875f8 EFLAGS: 00010246
RAX: 000000000000006d RBX: ffffea00010a25c8 RCX: 5b2b99cb42e7cd00
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000000
RBP: 0000000000000005 R08: 0000000000000003 R09: 0000000000000004
R10: dffffc0000000000 R11: fffffbfff1cbd61c R12: 1ffffd40002146f2
R13: dffffc0000000000 R14: ffffea00010a3788 R15: ffffea00010a3790
FS: 0000000000000000(0000) GS:ffff88808ca55000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 000020000004b000 CR3: 000000000e54c000 CR4: 0000000000352ef0


---
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 syzk...@googlegroups.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