From: Al Viro <viro@zeniv.linux.org.uk>
Date: Thu, 4 Dec 2008 14:59:23 +0000 (-0500)
Subject: ntfs: don't NULL i_op
X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=9742df331deb3fce95b321f38d4ea0c4e75edb63;p=GitHub%2Fexynos8895%2Fandroid_kernel_samsung_universal8895.git

ntfs: don't NULL i_op

it's already set to empty table (and no, ntfs doesn't have any explicit
checks for NULL ->i_op or NULL ->i_fop)

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
---

diff --git a/fs/ntfs/inode.c b/fs/ntfs/inode.c
index e9da092e2772..86bef156cf0a 100644
--- a/fs/ntfs/inode.c
+++ b/fs/ntfs/inode.c
@@ -1406,9 +1406,6 @@ static int ntfs_read_locked_attr_inode(struct inode *base_vi, struct inode *vi)
 		ni->allocated_size = sle64_to_cpu(
 				a->data.non_resident.allocated_size);
 	}
-	/* Setup the operations for this attribute inode. */
-	vi->i_op = NULL;
-	vi->i_fop = NULL;
 	if (NInoMstProtected(ni))
 		vi->i_mapping->a_ops = &ntfs_mst_aops;
 	else