Re: [PATCH v1 0/4] ntfs: fix MFT bitmap extension allocation
From: Namjae Jeon
Date: Fri Sep 25 2026 - 04:41:44 EST
On Thu, Sep 24, 2026 at 10:42 AM Xuewen Wang <wangxuewen@xxxxxxxxxx> wrote:
>
> This series fixes four bugs in the MFT bitmap extension path:
>
> - The adjacent-cluster candidate can be outside the volume. Check it
> before accessing $Bitmap and fall back to the regular allocator.
> - The allocator can return an adjacent cluster that merges with the
> existing run. Preserve that run when rolling back a failed extension.
> - Rollback can wait for the initial $Bitmap scan while holding a folio
> the scanner needs. Wait for the scan before starting the allocation.
> - Direct allocation changes $Bitmap without updating the cached free
> counts. Update both counts and honor per-page accounting and space
> reserved for delayed allocation.
>
> Xuewen Wang (4):
> ntfs: bound the adjacent cluster in MFT bitmap extension
> ntfs: fix rollback after MFT bitmap run coalescing
> ntfs: wait for the bitmap scan before MFT bitmap extension
> ntfs: account for direct MFT bitmap cluster allocation
Applied them to #ntfs-next.
Thanks!