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]

Date:	Mon, 7 May 2007 22:43:52 +0400
From:	Andrey Borzenkov <arvidjaar@...l.ru>
To:	Andreas Schwab <schwab@...e.de>
Cc:	Roland Kuhn <rkuhn@....physik.tu-muenchen.de>,
	hirofumi@...l.parknet.co.jp, linux-kernel@...r.kernel.org
Subject: Re: Long file names in VFAT broken with iocharset=utf8

On Monday 07 May 2007, Andreas Schwab wrote:
> Roland Kuhn <rkuhn@....physik.tu-muenchen.de> writes:
> > 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 PATH_MAX and there is NAME_MAX, and only the latter (which is
> 260 for vfat) matters here.
>

Do you imply that Linux is unable to represent full VFAT names (255 UCS2 
charaters) by design? Hmm ... testing ... looks like it,

touch $(perl -e 'print "ф" x 200;') -> Name too long.

So what do we do with long VFAT names? As initial post shows, they do exist.

Content of type "application/pgp-signature" skipped