Re: [PATCH v2 5/8] btrfs-progs: print encryptin type field of file extents

Daniel Vacek <[email protected]>
Newsgroups org.kernel.vger.linux-btrfs,org.kernel.vger.linux-fscrypt,org.kernel.vger.linux-kernel
Message-ID <CAPjX3Fdc7+iy+-zqHgnJQwgwDk4mNSbuWmLG44jWWJkk=3MWvg@mail.gmail.com>
On Thu, 2 Jul 2026 at 09:11, Qu Wenruo <[email protected]> wrote:
> 在 2026/7/2 16:35, Daniel Vacek 写道:
> [...]
> >>
> >> A simple tree dump can always show which range is hole and which is
> >> preallocated.
> >
> > Yeah, that's true. I'm curious how other FSes handle this. Let me see.
> > Or do you know from the top of your head?
>
> Sorry, not familiar with other fscrypt implementation at all.
> You may want to try to experiment on ext4 to see how it's implemented.
>
> I guess they do nothing special and just expose hole/prealloc info.
>
> As the other path would be always filling hole with zero filled regular
> extents (before encryption), and disable preallocation completely.
> That looks over-killed and may take a lot of extra space.

Well, rather filling the prealloc with the same zero-filled extent I guess.

--nX
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.