fscrypt: drop max_namelen check from fname_decrypt()
authorEric Biggers <ebiggers@google.com>
Mon, 30 Apr 2018 22:51:42 +0000 (15:51 -0700)
committerJaegeuk Kim <jaegeuk@kernel.org>
Thu, 28 Jun 2018 16:37:40 +0000 (09:37 -0700)
commit219e65410cae6cad0d61a059d0128005002875cf
treee070fbed55d68ac2c119357ec5de29f1475df8b5
parentef1def58e2fd6b9a74dfc7f9915ccdba1d1281d6
fscrypt: drop max_namelen check from fname_decrypt()

fname_decrypt() returns an error if the input filename is longer than
the inode's ->max_namelen() as given by the filesystem.  But, this
doesn't actually make sense because the filesystem provided the input
filename in the first place, where it was subject to the filesystem's
limits.  And fname_decrypt() has no internal limit itself.

Thus, remove this unnecessary check.

Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
fs/crypto/fname.c