view rvinterf/include/ffslimits.h @ 964:a96cb97b66a2

ringtools/imy: fix duplicate definition of tdma_durations[] The bug was reported by Vadim Yanitskiy <fixeria@osmocom.org>, although the present fix is slightly different from the contributed patch: because main.c doesn't need this tdma_durations[] array at all, let's simply remove the reference to this array from main.c rather than turn it into an extern. I no longer remember my original thought flow that resulted (by mistake) in tdma_durations[] being multiply defined in main.c and durations.c. My intent might have been to define all globals in main.c and have the reference in durations.c be an extern - and I missed that extern - but without clear memory, I have no certainty. In any case, having this data array defined in the same module that fills it (durations.c) is sensible, so let's make it the new way.
author Mychaela Falconia <falcon@freecalypso.org>
date Thu, 31 Aug 2023 19:38:18 +0000
parents e7502631a0f9
children
line wrap: on
line source

/*
 * Limits on FFS filenames and pathnames
 *
 * The deepest pathname allowed is one of the form /1/2/3/4/5/6, where the
 * last component may be a file, a directory or a symlink; if this last
 * component is a directory, it has to be empty, because any child of
 * that directory would violate the depth limit.
 *
 * The proper FFS pathname form begins with a slash (all pathnames must
 * be absolute, no Unix processes in the fw means no current directories),
 * has exactly one slash in each separating place (no double slashes),
 * and no trailing slash except in the special case of the root directory,
 * whose full pathname is "/".
 *
 * Each component name is [1,20] characters long; combining this limit
 * with the maximum depth of 6 puts the maximum length of a properly-formed
 * full pathname at 126 characters.
 */

#define	MAX_FN_COMPONENT	20
#define	MAX_NAME_DEPTH		6
#define	MAX_FULL_PATHNAME	((MAX_FN_COMPONENT+1) * MAX_NAME_DEPTH)