diff options
| author | Nikolay Borisov <nborisov@suse.com> | 2022-06-23 10:55:47 +0300 |
|---|---|---|
| committer | David Sterba <dsterba@suse.com> | 2022-07-25 18:45:38 +0300 |
| commit | e26b04c4c91925dba57324db177a24e18e2d0013 (patch) | |
| tree | 23ec531d5525ea6da3380bc820cf59334bf3571a /fs/btrfs/dev-replace.c | |
| parent | c8a5f8ca9a9c7d5c5bc31d54f47ea9d86f93ed69 (diff) | |
| download | linux-e26b04c4c91925dba57324db177a24e18e2d0013.tar.xz | |
btrfs: properly flag filesystem with BTRFS_FEATURE_INCOMPAT_BIG_METADATA
Commit 6f93e834fa7c seemingly inadvertently moved the code responsible
for flagging the filesystem as having BIG_METADATA to a place where
setting the flag was essentially lost. This means that
filesystems created with kernels containing this bug (starting with 5.15)
can potentially be mounted by older (pre-3.4) kernels. In reality
chances for this happening are low because there are other incompat
flags introduced in the mean time. Still the correct behavior is to set
INCOMPAT_BIG_METADATA flag and persist this in the superblock.
Fixes: 6f93e834fa7c ("btrfs: fix upper limit for max_inline for page size 64K")
CC: stable@vger.kernel.org # 5.4+
Reviewed-by: Qu Wenruo <wqu@suse.com>
Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Reviewed-by: David Sterba <dsterba@suse.com>
Signed-off-by: David Sterba <dsterba@suse.com>
Diffstat (limited to 'fs/btrfs/dev-replace.c')
0 files changed, 0 insertions, 0 deletions