]> git.hungrycats.org Git - linux/commit
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)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Fri, 7 Jun 2013 19:46:35 +0000 (12:46 -0700)
commitdae84f25ac695ff740ce1ca2226e5451ba296fc3
tree918f285ff481610f6ca84225ec997691ee5662e5
parentc2ecac559adaf4a9413a01d3601006320e345d96
cifs: only set ops for inodes in I_NEW state

commit c2b93e0699723700f886ce17bb65ffd771195a6d upstream.

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.

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: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/cifs/inode.c