From: Hyunchul Lee <hyc.lee@gmail.com>
To: CharSyam <charsyam@gmail.com>
Cc: linkinjeon@kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] ntfs: mark quotas out of date on initial rw mount
Date: Fri, 15 May 2026 08:50:46 +0900 [thread overview]
Message-ID: <CANFS6banT3Vc09bFNFTMP2UOjAhYK_EhHCNXPd2uZHX-dbWxNg@mail.gmail.com> (raw)
In-Reply-To: <CAMrLSE6ZwKd4cS0YnXuKRvYoRMfXTKz8_LH62uD7F-vVR1kGtg@mail.gmail.com>
2026년 5월 14일 (목) 오후 10:25, CharSyam <charsyam@gmail.com>님이 작성:
>
> Thanks for the review.
>
> You're right that the driver does not maintain quota accounting: it
> creates v1.2 $STANDARD_INFORMATION for new inodes, and it does not update
> the v3 quota fields or $Quota usage accounting.
>
> Given that I do not have modern Windows validation for the exact quota
> rescan behavior, I'll drop 3/3 from v3 and resend just 1/3 and 2/3.
I think setting the out-of-date flag in patch 2/3 is also not meaningful.
How about removing ntfs_mark_quotas_out_of_date() related codes for now?
>
> Thanks,
> DaeMyung
--
Thanks,
Hyunchul
next prev parent reply other threads:[~2026-05-14 23:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 16:06 [PATCH 0/3] ntfs: fix quota out-of-date marking DaeMyung Kang
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
2026-05-13 23:46 ` Hyunchul Lee
2026-05-14 13:25 ` CharSyam
2026-05-14 23:50 ` Hyunchul Lee [this message]
2026-05-15 0:35 ` CharSyam
2026-05-15 1:13 ` Hyunchul Lee
2026-05-16 15:58 ` CharSyam
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=CANFS6banT3Vc09bFNFTMP2UOjAhYK_EhHCNXPd2uZHX-dbWxNg@mail.gmail.com \
--to=hyc.lee@gmail.com \
--cc=charsyam@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
all inboxes | Powered by JetHome®