NFSv4.1: Don't change the security label as part of open reclaim.
The current caching model calls for the security label to be set on first lookup and/or on any subsequent label changes. There is no need to do it as part of an open reclaim. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
This commit is contained in:
parent
1966903f8e
commit
83c78eb042
|
@ -1337,8 +1337,6 @@ _nfs4_opendata_reclaim_to_nfs4_state(struct nfs4_opendata *data)
|
||||||
if (ret)
|
if (ret)
|
||||||
goto err;
|
goto err;
|
||||||
|
|
||||||
nfs_setsecurity(inode, &data->f_attr, data->f_label);
|
|
||||||
|
|
||||||
if (data->o_res.delegation_type != 0)
|
if (data->o_res.delegation_type != 0)
|
||||||
nfs4_opendata_check_deleg(data, state);
|
nfs4_opendata_check_deleg(data, state);
|
||||||
update_open_stateid(state, &data->o_res.stateid, NULL,
|
update_open_stateid(state, &data->o_res.stateid, NULL,
|
||||||
|
|
Loading…
Reference in New Issue