From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Qing Zhang <diasyzhangqing@gmail.com>, linux-btrfs@vger.kernel.org
Cc: David Sterba <dsterba@suse.com>, Chris Mason <mason@kernel.org>,
Jens Axboe <axboe@kernel.dk>,
Luis Chamberlain <mcgrof@kernel.org>,
"Darrick J . Wong" <djwong@kernel.org>, Qu Wenruo <wqu@suse.com>,
syzbot+5c01398781fb51df783a@syzkaller.appspotmail.com,
linux-kernel@vger.kernel.org, diasyzhang@tencent.com
Subject: Re: [PATCH] btrfs: set the block size before starting a transaction
Date: Thu, 29 Oct 2026 06:55:22 +1030 [thread overview]
Message-ID: <d7a63c1c-f178-4879-ae42-39e9e088b9dc@gmx.com> (raw)
In-Reply-To: <20261028121458.23499-1-diasyzhangqing@gmail.com>
在 2026/10/28 22:44, Qing Zhang 写道:
> From: Qing Zhang <diasyzhang@tencent.com>
>
> When adding a device, btrfs_init_new_device() calls set_blocksize()
> with a transaction handle held. If the block size changes, this takes
> the bdev inode's i_rwsem and triggers a lockdep dependency cycle:
>
> bdev i_rwsem -> mmap_lock -> trans_num_writers
> -> trans_num_extwriters -> bdev i_rwsem
>
> The buffered read path nests mmap_lock under the bdev i_rwsem, while
> mmapping a btrfs file can join a transaction through atime updates.
> Since commit c0e473a0d226 ("block: fix race between set_blocksize and
> read paths"), set_blocksize() takes the bdev inode's i_rwsem when
> changing the block size.
>
> Move set_blocksize() before btrfs_start_transaction() to break the
> cycle. Also check its return value to reject devices whose logical
> block size exceeds BTRFS_BDEV_BLOCKSIZE.
>
> Fixes: c0e473a0d226 ("block: fix race between set_blocksize and read paths")
> Reported-by: syzbot+5c01398781fb51df783a@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=5c01398781fb51df783a
There is already a better solution by not calling the stupid
ste_blocksize() at all:
https://lore.kernel.org/linux-btrfs/3d98566e8aa2cd99a23ce89665f79281c614f05e.1792885061.git.wqu@suse.com/
> Signed-off-by: Qing Zhang <diasyzhang@tencent.com>
> ---
> #syz test: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> fs/btrfs/volumes.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index d3e6a9b429dd..a7f0607a5b86 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -3019,6 +3019,10 @@ int btrfs_init_new_device(struct btrfs_fs_info *fs_info, const char *device_path
> if (ret)
> goto error_free_device;
>
> + ret = set_blocksize(device->bdev_file, BTRFS_BDEV_BLOCKSIZE);
> + if (ret)
> + goto error_free_zone;
> +
> trans = btrfs_start_transaction(root, 0);
> if (IS_ERR(trans)) {
> ret = PTR_ERR(trans);
> @@ -3043,7 +3047,6 @@ int btrfs_init_new_device(struct btrfs_fs_info *fs_info, const char *device_path
> */
> atomic_inc(&device->dev_stats_ccnt);
> device->dev_stats_valid = 1;
> - set_blocksize(device->bdev_file, BTRFS_BDEV_BLOCKSIZE);
>
> if (seeding_dev) {
> /* GFP_KERNEL allocation must not be under device_list_mutex */
prev parent reply other threads:[~2026-10-28 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 12:14 Qing Zhang
2026-10-28 13:01 ` [syzbot] [btrfs?] possible deadlock in set_blocksize syzbot
2026-10-28 20:25 ` Qu Wenruo [this message]
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=d7a63c1c-f178-4879-ae42-39e9e088b9dc@gmx.com \
--to=quwenruo.btrfs@gmx.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=syzbot+5c01398781fb51df783a@syzkaller.appspotmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®