ext4 crypto: separate kernel and userspace structure for the key
authorTheodore Ts'o <tytso@google.com>
Mon, 4 May 2015 23:35:03 +0000 (19:35 -0400)
committerIan Chang <ianc@nvidia.com>
Wed, 1 Jun 2016 05:00:03 +0000 (13:00 +0800)
commit923fdbbdf8d13528aeb6e214b191432aba812829
tree0a238522cc185d07c7701d945cf2990e147f5f81
parentc3fbc3fc5140cb96d29e225c74008321f5f75de7
ext4 crypto: separate kernel and userspace structure for the key

Use struct ext4_encryption_key only for the master key passed via the
kernel keyring.

For internal kernel space users, we now use struct ext4_crypt_info.
This will allow us to put information from the policy structure so we
can cache it and avoid needing to constantly looking up the extended
attribute.  We will do this in a spearate patch.  This patch is mostly
mechnical to make it easier for patch review.

Change-Id: I208472675d0550df5f60b3b58652a9a1b434caed
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Theodore Ts'o <tytso@google.com>
fs/ext4/crypto.c
fs/ext4/crypto_fname.c
fs/ext4/crypto_key.c
fs/ext4/ext4.h
fs/ext4/ext4_crypto.h
fs/ext4/super.c