From: Baolin Liu <liubaolin12138@163.com>
To: linkinjeon@kernel.org, hyc.lee@gmail.com
Cc: ntfs@lists.linux.dev, linux-kernel@vger.kernel.org,
chenxiaosong@chenxiaosong.com, Baolin Liu <liubaolin@kylinos.cn>
Subject: [PATCH v2 00/10] ntfs: persist Linux file attributes in an EA
Date: Sun, 20 Sep 2026 16:31:21 +0800 [thread overview]
Message-ID: <20260920083131.1880061-1-liubaolin12138@163.com> (raw)
From: Baolin Liu <liubaolin@kylinos.cn>
This series implements persistent immutable, append-only and nodump flags
using a private $LXFLAGS EA in the standard NTFS $EA/$EA_INFORMATION
attributes. No new NTFS attribute type or formatter changes are needed.
The value is a little-endian u32 with immutable, append-only and nodump
in bits 0, 1 and 2. Inode loading restores the flags. Unknown bits are
preserved, and the entry is removed only when its entire value is zero.
The setter protects system metadata and sys_immutable-derived immutable
state, rejects direct writes to $LXFLAGS, and updates in-memory flags
only after the EA update succeeds. Fileattr queries also report mount-wide
case folding. Nodump is reported through both fileattr and statx.
Changes since v1:
- Persist immutable, append-only and nodump in the private $LXFLAGS EA,
restoring them on inode load so inode reclaim and remount do not
discard the settings. Preserve unknown bits and reject direct xattr
writes or removal of this entry.
- Reject clearing immutable on system metadata files and files protected
by sys_immutable. Report mount-wide case folding with FS_CASEFOLD_FL.
- Add prerequisite EA fixes for presence tracking, chain validation,
error propagation, empty values and failed-update recovery. Use EUCLEAN
for structural errors detected by the EA helpers and preserve errors
from lower layers.
- Organize the series into six EA fixes and four fileattr patches, with
documentation accompanying each feature step.
- Rebase onto 018344e6f555 and verify Windows mount/access/CHKDSK
compatibility.
Patch overview:
- Patch 1 fixes the cached EA presence flag after creating or replacing
the only entry.
- Patch 2 validates EA chains and links zero-terminated tails before
appending entries.
- Patch 3 preserves EA write errors and reports truncate failures.
- Patch 4 distinguishes missing attributes from lookup failures and
rejects incomplete EA attribute pairs.
- Patch 5 distinguishes empty EA values from deletion and rejects
removal or replacement of absent entries.
- Patch 6 prepares the new list before updating attributes, restores
both old attributes on failure, and shuts down if restoration fails.
- Patch 7 adds fileattr queries for existing inode flags and mount-wide
case folding.
- Patch 8 introduces the $LXFLAGS storage and inode-load paths, adds
immutable persistence, and protects system-imposed immutable state.
- Patch 9 extends the persistent interface to append-only.
- Patch 10 adds persistent nodump and reports it through fileattr and
statx.
Testing on this revision:
- QEMU tests covered flag and EA readback, inode cache reclaim,
read-only/read-write remount, unmount/mount and fresh-kernel reload.
Checked immutable write/unlink denial, append-only enforcement,
normal I/O after clearing flags, and read-only SETFLAGS rejection.
- Verified EPERM when clearing $Bitmap protection, including without
sys_immutable, and when clearing sys_immutable-derived protection.
$MFT rejects SETFLAGS with ENOTTY through its empty operations.
Checked casefold reporting and STATX_ATTR_NODUMP.
- Exercised first-EA creation/removal, XATTR_CREATE/REPLACE, zero-length
values, zero-terminated tails, unrelated EA preservation, unknown-bit
preservation, and direct LXFLAGS write/removal rejection.
- Malformed LXFLAGS length, chain offsets, name termination, value
length and query length returned EUCLEAN. A corrupt tail following
LXFLAGS prevented an update without changing the existing flags.
An invalid resident EA_INFORMATION length rejected earlier by the
underlying attribute parser retained that parser's EIO.
- Fault injection covered allocation failure, failures after each EA
attribute update and rollback failure. Tested creation, replacement
and removal with no other EAs, resident EAs and an 8 KiB non-resident
EA; checked old values and protection after failure and remount, and
shutdown when restoration failed.
- Additional injection checked ENOSPC write errors, short writes,
truncate errors, ENOMEM/EIO lookup errors and missing EA attribute
pairs, with old EA contents verified after remount.
- Formatted a SanDisk USB partition inside QEMU using the final kernel,
and created combined and individual flag probes through SETFLAGS.
A fresh QEMU boot with both disk and mount read-only confirmed flags
0x70/0x10/0x20/0x40 and LXFLAGS values 7/1/2/4, directory nodump,
absence of the cleared entry, unchanged canary EA and statx nodump.
Windows compatibility testing of this revision completed on Windows
25H2 (OS build 26200.9457), using the LXFLAGS_V3 USB volume (serial
4C3F-43F9). Windows mounted the volume and accessed the existing probes
with dir/type. chkdsk G: /f initially could not lock the volume; after
accepting its forced-dismount prompt, it completed all three stages and
reported no filesystem problems and no further action required.
After returning the USB to Linux, a fresh QEMU guest running the final
kernel checked it with both the virtual disk and NTFS mount read-only.
GETFLAGS and EA reads confirmed the combined flags 0x70 and individual
flags 0x10/0x20/0x40, with four-byte LXFLAGS values 7/1/2/4 unchanged.
Directory nodump remained set, the cleared entry remained absent, the
unrelated canary EA was unchanged, and statx still reported nodump.
The tested Windows mount/access/CHKDSK sequence therefore preserved the
LXFLAGS names, lengths and values on the tested Windows build.
Baolin Liu (10):
ntfs: keep the EA presence flag after creating the first entry
ntfs: validate EA chains and link zero-terminated tails
ntfs: propagate EA write and truncate errors
ntfs: preserve EA attribute lookup errors
ntfs: distinguish empty EA values from removal
ntfs: restore EA attributes when an update fails
ntfs: add fileattr query support
ntfs: persist immutable in the $LXFLAGS EA
ntfs: persist append-only in the $LXFLAGS EA
ntfs: persist nodump in the $LXFLAGS EA
Documentation/filesystems/ntfs.rst | 24 ++
fs/ntfs/ea.c | 451 +++++++++++++++--------------
fs/ntfs/ea.h | 9 +
fs/ntfs/file.c | 125 +++++++-
fs/ntfs/inode.c | 12 +-
fs/ntfs/inode.h | 2 +
fs/ntfs/namei.c | 2 +
fs/ntfs/ntfs.h | 4 +
8 files changed, 410 insertions(+), 219 deletions(-)
--
2.51.0
next reply other threads:[~2026-09-20 8:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 8:31 Baolin Liu [this message]
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
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=20260920083131.1880061-1-liubaolin12138@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®