The patch titled
autofs4: pending flag not cleared on mount fail
has been added to the -mm tree. Its filename is
autofs4-pending-flag-not-cleared-on-mount-fail.patch
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: autofs4: pending flag not cleared on mount fail
From: Ian Kent <raven@xxxxxxxxxx>
During testing I've found that the mount pending flag can be left set at
exit from autofs4_lookup after a failed mount request. This shouldn't be
allowed to happen and causes incorrect error returns.
Signed-off-by: Ian Kent <raven@xxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
fs/autofs4/root.c | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff -puN fs/autofs4/root.c~autofs4-pending-flag-not-cleared-on-mount-fail fs/autofs4/root.c
--- a/fs/autofs4/root.c~autofs4-pending-flag-not-cleared-on-mount-fail
+++ a/fs/autofs4/root.c
@@ -281,9 +281,6 @@ static int try_to_fill_dentry(struct den
DPRINTK("mount done status=%d", status);
- if (status && dentry->d_inode)
- return status; /* Try to get the kernel to invalidate this dentry */
-
/* Turn this into a real negative dentry? */
if (status == -ENOENT) {
spin_lock(&dentry->d_lock);
@@ -540,6 +537,9 @@ static struct dentry *autofs4_lookup(str
return ERR_PTR(-ERESTARTNOINTR);
}
}
+ spin_lock(&dentry->d_lock);
+ dentry->d_flags &= ~DCACHE_AUTOFS_PENDING;
+ spin_unlock(&dentry->d_lock);
}
/*
_
Patches currently in -mm which might be from raven@xxxxxxxxxx are
autofs4-needs-to-force-fail-return-revalidate.patch
autofs4-autofs4_follow_link-false-negative-fix.patch
autofs4-pending-flag-not-cleared-on-mount-fail.patch
autofs-make-sure-all-dentries-refs-are-released-before-calling-kill_anon_super.patch
vfs-destroy-the-dentries-contributed-by-a-superblock-on-unmounting.patch
fs-kconfig-split-autofs.patch
fs-kconfig-split-autofs4.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
