On 2016-03-01 11:46, Chris Mason wrote:
On Tue, Mar 01, 2016 at 05:29:52PM +0100, Tomasz Torcz wrote:
On Wed, Mar 02, 2016 at 12:08:09AM +0800, Anand Jain wrote:
This patchset adds btrfs encryption support.
Warning:
The code is in prototype/experimental stage and is not suitable
for the production data yet.
Can you share some design documents? Will it be compatible
with existing encrypting filesystems:
– ext4 ?
– ZFS ?
It would be nice to have common API for encryption, not a dozen
of filesystem-specific interfaces.
We'll definitely move in line with the common API over time. Thanks
Anand for starting this!
I'd prefer that we keep it per-subvolume for now, just because
subvolumes are so cheap and because it seems like a better collection
point for general use. But as the other filesystems add features we'll
make sure and keep parity with what users expect.
I hate to tell you, but if you want feature parity, it needs to have \
per-file functionality from the start. Both ext4 and F2FS do per-file,
as does NTFS (not certain about ZFS, but people are not as likely to be
coming to BTRFS from ZFS as they are from ext4 or F2FS from what I've seen).
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
