summaryrefslogtreecommitdiffstats
path: root/fs/hfsplus/wrapper.c
diff options
context:
space:
mode:
authorIan Kent <raven@themaw.net>2017-02-27 14:27:16 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2017-02-27 18:43:45 -0800
commit092a53452bb7a6ca436b2d3859e7b1f1ec45479f (patch)
treebac0523edfd04c640c961b6b2a849f48fa684370 /fs/hfsplus/wrapper.c
parent3bb2fbdaba16386f520b5750d649a30643a4ab9e (diff)
downloadlinux-092a53452bb7a6ca436b2d3859e7b1f1ec45479f.tar.bz2
autofs: take more care to not update last_used on path walk
GUI environments seem to be becoming more agressive at scanning filesystems, to the point where autofs cannot expire mounts at all. This is one key reason the update of the autofs dentry info last_used field is done in the expire system when the dentry is seen to be in use. But somewhere along the way instances of the update has crept back into the autofs path walk functions which, with the more aggressive file access patterns, is preventing expiration. Changing the update in the path walk functions allows autofs to at least make progress in spite of frequent immediate re-mounts from file accesses. Link: http://lkml.kernel.org/r/148577167169.9801.1377050092212016834.stgit@pluto.themaw.net Signed-off-by: Ian Kent <raven@themaw.net> Cc: Tomohiro Kusumi <tkusumi@tuxera.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'fs/hfsplus/wrapper.c')
0 files changed, 0 insertions, 0 deletions