The patch titled
fuse: fix oops in revalidate when called with NULL nameidata
has been added to the -mm tree. Its filename is
fuse-fix-oops-in-revalidate-when-called-with-null-nameidata.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: fuse: fix oops in revalidate when called with NULL nameidata
From: Miklos Szeredi <mszeredi@xxxxxxx>
Some cases (e.g. ecryptfs) can call ->dentry_revalidate with NULL
nameidata.
Tyler Hicks pointed out that this bug was introduced by commit e7c0a16786
"fuse: make fuse_dentry_revalidate() RCU aware"
Addresses https://bugzilla.kernel.org/show_bug.cgi?id=34732
Reported-by: Witold Baryluk <baryluk@xxxxxxxxxxxxxxxx>
Signed-off-by: Miklos Szeredi <mszeredi@xxxxxxx>
Cc: Tyler Hicks <tyhicks@xxxxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
fs/fuse/dir.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -puN fs/fuse/dir.c~fuse-fix-oops-in-revalidate-when-called-with-null-nameidata fs/fuse/dir.c
--- a/fs/fuse/dir.c~fuse-fix-oops-in-revalidate-when-called-with-null-nameidata
+++ a/fs/fuse/dir.c
@@ -174,7 +174,7 @@ static int fuse_dentry_revalidate(struct
if (!inode)
return 0;
- if (nd->flags & LOOKUP_RCU)
+ if (nd && (nd->flags & LOOKUP_RCU))
return -ECHILD;
fc = get_fuse_conn(inode);
_
Patches currently in -mm which might be from mszeredi@xxxxxxx are
fuse-fix-oops-in-revalidate-when-called-with-null-nameidata.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
