samba - Jun 2022 - How samba guarantee close-to-open consistency?

Hi, all,
     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.
If  vfs_{vfs module}_openat get all newest attributes from backend storage,
it will be too slow.

Thanks.

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>