ext4: fix typo which broke '..' detection in ext4_find_entry()

There should be a check for the NUL character instead of '0'. Fortunately the only thing that cares about this is NFS serving, which is why we didn't notice this in the merge window testing. Reported-by: Phil Carmody <[email protected]> Signed-off-by: Aaro Koskinen <[email protected]> Signed-off-by: "Theodore Ts'o" <[email protected]>
josf · Dec 15, 2010 · 6d5c3aa · 6d5c3aa
1 parent 1449032
commit 6d5c3aa
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/fs/ext4/namei.c b/fs/ext4/namei.c
@@ -872,7 +872,7 @@ static struct buffer_head * ext4_find_entry (struct inode *dir,
 	if (namelen > EXT4_NAME_LEN)
 		return NULL;
 	if ((namelen <= 2) && (name[0] == '.') &&
-	    (name[1] == '.' || name[1] == '0')) {
+	    (name[1] == '.' || name[1] == '\0')) {
 		/*
 		 * "." or ".." will only be in the first block
 		 * NFS may look up ".."; "." should be handled by the VFS