On Tue, 27 May 2025 07:28:51 -0600, Jens Axboe wrote: > As per the thread here: > > https://lore.kernel.org/linux-fsdevel/20250525083209.GS2023217@ZenIV/ > > there was an issue with the dropbehind support, and hence it got > reverted (effectively) for the 6.15 kernel release. The problem stems > from the fact that the folio can get redirtied and/or scheduled for > writeback after the initial dropbehind test, and before we have it > locked again for invalidation. > > [...] Applied to the vfs.fixes branch of the vfs/vfs.git tree. Patches in the vfs.fixes branch should appear in linux-next soon. Please report any outstanding bugs that were missed during review in a new review to the original patch series allowing us to drop it. It's encouraged to provide Acked-bys and Reviewed-bys even though the patch has now been applied. If possible patch trailers will be updated. Note that commit hashes shown below are subject to change due to rebase, trailer updates or similar. If in doubt, please check the listed branch. tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git branch: vfs.fixes [1/5] mm/filemap: gate dropbehind invalidate on folio !dirty && !writeback https://git.kernel.org/vfs/vfs/c/095f627add86 [2/5] mm/filemap: use filemap_end_dropbehind() for read invalidation https://git.kernel.org/vfs/vfs/c/25b065a744ff [3/5] Revert "Disable FOP_DONTCACHE for now due to bugs" https://git.kernel.org/vfs/vfs/c/7b2b67dbd449 [4/5] mm/filemap: unify read/write dropbehind naming https://git.kernel.org/vfs/vfs/c/1da7a06d9ce4 [5/5] mm/filemap: unify dropbehind flag testing and clearing https://git.kernel.org/vfs/vfs/c/a1d98e4ffb97
