cifs: only set ops for inodes in I_NEW state
authorJeff Layton <jlayton@redhat.com>
Tue, 7 May 2013 15:28:31 +0000 (11:28 -0400)
committerSteve French <sfrench@us.ibm.com>
Fri, 24 May 2013 17:55:39 +0000 (12:55 -0500)
commit62106e96279f66c52e2123782f9420af9dbe8cbe
treed008f1b2ff13541b62c562cdb061ecdd1acd06dd
parent0e255f1c0c9add2f0c920240ac4cadc28ae274c3
cifs: only set ops for inodes in I_NEW state

It's generally not safe to reset the inode ops once they've been set. In
the case where the inode was originally thought to be a directory and
then later found to be a DFS referral, this can lead to an oops when we
try to trigger an inode op on it after changing the ops to the blank
referral operations.

Cc: <stable@vger.kernel.org>
Reported-and-Tested-by: Sachin Prabhu <sprabhu@redhat.com>
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Signed-off-by: Steve French <smfrench@gmail.com>
Signed-off-by: Steve French <sfrench@us.ibm.com>
fs/cifs/inode.c