diff options
author | Ian Kent <raven@themaw.net> | 2008-07-24 08:30:25 +0400 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2008-07-24 21:47:32 +0400 |
commit | 26e81b3142f1ba497d4cd0365c13661684b784ce (patch) | |
tree | b21545ceca70a0e93da1e4e6b19b5dcb99549d2d /fs/autofs4/expire.c | |
parent | ff9cd499d6258952385cb2f12e9a3c0908fd5786 (diff) | |
download | linux-26e81b3142f1ba497d4cd0365c13661684b784ce.tar.xz |
autofs4: fix pending checks
There are two cases for which a dentry that has a pending mount request
does not wait for completion. One is via autofs4_revalidate() and the
other via autofs4_follow_link().
In revalidate, after the mount point directory is created, but before the
mount is done, the check in try_to_fill_dentry() can can fail to send the
dentry to the wait queue since the dentry is positive and the lookup flags
may contain only LOOKUP_FOLLOW. Although we don't trigger a mount for the
LOOKUP_FOLLOW flag, if ther's one pending we might as well wait and use
the mounted dentry for the lookup.
In autofs4_follow_link() the dentry is not checked to see if it is pending
so it may fail to call try_to_fill_dentry() and not wait for mount
completion.
A dentry that is pending must always be sent to the wait queue.
Signed-off-by: Ian Kent <raven@themaw.net>
Reviewed-by: Jeff Moyer <jmoyer@redhat.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/autofs4/expire.c')
0 files changed, 0 insertions, 0 deletions