Re: Interrupt on readdirplus?

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

 



> 
> 
>> If I'm understanding your post correctly, the issue you are seeing is
>> that if your go-fuse server returns 25 entries to an interrupted
>> READDIRPLUS request, the kernel's next READDIRPLUS request is at
>> offset 1 instead of at offset 25?
> 
> yes. If the offset is ignored (mustSeek = false in fs/bridge.go), it
> causes test failures, because of a short read on the readdir result
> there are too few entries.
> 
> If I don't ignore the offset, I have to implement a workaround on my
> side which is expensive and clumsy (which is what the `mustSeek`
> variable controls.)
> 

That is the part I still do not understand - what is the issue if you do
not ignore the offset? Is it maybe just the test suite that expects
offset 25?


Thanks,
Bernd




[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