diff options
author | Jaegeuk Kim <jaegeuk@kernel.org> | 2017-04-24 10:00:08 -0700 |
---|---|---|
committer | Theodore Ts'o <tytso@mit.edu> | 2017-05-04 11:44:35 -0400 |
commit | 6332cd32c8290a80e929fc044dc5bdba77396e33 (patch) | |
tree | 24f76cfe6d3dddfd9aa15189ee6445584f71fee6 /fs/crypto/fname.c | |
parent | 413d5a9edbb45eec4dbb1904fe689b561ea5d143 (diff) | |
download | linux-6332cd32c8290a80e929fc044dc5bdba77396e33.tar.bz2 |
f2fs: check entire encrypted bigname when finding a dentry
If user has no key under an encrypted dir, fscrypt gives digested dentries.
Previously, when looking up a dentry, f2fs only checks its hash value with
first 4 bytes of the digested dentry, which didn't handle hash collisions fully.
This patch enhances to check entire dentry bytes likewise ext4.
Eric reported how to reproduce this issue by:
# seq -f "edir/abcdefghijklmnopqrstuvwxyz012345%.0f" 100000 | xargs touch
# find edir -type f | xargs stat -c %i | sort | uniq | wc -l
100000
# sync
# echo 3 > /proc/sys/vm/drop_caches
# keyctl new_session
# find edir -type f | xargs stat -c %i | sort | uniq | wc -l
99999
Cc: <stable@vger.kernel.org>
Reported-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
(fixed f2fs_dentry_hash() to work even when the hash is 0)
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Diffstat (limited to 'fs/crypto/fname.c')
0 files changed, 0 insertions, 0 deletions