On Wed, Aug 06, 2014 at 01:27:21PM +1000, Chris Dunlop wrote: > [resend, with corrected stable address] > > Please consider including the following commit in 3.10.x, to avoid > umountable NFS filesystems in certain cases: > > ---------------------------------------------------------------------- > commit 8033426e6bdb2690d302872ac1e1fadaec1a5581 > Author: Jeff Layton <jlayton@xxxxxxxxxx> > Date: Fri Jul 26 06:23:25 2013 -0400 > > vfs: allow umount to handle mountpoints without revalidating them Apologies, I should have looked at this harder, there are further patches involved in fixing this issue, and not all of them apply cleanly (starting at b18825a7): 8033426e vfs: allow umount to handle mountpoints without revalidating them 35759521 take unlazy_walk() into umount_lookup_last() 197df04c rename user_path_umountat() to user_path_mountpoint_at() 2d864651 introduce kern_path_mountpoint() bcceeeba Add missing unlocks to error paths of mountpoint_last. b18825a7 VFS: Put a small type field into struct dentry::d_flags 22213318 fix races between __d_instantiate() and checks of dentry flags 295dc39d fs: umount on symlink leaks mnt count I'm not confident I can correctly work out what needs to be done here, so I'll withdraw this backport request unless someone more knowledgable would like to take it on. Cheers, Chris -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html