From: liubaolin <liubaolin12138@163.com>
To: Hyunchul Lee <hyc.lee@gmail.com>
Cc: linkinjeon@kernel.org, ntfs@lists.linux.dev,
linux-kernel@vger.kernel.org, chenxiaosong@chenxiaosong.com,
Baolin Liu <liubaolin@kylinos.cn>
Subject: Re: [PATCH v2 08/10] ntfs: persist immutable in the $LXFLAGS EA
Date: Tue, 22 Sep 2026 14:02:19 +0800 [thread overview]
Message-ID: <b4cc0b52-23b8-4a6a-865a-a419ebecc6d0@163.com> (raw)
In-Reply-To: <CANFS6bbM-OpYLoRvQNAhmo-FNBd9V0K7wEt6iYTc-6cPf+2uEw@mail.gmail.com>
在 2026/9/22 13:25, Hyunchul Lee 写道:
> 2026년 9월 22일 (화) 오후 12:27, liubaolin <liubaolin12138@163.com>님이 작성:
>>
>>
>>
>> 在 2026/9/22 09:21, Hyunchul Lee 写道:
>>> Hi Baolin,
>>>
>>> 2026년 9월 20일 (일) 오후 5:32, Baolin Liu <liubaolin12138@163.com>님이 작성:
>>>>
>>>> From: Baolin Liu <liubaolin@kylinos.cn>
>>>>
>>>> Add a fileattr setter for immutable and store its state in bit 0 of a
>>>> little-endian u32 in the private $LXFLAGS EA. Reuse the standard NTFS EA
>>>> attributes and restore the flag when loading an inode, so eviction and
>>>> unmount do not discard the setting.
>>>
>>>
>>> I think that the name $LXFLAGS is not appropriate. the prefix $LX
>>> seems to be a WSL-owned namespace. The name could cause
>>> confusion or a future semantics collision with Windows WSL.
>>>
>>> Thanks,
>>> Hyunchul
>>
>> Hi Hyunchul,
>>
>> Thanks for pointing this out. I agree that we should avoid the $LX
>> prefix to prevent confusion or a future semantics collision with WSL.
>>
>> Would $LINUXFLAGS be an acceptable name for this private EA?
>>
>> If you agree, I'll update the code and documentation, rerun the
>> relevant tests, including the Windows NTFS and CHKDSK compatibility
>> tests with the new name, and submit the revised patches as v4.
>
> I agree. And others look good to me.
> Feel free to add my review tag for this patch set.
>
> Reviewed-by: Hyunchul Lee <hyc.lee@gmail.com>
Hi Hyunchul,
Thanks for your reply. I'll add your Reviewed-by tag to the v4 series.
Thanks,
Baolin.
>
>>
>> I look forward to your feedback.
>>
>> Thanks,
>> Baolin.
>>
>
>
next prev parent reply other threads:[~2026-09-22 6:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 8:31 [PATCH v2 00/10] ntfs: persist Linux file attributes in an EA Baolin Liu
2026-09-20 8:31 ` [PATCH v2 01/10] ntfs: keep the EA presence flag after creating the first entry Baolin Liu
2026-09-20 8:31 ` [PATCH v2 02/10] ntfs: validate EA chains and link zero-terminated tails Baolin Liu
2026-09-21 6:17 ` Namjae Jeon
2026-09-21 10:34 ` liubaolin
2026-09-20 8:31 ` [PATCH v2 03/10] ntfs: propagate EA write and truncate errors Baolin Liu
2026-09-20 8:31 ` [PATCH v2 04/10] ntfs: preserve EA attribute lookup errors Baolin Liu
2026-09-20 8:31 ` [PATCH v2 05/10] ntfs: distinguish empty EA values from removal Baolin Liu
2026-09-20 8:31 ` [PATCH v2 06/10] ntfs: restore EA attributes when an update fails Baolin Liu
2026-09-20 8:31 ` [PATCH v2 07/10] ntfs: add fileattr query support Baolin Liu
2026-09-20 8:31 ` [PATCH v2 08/10] ntfs: persist immutable in the $LXFLAGS EA Baolin Liu
2026-09-22 1:21 ` Hyunchul Lee
2026-09-22 3:26 ` liubaolin
2026-09-22 5:25 ` Hyunchul Lee
2026-09-22 6:02 ` liubaolin [this message]
2026-09-20 8:31 ` [PATCH v2 09/10] ntfs: persist append-only " Baolin Liu
2026-09-20 8:31 ` [PATCH v2 10/10] ntfs: persist nodump " Baolin Liu
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=b4cc0b52-23b8-4a6a-865a-a419ebecc6d0@163.com \
--to=liubaolin12138@163.com \
--cc=chenxiaosong@chenxiaosong.com \
--cc=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liubaolin@kylinos.cn \
--cc=ntfs@lists.linux.dev \
/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®