diff options
| author | Jaegeuk Kim | 2016-02-06 04:37:27 +0100 |
|---|---|---|
| committer | Jaegeuk Kim | 2016-02-23 01:07:23 +0100 |
| commit | 1dafa51d45c6332f255faee101d9c47eb56ea7c7 (patch) | |
| tree | 9a555cf6ecacc8d20e3ee153836a2297e69f541e /fs/f2fs/crypto_key.c | |
| parent | f2fs crypto: f2fs_page_crypto() doesn't need a encryption context (diff) | |
| download | kernel-qcow2-linux-1dafa51d45c6332f255faee101d9c47eb56ea7c7.tar.gz kernel-qcow2-linux-1dafa51d45c6332f255faee101d9c47eb56ea7c7.tar.xz kernel-qcow2-linux-1dafa51d45c6332f255faee101d9c47eb56ea7c7.zip | |
f2fs crypto: check for too-short encrypted file names
This patch adopts:
ext4 crypto: check for too-short encrypted file names
An encrypted file name should never be shorter than an 16 bytes, the
AES block size. The 3.10 crypto layer will oops and crash the kernel
if ciphertext shorter than the block size is passed to it.
Fortunately, in modern kernels the crypto layer will not crash the
kernel in this scenario, but nevertheless, it represents a corrupted
directory, and we should detect it and mark the file system as
corrupted so that e2fsck can fix this.
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs/f2fs/crypto_key.c')
0 files changed, 0 insertions, 0 deletions