From: DaeMyung Kang <charsyam@gmail.com>
To: linkinjeon@kernel.org, hyc.lee@gmail.com
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
DaeMyung Kang <charsyam@gmail.com>
Subject: [PATCH 0/3] ntfs: fix quota out-of-date marking
Date: Tue, 12 May 2026 01:06:22 +0900 [thread overview]
Message-ID: <20260511160626.1268612-1-charsyam@gmail.com> (raw)
This series fixes NTFS quota out-of-date marking in fs/ntfs.
The driver already has quota compatibility code: it loads
FILE_Extend/$Quota, opens the $Q index, and has
ntfs_mark_quotas_out_of_date() to set QUOTA_FLAG_OUT_OF_DATE so Windows
can rescan quota usage. The failures were not an intentional quota block;
the code could not reach and update the $Quota/$Q defaults entry correctly.
Patch 1 fixes ntfs_index_lookup() so callers looking up view indexes get
the index entry value instead of the key. Directory $I30 callers keep the
existing key-return behavior. The patch uses the index root type, not the
collation rule, to choose between $FILE_NAME keys and view-index values. It
also validates the returned value bounds without truncating the minimum
offset, excludes the child VCN tail from INDEX_ENTRY_NODE value ranges, and
clears the returned context pointers before returning an invalid view-index
entry error. The matched-entry data exposure and validation are moved into
a small helper, ntfs_index_lookup_set_data(), so the done label stays flat
and the bounds check has a single return.
Patch 2 fixes ntfs_mark_quotas_out_of_date() to look up $Quota/$Q by the
$Q index name, not $I30.
Patch 3 calls ntfs_mark_quotas_out_of_date() during initial read-write mount
as well as the existing read-only to read-write remount path. The init
sequence is wrapped in a small helper, ntfs_init_quota_for_mount(), which
captures each call result in a local variable, derives the failure reason,
and gates the read-only downgrade on policy in one place — keeping
ntfs_load_system_files() flat.
QEMU/virtme testing:
- The original remount-rw reproducer failed with:
"Lookup of quota defaults entry failed."
- After changing only the quota index name, the same path exposed the second
bug and failed with:
"Quota defaults entry size is invalid. Run chkdsk."
- With this series applied:
- read-only mount followed by remount,rw succeeds
- with the $Quota/$Q defaults flags prepared as 0x00000011, remount,rw
persists 0x00000211
- direct rw mount with the same prepared image also persists 0x00000211
DaeMyung Kang (3):
ntfs: return view index entry data from lookup
ntfs: use $Q when marking quotas out of date
ntfs: mark quotas out of date on initial rw mount
fs/ntfs/index.c | 75 ++++++++++++++++++++++++++++++++++++++++++++++++++++---
fs/ntfs/index.h | 3 +-
fs/ntfs/quota.c | 3 +-
fs/ntfs/super.c | 46 ++++++++++++++++++++++++++--------
4 files changed, 110 insertions(+), 17 deletions(-)
--
2.43.0
next reply other threads:[~2026-05-11 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 16:06 DaeMyung Kang [this message]
2026-05-11 16:06 ` [PATCH 1/3] ntfs: return view index entry data from lookup DaeMyung Kang
2026-05-13 2:14 ` Hyunchul Lee
2026-05-11 16:06 ` [PATCH 2/3] ntfs: use $Q when marking quotas out of date DaeMyung Kang
2026-05-13 14:53 ` Namjae Jeon
2026-05-11 16:06 ` [PATCH 3/3] ntfs: mark quotas out of date on initial rw mount DaeMyung Kang
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=20260511160626.1268612-1-charsyam@gmail.com \
--to=charsyam@gmail.com \
--cc=hyc.lee@gmail.com \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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