ext4 crypto: add ext4 encryption facilities
authorMichael Halcrow <mhalcrow@google.com>
Sun, 12 Apr 2015 04:43:56 +0000 (00:43 -0400)
committerTheodore Ts'o <tytso@mit.edu>
Sun, 12 Apr 2015 04:43:56 +0000 (00:43 -0400)
commitb30ab0e03407d2aa2d9316cba199c757e4bfc8ad
tree900754eb3fe069f90bb5ea2c1df1ed88cf701eb5
parent9bd8212f981ea6375911fe055382ad7529be5b28
ext4 crypto: add ext4 encryption facilities

On encrypt, we will re-assign the buffer_heads to point to a bounce
page rather than the control_page (which is the original page to write
that contains the plaintext). The block I/O occurs against the bounce
page.  On write completion, we re-assign the buffer_heads to the
original plaintext page.

On decrypt, we will attach a read completion callback to the bio
struct. This read completion will decrypt the read contents in-place
prior to setting the page up-to-date.

The current encryption mode, AES-256-XTS, lacks cryptographic
integrity. AES-256-GCM is in-plan, but we will need to devise a
mechanism for handling the integrity data.

Signed-off-by: Michael Halcrow <mhalcrow@google.com>
Signed-off-by: Ildar Muslukhov <ildarm@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
fs/ext4/Makefile
fs/ext4/crypto.c [new file with mode: 0644]
fs/ext4/crypto_policy.c
fs/ext4/ext4.h
fs/ext4/ext4_crypto.h
fs/ext4/super.c