[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20251113102244.GJ13846@twin.jikos.cz>
Date: Thu, 13 Nov 2025 11:22:44 +0100
From: David Sterba <dsterba@...e.cz>
To: Qu Wenruo <wqu@...e.com>
Cc: Daniel Vacek <neelx@...e.com>, Chris Mason <clm@...com>,
Josef Bacik <josef@...icpanda.com>, David Sterba <dsterba@...e.com>,
linux-btrfs@...r.kernel.org, linux-kernel@...r.kernel.org,
Omar Sandoval <osandov@...ndov.com>,
Sweet Tea Dorminy <sweettea-kernel@...miny.me>
Subject: Re: [PATCH v6 1/8] btrfs: disable various operations on encrypted
inodes
On Thu, Nov 13, 2025 at 07:40:35AM +1030, Qu Wenruo wrote:
> 在 2025/11/13 06:06, Daniel Vacek 写道:
> > From: Omar Sandoval <osandov@...ndov.com>
> >
> > Initially, only normal data extents will be encrypted. This change
> > forbids various other bits:
> > - allows reflinking only if both inodes have the same encryption status
> > - disable inline data on encrypted inodes
>
> I'm wondering how will this affect other users of inlined data.
> Especially for symbol links.
>
> Symbol links always store they link source inside an inline data file
> extent. Does such content also get encrypted?
Symlinks are passed to the fscrypt API and encrypted if needed, using
ext4_symlink() as an example.
Powered by blists - more mailing lists