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 <smfrench@gmail.com>
Wed, 8 May 2013 22:12:47 +0000 (17:12 -0500)
commitc2b93e0699723700f886ce17bb65ffd771195a6d
tree174d082487c61ca59e166c5f0b906595f6facc5a
parentebb37277796269da36a8bc5d72ed1e8e1fb7d34b
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>
fs/cifs/inode.c