[v5.15] WARNING in btrfs_chunk_alloc

2 views
Skip to first unread message

syzbot

unread,
Mar 23, 2023, 5:32:52 AM3/23/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 115472395b0a Linux 5.15.104
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=1093d77ec80000
kernel config: https://syzkaller.appspot.com/x/.config?x=f5592cc4916e1c2f
dashboard link: https://syzkaller.appspot.com/bug?extid=b001c5f1a59914f11936
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6c2c0744c7e0/disk-11547239.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/7ea4c5ecca4f/vmlinux-11547239.xz
kernel image: https://storage.googleapis.com/syzbot-assets/9a231dbcf423/bzImage-11547239.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 30164 at fs/btrfs/block-group.c:3443 do_chunk_alloc fs/btrfs/block-group.c:3443 [inline]
WARNING: CPU: 0 PID: 30164 at fs/btrfs/block-group.c:3443 btrfs_chunk_alloc+0xc0e/0x1020 fs/btrfs/block-group.c:3666
Modules linked in:
CPU: 0 PID: 30164 Comm: kworker/u4:18 Not tainted 5.15.104-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: events_unbound btrfs_async_reclaim_data_space
RIP: 0010:do_chunk_alloc fs/btrfs/block-group.c:3443 [inline]
RIP: 0010:btrfs_chunk_alloc+0xc0e/0x1020 fs/btrfs/block-group.c:3666
Code: 00 00 00 fc ff df 4c 8b 24 24 0f 1f 44 00 00 e8 58 00 ff fd eb 16 e8 51 00 ff fd 48 c7 c7 40 76 cb 8a 44 89 ee e8 22 e5 ca fd <0f> 0b 48 8b 7c 24 20 48 c7 c6 40 84 cb 8a ba 73 0d 00 00 e9 8e 00
RSP: 0018:ffffc900044079d8 EFLAGS: 00010246
RAX: bd23d6e86d249000 RBX: dffffc0000000000 RCX: ffff88803eaf8000
RDX: 0000000000000000 RSI: 0000000080000000 RDI: 0000000000000000
RBP: ffff88808c3b0001 R08: ffffffff8166101c R09: ffffed1017344f24
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff888079762884
R13: ffffffffffffffe4 R14: ffff88807352d04b R15: 1ffff1100f2ec510
FS: 0000000000000000(0000) GS:ffff8880b9a00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000001b2e333000 CR3: 0000000023455000 CR4: 00000000003506f0
DR0: 00000000ffff070c DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
flush_space+0x4c5/0xd50 fs/btrfs/space-info.c:670
btrfs_async_reclaim_data_space+0x118/0x3e0 fs/btrfs/space-info.c:1169
process_one_work+0x8a1/0x10c0 kernel/workqueue.c:2306
worker_thread+0xaca/0x1280 kernel/workqueue.c:2453
kthread+0x3f6/0x4f0 kernel/kthread.c:319
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:298
</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 syzk...@googlegroups.com.

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

syzbot

unread,
Mar 28, 2023, 9:54:44 AM3/28/23
to syzkaller...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: e3a87a10f259 Linux 6.1.21
git tree: linux-6.1.y
console output: https://syzkaller.appspot.com/x/log.txt?x=165c0a01c80000
kernel config: https://syzkaller.appspot.com/x/.config?x=b49b0405a60858ed
dashboard link: https://syzkaller.appspot.com/bug?extid=b511d1aeef04cf811d00
compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/ed3d1f3e75e6/disk-e3a87a10.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/6d8e44c8c75c/vmlinux-e3a87a10.xz
kernel image: https://storage.googleapis.com/syzbot-assets/cebe803ea4fa/bzImage-e3a87a10.xz

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

------------[ cut here ]------------
WARNING: CPU: 0 PID: 3904 at fs/btrfs/block-group.c:3536 do_chunk_alloc fs/btrfs/block-group.c:3536 [inline]
WARNING: CPU: 0 PID: 3904 at fs/btrfs/block-group.c:3536 btrfs_chunk_alloc+0xe47/0xff0 fs/btrfs/block-group.c:3778
Modules linked in:
CPU: 0 PID: 3904 Comm: kworker/u4:10 Not tainted 6.1.21-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Workqueue: events_unbound btrfs_async_reclaim_data_space
RIP: 0010:do_chunk_alloc fs/btrfs/block-group.c:3536 [inline]
RIP: 0010:btrfs_chunk_alloc+0xe47/0xff0 fs/btrfs/block-group.c:3778
Code: fd 48 c7 c7 e0 7c 2f 8b 44 89 e6 e8 03 c3 a8 fd 0f 0b e9 02 fe ff ff e8 37 24 e0 fd 48 c7 c7 e0 7c 2f 8b 89 ee e8 e9 c2 a8 fd <0f> 0b e9 0d fe ff ff e8 1d 24 e0 fd 48 c7 c7 e0 7c 2f 8b 44 89 e6
RSP: 0018:ffffc900055d79c8 EFLAGS: 00010246
RAX: 2493fe02cb205f00 RBX: ffff888074ef4001 RCX: ffff88808b4b3a80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: ffffffffffffffe4 R08: ffffffff8152292e R09: ffffed1017304f1c
R10: 0000000000000000 R11: dffffc0000000001 R12: ffff88807cb6c000
R13: dffffc0000000000 R14: ffff88807c568000 R15: 0000000000000000
FS: 0000000000000000(0000) GS:ffff8880b9800000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 0000000023dc8000 CR4: 00000000003506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
flush_space+0xa03/0xe60 fs/btrfs/space-info.c:770
btrfs_async_reclaim_data_space+0x146/0x4f0 fs/btrfs/space-info.c:1300
process_one_work+0x8aa/0x11f0 kernel/workqueue.c:2289
worker_thread+0xa5f/0x1210 kernel/workqueue.c:2436
kthread+0x268/0x300 kernel/kthread.c:376
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:306

syzbot

unread,
Jul 26, 2023, 9:54:38 AM7/26/23
to syzkaller...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.

syzbot

unread,
Sep 22, 2023, 11:34:51 AM9/22/23
to syzkaller...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages