linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Eric Biggers <ebiggers3@gmail.com>, linux-fsdevel@vger.kernel.org
Cc: Theodore Ts'o <tytso@mit.edu>, Jaegeuk Kim <jaegeuk@kernel.org>,
	Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH] fscrypt: make fscrypt_operations.key_prefix a string
Date: Fri, 6 Jan 2017 01:01:14 +0100	[thread overview]
Message-ID: <e02f850a-902c-3506-263e-dd39c950cf7a@nod.at> (raw)
In-Reply-To: <20170105215118.108712-1-ebiggers3@gmail.com>

Am 05.01.2017 um 22:51 schrieb Eric Biggers:
> From: Eric Biggers <ebiggers@google.com>
> 
> There was an unnecessary amount of complexity around requesting the
> filesystem-specific key prefix.  It was unclear why; perhaps it was
> envisioned that different instances of the same filesystem type could
> use different key prefixes, or that key prefixes could be binary.

This complexity was also never clear to me.

> However, neither of those things were implemented or really make sense
> at all.  So simplify the code by making key_prefix a const char *.
> 
> Signed-off-by: Eric Biggers <ebiggers@google.com>
> ---
>  fs/crypto/keyinfo.c      | 31 +++++++++++--------------------
>  fs/ext4/ext4.h           | 11 -----------
>  fs/ext4/super.c          | 13 +------------
>  fs/f2fs/f2fs.h           |  9 ---------
>  fs/f2fs/super.c          | 14 +-------------
>  fs/ubifs/crypto.c        | 11 +----------
>  include/linux/fscrypto.h |  2 +-
>  7 files changed, 15 insertions(+), 76 deletions(-)

Reviewed-by: Richard Weinberger <richard@nod.at>

Thanks,
//richard

  reply	other threads:[~2017-01-06  0:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-05 21:51 [PATCH] fscrypt: make fscrypt_operations.key_prefix a string Eric Biggers
2017-01-06  0:01 ` Richard Weinberger [this message]
2017-01-08  6:08 ` 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=e02f850a-902c-3506-263e-dd39c950cf7a@nod.at \
    --to=richard@nod.at \
    --cc=ebiggers3@gmail.com \
    --cc=ebiggers@google.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --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).