All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Biggers <ebiggers@kernel.org>
To: linux-fscrypt@vger.kernel.org
Cc: Daniel Rosenberg <drosen@google.com>
Subject: Re: [PATCH 0/4] fscrypt: fscrypt_supported_policy() fixes and cleanups
Date: Fri, 3 Jan 2020 09:00:20 -0800	[thread overview]
Message-ID: <20200103170020.GI19521@gmail.com> (raw)
In-Reply-To: <20191209211829.239800-1-ebiggers@kernel.org>

On Mon, Dec 09, 2019 at 01:18:25PM -0800, Eric Biggers wrote:
> Make FS_IOC_SET_ENCRYPTION_POLICY start rejecting the DIRECT_KEY flag
> when it's incompatible with the selected encryption modes, instead of
> delaying this check until later when actually trying to set up the
> directory's key.
> 
> Also make some related cleanups, such as splitting
> fscrypt_supported_policy() into a separate function for each encryption
> policy version.
> 
> Eric Biggers (4):
>   fscrypt: split up fscrypt_supported_policy() by policy version
>   fscrypt: check for appropriate use of DIRECT_KEY flag earlier
>   fscrypt: move fscrypt_valid_enc_modes() to policy.c
>   fscrypt: remove fscrypt_is_direct_key_policy()
> 
>  fs/crypto/fscrypt_private.h |  30 +------
>  fs/crypto/keysetup.c        |  14 +---
>  fs/crypto/keysetup_v1.c     |  15 ----
>  fs/crypto/policy.c          | 163 +++++++++++++++++++++++-------------
>  4 files changed, 111 insertions(+), 111 deletions(-)
> 
> -- 
> 2.24.0.393.g34dc348eaf-goog
> 

All applied to fscrypt.git#master for 5.6.

- Eric

      parent reply	other threads:[~2020-01-03 17:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-09 21:18 [PATCH 0/4] fscrypt: fscrypt_supported_policy() fixes and cleanups Eric Biggers
2019-12-09 21:18 ` [PATCH 1/4] fscrypt: split up fscrypt_supported_policy() by policy version Eric Biggers
2019-12-09 21:18 ` [PATCH 2/4] fscrypt: check for appropriate use of DIRECT_KEY flag earlier Eric Biggers
2019-12-09 21:18 ` [PATCH 3/4] fscrypt: move fscrypt_valid_enc_modes() to policy.c Eric Biggers
2019-12-09 21:18 ` [PATCH 4/4] fscrypt: remove fscrypt_is_direct_key_policy() Eric Biggers
2020-01-03 17:00 ` Eric Biggers [this message]

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=20200103170020.GI19521@gmail.com \
    --to=ebiggers@kernel.org \
    --cc=drosen@google.com \
    --cc=linux-fscrypt@vger.kernel.org \
    /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.