mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-28 10:41:38 -04:00
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: <[email protected]> Reported-and-Tested-by: Sachin Prabhu <[email protected]> Signed-off-by: Jeff Layton <[email protected]> Signed-off-by: Steve French <[email protected]> Signed-off-by: Steve French <[email protected]>
This commit is contained in:
parent
0e255f1c0c
commit
62106e9627
1 changed files with 2 additions and 1 deletions
|
|
@ -171,7 +171,8 @@ cifs_fattr_to_inode(struct inode *inode, struct cifs_fattr *fattr)
|
|||
|
||||
if (fattr->cf_flags & CIFS_FATTR_DFS_REFERRAL)
|
||||
inode->i_flags |= S_AUTOMOUNT;
|
||||
cifs_set_ops(inode);
|
||||
if (inode->i_state & I_NEW)
|
||||
cifs_set_ops(inode);
|
||||
}
|
||||
|
||||
void
|
||||
|
|
|
|||
Loading…
Reference in a new issue