From: liubaolin <liubaolin12138@163.com>
To: Xuewen Wang <wangxuewen@kylinos.cn>,
linkinjeon@kernel.org, hyc.lee@gmail.com
Cc: ntfs@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/4] ntfs: fix MFT bitmap extension allocation
Date: Thu, 24 Sep 2026 10:10:45 +0800 [thread overview]
Message-ID: <8a52d6f6-0c16-4ae8-af98-c6eec9167e45@163.com> (raw)
In-Reply-To: <20260924014514.1678828-1-wangxuewen@kylinos.cn>
在 2026/9/24 09:45, Xuewen Wang 写道:
> 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
>
> fs/ntfs/mft.c | 26 +++++++++++++++++++++++---
> 1 file changed, 23 insertions(+), 3 deletions(-)
>
The series looks good to me.
Reviewed-by: Baolin Liu <liubaolin@kylinos.cn>
next prev parent reply other threads:[~2026-09-24 2:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 1:45 Xuewen Wang
2026-09-24 1:45 ` [PATCH v1 1/4] ntfs: bound the adjacent cluster in MFT bitmap extension Xuewen Wang
2026-09-24 2:26 ` liubaolin
2026-09-24 1:45 ` [PATCH v1 2/4] ntfs: fix rollback after MFT bitmap run coalescing Xuewen Wang
2026-09-24 2:26 ` liubaolin
2026-09-24 1:45 ` [PATCH v1 3/4] ntfs: wait for the bitmap scan before MFT bitmap extension Xuewen Wang
2026-09-24 2:26 ` liubaolin
2026-09-24 1:45 ` [PATCH v1 4/4] ntfs: account for direct MFT bitmap cluster allocation Xuewen Wang
2026-09-24 2:26 ` liubaolin
2026-09-24 2:10 ` liubaolin [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-24 1:42 [PATCH v1 0/4] ntfs: fix MFT bitmap extension allocation Xuewen Wang
2026-09-24 9:10 ` Namjae Jeon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8a52d6f6-0c16-4ae8-af98-c6eec9167e45@163.com \
--to=liubaolin12138@163.com \
--cc=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntfs@lists.linux.dev \
--cc=wangxuewen@kylinos.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®