summaryrefslogtreecommitdiffstats
path: root/init
diff options
context:
space:
mode:
authorIan Kent <raven@themaw.net>2006-09-27 01:50:44 -0700
committerLinus Torvalds <torvalds@g5.osdl.org>2006-09-27 08:26:17 -0700
commitbcdc5e019d9f525a9f181a7de642d3a9c27c7610 (patch)
treec2a93b8456095b260bee2be6e169c116f4b0be84 /init
parent1183dc943cae8b0fddca0b310c26052b2355e04b (diff)
downloadlinux-bcdc5e019d9f525a9f181a7de642d3a9c27c7610.tar.gz
linux-bcdc5e019d9f525a9f181a7de642d3a9c27c7610.tar.bz2
linux-bcdc5e019d9f525a9f181a7de642d3a9c27c7610.zip
[PATCH] autofs4 needs to force fail return revalidate
For a long time now I have had a problem with not being able to return a lookup failure on an existsing directory. In autofs this corresponds to a mount failure on a autofs managed mount entry that is browsable (and so the mount point directory exists). While this problem has been present for a long time I've avoided resolving it because it was not very visible. But now that autofs v5 has "mount and expire on demand" of nested multiple mounts, such as is found when mounting an export list from a server, solving the problem cannot be avoided any longer. I've tried very hard to find a way to do this entirely within the autofs4 module but have not been able to find a satisfactory way to achieve it. So, I need to propose a change to the VFS. Signed-off-by: Ian Kent <raven@themaw.net> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions