]> git.ipfire.org Git - thirdparty/kernel/stable.git/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:52:26 +0000 (12:52 -0700)
commit92f3a29f74d31f4d2d055e0eaeb21145019c4a0a
tree1858369fa50b3e9b03c05dc64a247c77ae961566
parent3343e275c00997a0c68485434f149302830a2583
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