On Tue, Sep 13, 2016 at 09:39:46PM +0800, Anand Jain wrote: > This patchset adds btrfs encryption support. > > The main objective of this series is to have bugs fixed and stability. > I have verified with fstests to confirm that there is no regression. > > A design write-up is coming next,
You're approaching it from the wrong side. The detailed specification must come first. Don't bother to send the code again. > however here below is the quick example > on the cli usage. Please try out, let me know if I have missed something. > > Also would like to mention that a review from the security experts is due, > which is important and I believe those review comments can be accommodated > without major changes from here. I disagree. Others commented on the crypto stuff, I see enough points to address that would lead to major changes. > Also yes, thanks for the emails, I hear, per file encryption and inline > with vfs layer is also important, which is wip among other things in the > list. Implementing the recent vfs encryption in btrfs is ok, it's just feature parity using an existing API. And a note from me with maintainer's hat on, there are enough pending patches and patchsets that need review, and bugs to fix, I'm not going to spend time on something that we don't need at the moment if there are alternatives. -- 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
