From: Anand Jain <anand.jain@oracle.com>
To: Chris Murphy <lists@colorremedies.com>,
Filip Bystricky <filipbystricky@google.com>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs native encryption
Date: Sun, 11 Jun 2017 02:31:32 +0900 [thread overview]
Message-ID: <593C2CF4.8000509@oracle.com> (raw)
In-Reply-To: <CAJCQCtRvzveHJuzRg9fqTAiPNpjAQxaZbcf+t1E65hojhzXaXQ@mail.gmail.com>
> dealing with inheritance of
> encryption when making snapshots, and dealing with reflinks.
Right. To address this, there is a proposal to bring encryption down
to the extent level, it solves these limitations.
Thanks, Anand
next prev parent reply other threads:[~2017-06-10 18:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 15:50 btrfs native encryption Filip Bystricky
2017-06-09 16:03 ` Hugo Mills
2017-06-10 17:22 ` Anand Jain
2017-06-09 18:09 ` Chris Murphy
2017-06-10 17:31 ` Anand Jain [this message]
2017-06-12 12:40 ` David Sterba
2017-06-12 12:46 ` David Sterba
-- strict thread matches above, loose matches on Subject: below --
2020-04-26 13:54 Btrfs " Neal Gompa
2020-04-26 14:14 ` Nikolay Borisov
2020-04-26 14:25 ` Mark Harmstone
2020-04-27 4:49 ` Chris Murphy
2020-04-27 8:00 ` Mark Harmstone
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=593C2CF4.8000509@oracle.com \
--to=anand.jain@oracle.com \
--cc=filipbystricky@google.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.