From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Sai Chaitanya Mitta <mittachaitu@gmail.com>, linux-xfs@vger.kernel.org
Subject: Re: Approach to quickly zeroing large XFS file (or) tool to mark XFS file extents as written
Date: Mon, 6 Jan 2025 03:15:08 -0800 [thread overview]
Message-ID: <Z3u7PDUmybjmOBez@infradead.org> (raw)
In-Reply-To: <Z2otkMAbTdrbtNFW@dread.disaster.area>
On Tue, Dec 24, 2024 at 02:42:08PM +1100, Dave Chinner wrote:
> On Mon, Dec 23, 2024 at 10:12:32PM +0530, Sai Chaitanya Mitta wrote:
> > Hi Team,
> > Is there any method/tool available to explicitly mark XFS
> > file extents as written? One approach I
>
> Writing data to the unwritten extent is the only way to do this.
> Allowing uninitialised data extents to be converted to a written
> state opens a massive hole in system security.
Yes.
> Go search for the discussions around FALLOC_FL_NO_HIDE_STALE from
> well over a decade ago.....
Or look for the old XFS_IOC_ALLOCSP ioctl which did allocation and
freeing in one syscall, which we removed quite a while ago.
prev parent reply other threads:[~2025-01-06 11:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 16:42 Approach to quickly zeroing large XFS file (or) tool to mark XFS file extents as written Sai Chaitanya Mitta
2024-12-23 21:53 ` Darrick J. Wong
2024-12-24 5:47 ` Sai Chaitanya Mitta
2025-01-06 19:46 ` Darrick J. Wong
2025-01-07 6:14 ` Christoph Hellwig
2025-01-07 7:04 ` Darrick J. Wong
2025-01-07 8:37 ` Christoph Hellwig
2025-01-07 22:11 ` Darrick J. Wong
2024-12-24 3:42 ` Dave Chinner
2025-01-06 11:15 ` Christoph Hellwig [this message]
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=Z3u7PDUmybjmOBez@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--cc=linux-xfs@vger.kernel.org \
--cc=mittachaitu@gmail.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