Re: [PATCH V2] hfsplus: fixes worst-case unicode to char conversion of file names and attributes

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

 



On Tue, 2014-04-08 at 20:53 +0100, Hin-Tak Leung wrote:

[snip]

> 
> If you insist on doing Chinese all the way, 127/3 = 42 is really a bit low for a
> descriptive string of any usage, but does anybody use non-english extended
> attributes on any OSes?
> 

If you think that nobody use non-english extended attributes then it
doesn't make sense to make any fixes in xattr subsystem of HFS+. And
partial code changing in hfsplus_listxattr() is completely useless.
Because getxattr() and setxattr() series of methods will be the primary
source of error in the case of worst-case unicode to char conversion.

Otherwise, you can use any splitting of fixes between patches. In my
last e-mail I suggested to use kmem cache approach for xattr names
instead of kmalloc only.

Thanks,
Vyacheslav Dubeyko.


--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




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