Hi, On 6/23/22 13:25, jie wang via samba wrote:> I'm curious about how samba guarantee close-to-open consistency, does > it need to get all newest attributes from backend storage, when samba call > vfs_{vfs module}_openat, rather than use the cache in vfs module.oh, that's simple, there is no cache. :) At least not in upstream Samba. The question kind of implies you're using a non upstream VFS module that implements caching? -slow -- Ralph Boehme, Samba Team https://samba.org/ SerNet Samba Team Lead https://sernet.de/en/team-samba -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20220623/c95d9b84/OpenPGP_signature.sig>
Yes, we implement a vfs module which has cache. And we want to get attributes from cache when samba calls openat. On Thu, Jun 23, 2022 at 9:37 PM Ralph Boehme <slow at samba.org> wrote:> Hi, > > On 6/23/22 13:25, jie wang via samba wrote: > > I'm curious about how samba guarantee close-to-open consistency, > does > > it need to get all newest attributes from backend storage, when samba > call > > vfs_{vfs module}_openat, rather than use the cache in vfs module. > > oh, that's simple, there is no cache. :) At least not in upstream Samba. > The question kind of implies you're using a non upstream VFS module that > implements caching? > > -slow > > -- > Ralph Boehme, Samba Team https://samba.org/ > SerNet Samba Team Lead https://sernet.de/en/team-samba >