Re: Getting Unexpected Lookup entries calls after Readdirplus

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Gentle reminder!!

-Prince.

On Thu, Jun 5, 2025 at 2:53 PM Prince Kumar <princer@xxxxxxxxxx> wrote:
>
> Hello Team,
>
> I'm implementing Readdirplus support in GCSFuse
> (https://github.com/googlecloudplatform/gcsfuse) and have observed
> behavior that seems to contradict my understanding of its purpose.
>
> When Readdirplus returns ChildInodeEntry, I expect the kernel to use
> this information and avoid subsequent lookup calls for those entries.
> However, I'm seeing lookup calls persist for these entries unless an
> entry_timeout is explicitly set.
>
> One similar open issue on the libfuse github repo:
> https://github.com/libfuse/libfuse/issues/235, which is closed but
> seems un-resolved.
>
> 1. Could you confirm if this is the expected behavior, or a kernel side issue?
> 2. Also, is there a way other than setting entry_timeout, to suppress
> these lookup entries calls after the Readdirplus call?
>
> Regards,
> Prince Kumar.





[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [NTFS 3]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [NTFS 3]     [Samba]     [Device Mapper]     [CEPH Development]

  Powered by Linux