linux-kernel - Re: Long file names in VFAT broken with iocharset=utf8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <463F7F30.5010200@zytor.com>
Date:	Mon, 07 May 2007 12:34:08 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
CC:	Roland Kuhn <rkuhn@....physik.tu-muenchen.de>,
	Andrey Borzenkov <arvidjaar@...l.ru>,
	linux-kernel@...r.kernel.org
Subject: Re: Long file names in VFAT broken with iocharset=utf8

OGAWA Hirofumi wrote:
>>>
>> PATH_MAX specifically counts _bytes_ not characters, so UTF-8 does  
>> not matter. ISTR that PATH_MAX was 256 at some point, but I just  
>> quickly grepped /usr/include and found various mention of 4096, so  
>> where's the central repository for this configuration item? A hard- 
>> coded value of 256 somewhere inside the kernel smells like a bug.
> 
> There is a nasty issue here. FAT is limited by 255 unicode chars or so.
> So, we would need to count number of unicode chars of filename.
> 
> That's not implemented currently.

Note also there is PATH_MAX and NAME_MAX; the latter is 255 I believe.

POSIX allows NAME_MAX to vary on a filesystem by filesystem basis,
although that is not currently implemented in Linux.

	-hpa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/