ntfs: don't NULL i_op
authorAl Viro <viro@zeniv.linux.org.uk>
Thu, 4 Dec 2008 14:59:23 +0000 (09:59 -0500)
committerAl Viro <viro@zeniv.linux.org.uk>
Mon, 5 Jan 2009 16:54:27 +0000 (11:54 -0500)
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>
fs/ntfs/inode.c

index e9da092e27723a91d5c2bc9bd60a1645b494ca00..86bef156cf0a15b277d879021b24138a333d4eeb 100644 (file)
@@ -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