f2fs crypto: check for too-short encrypted file names
authorJaegeuk Kim <jaegeuk@kernel.org>
Sat, 6 Feb 2016 03:37:27 +0000 (19:37 -0800)
committerJaegeuk Kim <jaegeuk@kernel.org>
Tue, 23 Feb 2016 00:07:23 +0000 (16:07 -0800)
commit1dafa51d45c6332f255faee101d9c47eb56ea7c7
tree9a555cf6ecacc8d20e3ee153836a2297e69f541e
parentce855a3bd0922f548a3c4937d6447c2ed4d4b1bc
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>
fs/f2fs/crypto_fname.c
This page took 0.025262 seconds and 5 git commands to generate.