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>
Showing
- fs/ext4/Makefile 1 addition, 1 deletionfs/ext4/Makefile
- fs/ext4/crypto.c 558 additions, 0 deletionsfs/ext4/crypto.c
- fs/ext4/crypto_policy.c 8 additions, 0 deletionsfs/ext4/crypto_policy.c
- fs/ext4/ext4.h 52 additions, 0 deletionsfs/ext4/ext4.h
- fs/ext4/ext4_crypto.h 55 additions, 0 deletionsfs/ext4/ext4_crypto.h
- fs/ext4/super.c 8 additions, 0 deletionsfs/ext4/super.c
Loading
Please register or sign in to comment