[Bug 1695] bytes_transfered = rtems_rfs_rtems_error

[bugzilla-daemon at rtems.org]

https://www.rtems.org/bugzilla/show_bug.cgi?id=1695

--- Comment #5 from Chris Johns <chrisj at rtems.org> 2010-08-31 18:06:23 CDT ---
(In reply to comment #4)
> 
> The question at hand is whether it makes sense to say bytes transferred is
> always either 0 or -1.  This implies there really is no data transfer ever. So
> the variable name bytes_transfered is a bite of a misnomer (and a misspelling,
> there should be two r's).

I am a little confused. Is the name (excluding the spelling) the issue or the
fact -1 is being set ? The setting of -1 is determined by the read call defined
in the standards. The call to here is wrapped by the read call in libcsupport
and is itself a wrapper for the RFS implementation to RTEMS.

Yes it is a spelling mistake and I am happy to fix that. I could have returned
-1 rather than set bytes_transferred but I would have had to cut and paste the
clean up code that closes the inode handle and unlocks the file system.

The call to rtems_rfs_rtems_error lets a trace message appear when debugging is
turned on.

-- 
Configure bugmail: https://www.rtems.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.