diff options
| author | Matthias Goergens <matthias.goergens@gmail.com> | 2026-09-26 12:29:14 +0800 |
|---|---|---|
| committer | Jan Kara <jack@suse.cz> | 2026-10-02 12:54:49 +0200 |
| commit | 1885d252b3a944997701db0a4df89761741ed43f (patch) | |
| tree | 9d7addb5c7a9ffa361a90140ee86a89729cbf7ed /tools/perf/scripts/python/bin | |
| parent | b8253bcf92d6365b20eea6465f5a93c9fc4aa029 (diff) | |
| download | linux-1885d252b3a944997701db0a4df89761741ed43f.tar.gz linux-1885d252b3a944997701db0a4df89761741ed43f.zip | |
isofs: report the Joliet name length in statfs
isofs_statfs() reports NAME_MAX as the longest name, but a Joliet name
can now be up to JOLIET_NAME_MAX bytes long. glibc answers
pathconf(_PC_NAME_MAX) from f_namelen, so a program sizing a buffer from
it should get room for every name readdir returns. vfat has reported
255 times NLS_MAX_CHARSET_SIZE, 1530, since commit f68e542f3478 ("fat:
Fix statfs->f_namelen"), which followed a report of readdir_r()
overflowing a buffer sized that way, and exfat reports the same.
Windows reports a maximum component length of 110 for CDFS.
Report JOLIET_NAME_MAX on Joliet mounts. Rock Ridge and plain ISO 9660
mounts keep NAME_MAX.
Signed-off-by: Matthias Goergens <matthias.goergens@gmail.com>
Link: https://patch.msgid.link/20260926042916.3277409-3-matthias.goergens@gmail.com
Signed-off-by: Jan Kara <jack@suse.cz>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions