From: syzbot <syzbot+5c01398781fb51df783a@syzkaller.appspotmail.com>
To: axboe@kernel.dk, diasyzhang@tencent.com,
diasyzhangqing@gmail.com, djwong@kernel.org, dsterba@suse.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
mason@kernel.org, mcgrof@kernel.org,
syzkaller-bugs@googlegroups.com, wqu@suse.com
Subject: Re: [syzbot] [btrfs?] possible deadlock in set_blocksize
Date: Wed, 28 Oct 2026 06:01:04 -0700 [thread overview]
Message-ID: <6ae1f210.6200f071.51519.0f63.GAE@google.com> (raw)
In-Reply-To: <20261028121458.23499-1-diasyzhangqing@gmail.com>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
WARNING in __btrfs_free_extent
------------[ cut here ]------------
ret == -E
ret == -ENOENT
WARNING: fs/btrfs/extent-tree.c:3418 at __btrfs_free_extent+0x1745/0x38a0 fs/btrfs/extent-tree.c:3418, CPU#1: btrfs-transacti/6038
Modules linked in:
CPU: 1 UID: 0 PID: 6038 Comm: btrfs-transacti Not tainted syzkaller #0 PREEMPT(full)
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 10/15/2026
RIP: 0010:__btrfs_free_extent+0x1745/0x38a0 fs/btrfs/extent-tree.c:3418
Code: 84 c0 0f 84 01 03 00 00 e8 d8 88 a8 fd e9 30 0b 00 00 e8 1e ef 8c fd 84 c0 0f 84 0c 03 00 00 e8 c1 88 a8 fd e9 9d 0c 00 00 90 <0f> 0b 90 48 8b 44 24 28 42 80 3c 20 00 4d 8d 75 60 74 08 4c 89 f7
RSP: 0018:ffffc900034d7580 EFLAGS: 00010246
RAX: 00000000fffffffe RBX: ffff88801faee720 RCX: 0000000000000005
RDX: ffffffff8420790e RSI: ffffffff905d9c00 RDI: 00000000fffffffe
RBP: ffffc900034d7730 R08: ffff888021381f40 R09: 0000000000000002
R10: 00000000fffffffe R11: 0000000000000000 R12: dffffc0000000000
R13: ffff88805ad54178 R14: ffff888053e7ddc0 R15: 00000000fffffffe
FS: 0000000000000000(0000) GS:ffff88812372b000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000560567923d51 CR3: 000000007caed000 CR4: 0000000000350ef0
Call Trace:
<TASK>
run_delayed_tree_ref fs/btrfs/extent-tree.c:1824 [inline]
run_one_delayed_ref fs/btrfs/extent-tree.c:1851 [inline]
btrfs_run_delayed_refs_for_head fs/btrfs/extent-tree.c:2058 [inline]
__btrfs_run_delayed_refs+0x1669/0x43a0 fs/btrfs/extent-tree.c:2134
btrfs_run_delayed_refs+0xdc/0x2a0 fs/btrfs/extent-tree.c:2246
btrfs_commit_transaction+0x287/0x3010 fs/btrfs/transaction.c:2283
transaction_kthread+0x2c1/0x460 fs/btrfs/disk-io.c:1586
kthread+0x38b/0x480 kernel/kthread.c:436
ret_from_fork+0x514/0xb70 arch/x86/kernel/process.c:158
ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:245
</TASK>
Tested on:
commit: 65ba8f34 Merge tag 'xtensa-20261027' of https://github..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1439e469580000
kernel config: https://syzkaller.appspot.com/x/.config?x=fbcd9c8641bd149b
dashboard link: https://syzkaller.appspot.com/bug?extid=5c01398781fb51df783a
compiler: Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=11607721580000
next prev parent reply other threads:[~2026-10-28 13:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 12:14 [PATCH] btrfs: set the block size before starting a transaction Qing Zhang
2026-10-28 13:01 ` syzbot [this message]
2026-10-28 20:25 ` Qu Wenruo
2026-10-29 6:22 ` Qing Zhang
-- strict thread matches above, loose matches on Subject: below --
2026-10-24 13:33 [syzbot] [btrfs?] possible deadlock in set_blocksize syzbot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6ae1f210.6200f071.51519.0f63.GAE@google.com \
--to=syzbot+5c01398781fb51df783a@syzkaller.appspotmail.com \
--cc=axboe@kernel.dk \
--cc=diasyzhang@tencent.com \
--cc=diasyzhangqing@gmail.com \
--cc=djwong@kernel.org \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@kernel.org \
--cc=mcgrof@kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wqu@suse.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.