[NFS-Ganesha-Devel] Re: Invalidating Ganesha MDCACHE attr entry from spawned off thread triggered by my FSAL

Thank you for the quick response Daniel. A follow up question: I need the fsal_up_vector to make the invalidate UP call. My server receives the occasional "remote" change to some path (by remote I mean not coming through Ganesha's "front door"). Therefore, when I want to call fsal_up_vector.invalidate (or its async variant) I am not in a ganesha thread, and therefore I think I will not have a req_op_context pointer. I plan to workaround this by capturing the "const fsal_up_vector*" inside the create_export call and saving the pointer in my own data structure for later use. Is this a reasonable plan? Any gotchas?