From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org, HAN Yuwei <hrx@bupt.moe>,
stable@vger.kernel.org
Subject: Re: [PATCH] btrfs: reject zoned RW mount if sectorsize is smaller than page size
Date: Mon, 12 Feb 2024 12:14:50 +0100 [thread overview]
Message-ID: <20240212111450.GZ355@twin.jikos.cz> (raw)
In-Reply-To: <2a19a500ccb297397018dac23d30106977153d62.1707714970.git.wqu@suse.com>
On Mon, Feb 12, 2024 at 03:46:15PM +1030, Qu Wenruo wrote:
> [BUG]
> There is a bug report that with zoned device and sectorsize is smaller
> than page size (aka, subpage), btrfs would crash with a very basic
> workload:
>
> # getconfig PAGESIZE
> 16384
> # mkfs.btrfs -f $dev -s 4k
> # mount $dev $mnt
> # $fsstress -w -n 8 -s 1707820327 -v -d $mnt
> # umount $mnt
>
> The crash would look like this (with CONFIG_BTRFS_ASSERT enabled):
>
> assertion failed: block_start != EXTENT_MAP_HOLE, in fs/btrfs/extent_io.c:1384
This is the same as what Josef fixed in
https://github.com/btrfs/linux/commit/400bb013912dac637c7d6826407be580ea8ef9cc
"btrfs: don't drop extent_map for free space inode on write error"
but not on zoned+subpage, is it really a different error you're fixing?
[...]
> [WORKAROUND]
> A proper fix requires some big changes to delalloc workload, to allow
> extent_write_locked_range() to handle multiple different entries with
> the same @locked_page.
>
> So for now, disable read-write support for subpage zoned btrfs.
>
> The problem can only be solved if subpage btrfs can handle subpage
> compression, which need quite some work on the delalloc procedure for
> the @locked_page handling.
Ok, this on itself is a valid reason to disable the support.
next prev parent reply other threads:[~2024-02-12 11:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 5:16 [PATCH] btrfs: reject zoned RW mount if sectorsize is smaller than page size Qu Wenruo
2024-02-12 9:45 ` Johannes Thumshirn
2024-02-12 9:50 ` Qu Wenruo
2024-02-12 10:25 ` Johannes Thumshirn
2024-02-14 7:29 ` David Sterba
2024-02-17 0:07 ` Qu Wenruo
2024-02-12 11:14 ` David Sterba [this message]
2024-02-12 22:54 ` Qu Wenruo
2024-02-14 7:28 ` David Sterba
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=20240212111450.GZ355@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=hrx@bupt.moe \
--cc=linux-btrfs@vger.kernel.org \
--cc=stable@vger.kernel.org \
--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