From: Eric Biggers <ebiggers@google.com>
To: Richard Weinberger <richard@nod.at>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, tytso@mit.edu, jaegeuk@kernel.org
Subject: Re: [PATCH] MAINTAINERS: fscrypto: recommend linux-fsdevel for fscrypto patches
Date: Mon, 24 Oct 2016 15:58:26 -0700 [thread overview]
Message-ID: <20161024225826.GC83082@google.com> (raw)
In-Reply-To: <8426b631-dc03-b45a-ec58-fc3ae5cdf0c9@nod.at>
On Mon, Oct 24, 2016 at 10:44:41PM +0200, Richard Weinberger wrote:
> That's a very good idea!
> Do we also have designated git tree for fscrypto?
> As soon UBIFS file encryption is mainline I'll have to monitor changes
> to fscrypto very closely because changes in fscrypto could introduce
> changes in the on-flash format of UBIFS.
> i.e. a subtle change in filename encryption... :-)
There isn't yet a dedicated fscrypto tree. Ted has been taking in most of my
fscrypto patches through the ext4 tree.
This was discussed briefly before, but as designed filesystems do not need to be
aware of the format of the xattr (fscrypt_context) or the format of the
encrypted data per se. Thus, new modes/formats can be introduced without
requiring changes to filesystem-specific code. The point that was brought up is
whether some filesystems would additionally like to track in their superblock
which encryption modes and flags are used and either deny mounts or warn at
mount-time if some are unrecognized. So it should be decided soon if UBIFS is
going to do that or not.
Eric
next prev parent reply other threads:[~2016-10-24 22:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 20:29 [PATCH] MAINTAINERS: fscrypto: recommend linux-fsdevel for fscrypto patches Eric Biggers
2016-10-24 20:44 ` Richard Weinberger
2016-10-24 22:58 ` Eric Biggers [this message]
2016-11-26 20:05 ` Theodore Ts'o
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=20161024225826.GC83082@google.com \
--to=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=tytso@mit.edu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).