From: Matthew Wilcox <willy@infradead.org>
To: David Timber <dxdt@dev.snart.me>
Cc: linkinjeon@kernel.org, sj1557.seo@samsung.com,
yuezhang.mo@sony.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/2] exfat: EXFAT_IOC_GET_VALID_DATA ioctl
Date: Thu, 12 Mar 2026 03:23:03 +0000 [thread overview]
Message-ID: <abIxl8XEftpku8yf@casper.infradead.org> (raw)
In-Reply-To: <20260311222613.2010177-1-dxdt@dev.snart.me>
On Thu, Mar 12, 2026 at 07:26:13AM +0900, David Timber wrote:
> When a file in exfat fs gets truncated up or fallocate()'d up, only
> additional clusters are allocated and isize updated whilst VDL(valid
> data length) remains unchanged. If an application writes to the file
> past the VDL, significant IO delay can occur as the skipped range
> [VDL, offset) has to be zeroed out before returning to userspace. Some
> users may find this caveat unacceptible.
>
> Some niche applications(especially embedded systems) may want to query
> the discrepancy between the VDL and isize before doing lseek() and
> write() to estimate the delay from implicit zeroring.
>
> The commit introduces a new ioctl EXFAT_IOC_GET_VALID_DATA, which
> correspond to `fsutil file queryvaliddata ...` available on Windows.
> With the new ioctl, applications could assess the delay that may incur
> and make decisions accordingly before seeking past the VDL to write.
We already have two interfaces for this on Linux. One is SEEK_HOLE /
SEEK_DATA and the other is fiemap (Documentation/filesystems/fiemap.rst)
Why are both of these interfaces unsuitable?
next prev parent reply other threads:[~2026-03-12 3:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-11 22:26 David Timber
2026-03-12 3:23 ` Matthew Wilcox [this message]
2026-03-12 14:02 ` David Timber
2026-03-12 14:57 ` Matthew Wilcox
2026-03-12 15:06 ` Darrick J. Wong
2026-03-13 7:59 ` David Timber
2026-03-13 13:59 ` Namjae Jeon
2026-03-13 16:24 ` Darrick J. Wong
2026-03-16 22:37 ` David Timber
2026-03-19 0:51 ` Namjae Jeon
2026-03-19 3:29 ` David Timber
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=abIxl8XEftpku8yf@casper.infradead.org \
--to=willy@infradead.org \
--cc=dxdt@dev.snart.me \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=yuezhang.mo@sony.com \
/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®