[PATCH 44/88] fuse: don't WARN when nlink is zero
Luis Henriques
luis.henriques at canonical.com
Thu Mar 14 10:35:37 UTC 2013
3.5.7.8 -stable review patch. If anyone has any objections, please let me know.
------------------
From: Miklos Szeredi <mszeredi at suse.cz>
commit dfca7cebc2679f3d129f8e680a8f199a7ad16e38 upstream.
drop_nlink() warns if nlink is already zero. This is triggerable by a buggy
userspace filesystem. The cure, I think, is worse than the disease so disable
the warning.
Reported-by: Tero Roponen <tero.roponen at gmail.com>
Signed-off-by: Miklos Szeredi <mszeredi at suse.cz>
Signed-off-by: Luis Henriques <luis.henriques at canonical.com>
---
fs/fuse/dir.c | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/fs/fuse/dir.c b/fs/fuse/dir.c
index 334e0b1..f6e4bc8 100644
--- a/fs/fuse/dir.c
+++ b/fs/fuse/dir.c
@@ -645,7 +645,14 @@ static int fuse_unlink(struct inode *dir, struct dentry *entry)
spin_lock(&fc->lock);
fi->attr_version = ++fc->attr_version;
- drop_nlink(inode);
+ /*
+ * If i_nlink == 0 then unlink doesn't make sense, yet this can
+ * happen if userspace filesystem is careless. It would be
+ * difficult to enforce correct nlink usage so just ignore this
+ * condition here
+ */
+ if (inode->i_nlink > 0)
+ drop_nlink(inode);
spin_unlock(&fc->lock);
fuse_invalidate_attr(inode);
fuse_invalidate_attr(dir);
--
1.8.1.2
More information about the kernel-team
mailing list