mirror of
git://git.yoctoproject.org/linux-yocto.git
synced 2026-01-27 12:47:24 +01:00
btrfs: subpage: prepare for large data folios
The subpage handling code has two locations not supporting large folios: - btrfs_attach_subpage() Which is doing a metadata specific ASSERT() check. But for the future large data folios support, that check is too generic. Since it's metadata specific, only check the ASSERT() for metadata. - btrfs_subpage_assert() Just remove the "ASSERT(folio_order(folio) == 0)" check. Signed-off-by: Qu Wenruo <wqu@suse.com> Reviewed-by: David Sterba <dsterba@suse.com> Signed-off-by: David Sterba <dsterba@suse.com>
This commit is contained in:
parent
c08d45de63
commit
3a8f948633
|
|
@ -69,7 +69,8 @@ int btrfs_attach_subpage(const struct btrfs_fs_info *fs_info,
|
|||
struct btrfs_subpage *subpage;
|
||||
|
||||
/* For metadata we don't support large folio yet. */
|
||||
ASSERT(!folio_test_large(folio));
|
||||
if (type == BTRFS_SUBPAGE_METADATA)
|
||||
ASSERT(!folio_test_large(folio));
|
||||
|
||||
/*
|
||||
* We have cases like a dummy extent buffer page, which is not mapped
|
||||
|
|
@ -181,9 +182,6 @@ void btrfs_folio_dec_eb_refs(const struct btrfs_fs_info *fs_info, struct folio *
|
|||
static void btrfs_subpage_assert(const struct btrfs_fs_info *fs_info,
|
||||
struct folio *folio, u64 start, u32 len)
|
||||
{
|
||||
/* For subpage support, the folio must be single page. */
|
||||
ASSERT(folio_order(folio) == 0);
|
||||
|
||||
/* Basic checks */
|
||||
ASSERT(folio_test_private(folio) && folio_get_private(folio));
|
||||
ASSERT(IS_ALIGNED(start, fs_info->sectorsize) &&
|
||||
|
|
|
|||
Loading…
Reference in New Issue
Block a user