NFSv4: Don't ask for delegated attributes when revalidating the inode
Again, when revalidating the inode, we don't need to ask for attributes for which we are authoritative. Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
This commit is contained in:
parent
a841b54dbd
commit
771734f291
|
@ -3832,9 +3832,10 @@ static int _nfs4_proc_getattr(struct nfs_server *server, struct nfs_fh *fhandle,
|
|||
struct nfs_fattr *fattr, struct nfs4_label *label,
|
||||
struct inode *inode)
|
||||
{
|
||||
__u32 bitmask[NFS4_BITMASK_SZ];
|
||||
struct nfs4_getattr_arg args = {
|
||||
.fh = fhandle,
|
||||
.bitmask = server->attr_bitmask,
|
||||
.bitmask = bitmask,
|
||||
};
|
||||
struct nfs4_getattr_res res = {
|
||||
.fattr = fattr,
|
||||
|
@ -3847,7 +3848,7 @@ static int _nfs4_proc_getattr(struct nfs_server *server, struct nfs_fh *fhandle,
|
|||
.rpc_resp = &res,
|
||||
};
|
||||
|
||||
args.bitmask = nfs4_bitmask(server, label);
|
||||
nfs4_bitmap_copy_adjust(bitmask, nfs4_bitmask(server, label), inode);
|
||||
|
||||
nfs_fattr_init(fattr);
|
||||
return nfs4_call_sync(server->client, server, &msg, &args.seq_args, &res.seq_res, 0);
|
||||
|
|
Loading…
Reference in a new issue