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, 07 May 2007 20:17:15 +0200
From:	Andreas Schwab <schwab@...e.de>
To:	Roland Kuhn <rkuhn@....physik.tu-muenchen.de>
Cc:	Andrey Borzenkov <arvidjaar@...l.ru>, hirofumi@...l.parknet.co.jp,
	linux-kernel@...r.kernel.org
Subject: Re: Long file names in VFAT broken with iocharset=utf8

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.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@...e.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
-
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/