diff options
author | Al Viro <viro@zeniv.linux.org.uk> | 2011-03-09 01:34:45 -0500 |
---|---|---|
committer | Al Viro <viro@zeniv.linux.org.uk> | 2011-03-14 09:15:27 -0400 |
commit | f374ed5fa8afed8590deaae5dc147422e0e1a6d9 (patch) | |
tree | 76bf116e7a8c75be60734527dd804632dee8a95b /fs/ecryptfs | |
parent | 6c0d46c493217cf48999b3f8808910ae534aa085 (diff) | |
download | linux-f374ed5fa8afed8590deaae5dc147422e0e1a6d9.tar.gz linux-f374ed5fa8afed8590deaae5dc147422e0e1a6d9.tar.bz2 linux-f374ed5fa8afed8590deaae5dc147422e0e1a6d9.zip |
do_last: kill a rudiment of old ->d_revalidate() workaround
There used to be time when ->d_revalidate() couldn't return an error.
So intents code had lookup_instantiate_filp() stash ERR_PTR(error)
in nd->intent.open.filp and had it checked after lookup_hash(), to
catch the otherwise silent failures. That had been introduced by
commit 4af4c52f34606bdaab6930a845550c6fb02078a4. These days
->d_revalidate() can and does propagate errors back to callers
explicitly, so this check isn't needed anymore.
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
Diffstat (limited to 'fs/ecryptfs')
0 files changed, 0 insertions, 0 deletions