[ECOS] RE : [ECOS] empty filenames in JFFS2

[Nick Garnett]

"Vincent Catros" <Vincent.Catros@elios-informatique.fr> writes:

> Hello,
> 
> > -----Message d'origine-----
> > De : ecos-discuss-owner@ecos.sourceware.org [mailto:ecos-discuss-
> > owner@ecos.sourceware.org] De la part de Øyvind Harboe
> > Envoyé : lundi 8 mars 2004 17:35
> > À : Thomas Koeller
> > Cc : ecos-discuss@sources.redhat.com
> > Objet : Re: [ECOS] empty filenames in JFFS2
> > 
> > man, 08.03.2004 kl. 11.57 skrev Thomas Koeller:
> > > This happens because JFFS2 happily creates files with empty names if
> > > asked to do so, I've noticed this before.
> > 
> > Some questions come to mind:
> > 
> > - Is this the intended behaviour?
> > - If empty filenames are illegal, whos job is it to produce an error
> > message? I.e. should the fix go into JFFS2 or eCos higher layers?
> 
> I think empty file name shouldn't be allowed because it would become
> impossible to distinguish for instance "/" (root directory) and "/"
> (empty filename under root directory).
> 
> As this is a general behaviour it should be fixed into "fileio" package.

Most of the responsibility of handling filenames lies with the
individual filesystems. This problem has probably arisen because in
Linux the generic filesystem infrastructure will reject invalid
filenames before they reach an individual filesystem implementation.
In eCos we do not have that infrastructure. The problem is probably
somewhere in the JFFS2 eCos glue code.

-- 
Nick Garnett                    eCos Kernel Architect
http://www.ecoscentric.com      The eCos and RedBoot experts


--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss