Re: [Nfs-ganesha-devel] Attribute refresh on rename

2016-10-14 Thread Daniel Gryniewicz
It should. It should invalidate the attributes on mdc_lookup_dst, which is what you wanted. Daniel On 10/13/2016 01:29 PM, Frank Filz wrote: >> I suspect the correct solution is to mark attrs untrusted in >> mdc_unreachable(). > > That doesn't help the entry being renamed though, which is actua

Re: [Nfs-ganesha-devel] Attribute refresh on rename

2016-10-13 Thread Frank Filz
> I suspect the correct solution is to mark attrs untrusted in > mdc_unreachable(). That doesn't help the entry being renamed though, which is actually the biggest concern. Frank > On Wed, Oct 12, 2016 at 6:29 PM, Frank Filz > wrote: > > Dan, > > > > In cache_inode_rename, we did a lookup of b

Re: [Nfs-ganesha-devel] Attribute refresh on rename

2016-10-13 Thread Daniel Gryniewicz
I suspect the correct solution is to mark attrs untrusted in mdc_unreachable(). Daniel On Wed, Oct 12, 2016 at 6:29 PM, Frank Filz wrote: > Dan, > > In cache_inode_rename, we did a lookup of both the old name and the new > name, and refreshed attributes on both objects. > > In mdcache, I'm not s