Re: [PATCH v2 2/2] fuse: Increase FUSE_NAME_MAX to PATH_MAX

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

 




On 12/14/24 03:07, Jingbo Xu wrote:
> 
> 
> On 12/14/24 12:01 AM, Bernd Schubert wrote:
>> Our file system has a translation capability for S3-to-posix.
>> The current value of 1kiB is enough to cover S3 keys, but
>> does not allow encoding of %xx escape characters.
>> The limit is increased to (PATH_MAX - 1), as we need
>> 3 x 1024 and that is close to PATH_MAX (4kB) already.
>> -1 is used as the terminating null is not included in the
>> length calculation.
>>
>> Testing large file names was hard with libfuse/example file systems,
>> so I created a new memfs that does not have a 255 file name length
>> limitation.
>> https://github.com/libfuse/libfuse/pull/1077
>>
>> Signed-off-by: Bernd Schubert <bschubert@xxxxxxx>
> 
> LGTM.
> 
> Reviewed-by: Jingbo Xu <jefflexu@xxxxxxxxxxxxxxxxx>
> 

Thank you! I didn't add your reviewed-by yet, as I added some changes to
address Shachars concern about operations that need two hold two
file names, but fuse server might use FUSE_MIN_READ_BUFFER.


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