From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/3] btrfs-progs: make subpage warnings more strict
Date: Fri, 20 Aug 2021 14:46:49 +0200 [thread overview]
Message-ID: <20210820124649.GR5047@twin.jikos.cz> (raw)
In-Reply-To: <20210818064420.866803-1-wqu@suse.com>
On Wed, Aug 18, 2021 at 02:44:17PM +0800, Qu Wenruo wrote:
> For the incoming support of more page sizes for subpage RW mount, we
> will require tree blocks to be nodesize aligned.
>
> This patch prepare such restrict warnings for btrfs-check and update
> self-tests to handle them.
>
> Currently all convert/fsck/misc can pass except one unrelated
> regression, fsck/025, which is caused by "btrfs-progs: Drop the type
> check in init_alloc_chunk_ctl_policy_regular".
I've dropped the test 025 for now so we can do the tests.
> All fsck images except fsck/018 are newer enough to have all their tree
> blocks nodesize aligned, so they won't cause any new warnings.
> But still, for read-only tests, we will skip the subpage warnings as we
> only want to ensure our writes from btrfs-progs won't cause new subpage
> warnings.
>
> Qu Wenruo (3):
> btrfs-progs: tests: also check subpage warning for type 2 test cases
> btrfs-progs: tests: don't check subpage related warnings for fsck type
> 1 tests
> btrfs-progs: require full nodesize alignement for subpage support
Added to devel, thanks.
prev parent reply other threads:[~2021-08-20 12:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 6:44 [PATCH 0/3] btrfs-progs: make subpage warnings more strict Qu Wenruo
2021-08-18 6:44 ` [PATCH 1/3] btrfs-progs: tests: also check subpage warning for type 2 test cases Qu Wenruo
2021-08-18 18:12 ` David Sterba
2021-08-20 12:42 ` David Sterba
2021-08-18 6:44 ` [PATCH 2/3] btrfs-progs: tests: don't check subpage related warnings for fsck type 1 tests Qu Wenruo
2021-08-18 6:44 ` [PATCH 3/3] btrfs-progs: require full nodesize alignement for subpage support Qu Wenruo
2021-08-20 12:46 ` David Sterba [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=20210820124649.GR5047@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).