Skip to content

fs/dax: check zero or empty entry before converting xarray entry#1321

Open
vfsci-bot[bot] wants to merge 1 commit intovfs.base.cifrom
pw/1089993/vfs.base.ci
Open

fs/dax: check zero or empty entry before converting xarray entry#1321
vfsci-bot[bot] wants to merge 1 commit intovfs.base.cifrom
pw/1089993/vfs.base.ci

Conversation

@vfsci-bot
Copy link
Copy Markdown

@vfsci-bot vfsci-bot Bot commented May 5, 2026

Series: https://patchwork.kernel.org/project/linux-fsdevel/list/?series=1089993
Submitter: Seunguk Shin
Version: 3
Patches: 1/1
Message-ID: <[email protected]>
Base: vfs.base.ci
Lore: https://lore.kernel.org/linux-fsdevel/[email protected]


Automated by ml2pr

dax_associate_entry(), dax_disassociate_entry(), and dax_busy_page()
call dax_to_folio(entry) before checking whether entry is a zero or
empty xarray entry.

That ordering is wrong because zero and empty entries are not folio
entries. Commit 98c183a ("fs/dax: don't disassociate zero page
entries") added guards in the associate and disassociate paths, but the
guards still come after dax_to_folio(entry), and dax_busy_page() still
has the same problem.

Move the zero/empty checks before dax_to_folio(entry) in all three helpers.

Fixes: 38607c6 ("fs/dax: properly refcount fs dax pages")
Signed-off-by: Seunguk Shin <[email protected]>
Reviewed-by: Jan Kara <[email protected]>
Reviewed-by: Alistair Popple <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant