This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE : RAMFS error code.


Jonathan Larmour wrote :

> Vincent Catros wrote:
> > Hello,
> >
> > Whith RAMFS a file is made of a limited number of blocks.
> > This can result in a full file before the file system is.
> >
> > Nothing wrong with that.
> >
> > But, when facing this situation, returned code is EINVAL (see
ramfs.c
> > function findbuffer_node).
> > I was waiting for ENOSPC.
> >
> > Am I wrong?
> 
> Looking at ramfs.c, it appears to return ENOSPC. Where is the EINVAL
you
> are referring to?

In "ramfs.c" there are 2 versions of "findbuffer_node" function.
One for "SIMPLE" allocation policy and one for "BLOCKS" allocation
policy.

The one that, I think, doesn't not return the good error code is the
second one.

Regards.

Vincent CATROS


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]