You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Depending on the filesystem in use, the RTEMS statvfs() call might not be implemented at the filesystem level. In particular if it is called on the IMFS filesystem type, it returns an error and sets errno to ENOSYS.
OSAL translates any error here to OS_ERROR, which is what gets returned to the application.
Ultimately this causes the filesystem unit test to fail when this filesystem type is in use.
Describe the solution you'd like
Preferable to return OS_ERR_NOT_IMPLEMENTED in this case. In particular, unit tests already check for this, and will skip the test cases for this API, avoiding failure. This makes it a soft error.
Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered:
The statvfs() call depends on the underlying filesystem
supporting this. On RTEMS, the IMFS filesystem type
does not, and it returns the ENOSYS errno. This is better
translated to OS_ERR_NOT_IMPLEMENTED rather than OS_ERROR.
Is your feature request related to a problem? Please describe.
Depending on the filesystem in use, the RTEMS
statvfs()
call might not be implemented at the filesystem level. In particular if it is called on the IMFS filesystem type, it returns an error and sets errno toENOSYS
.OSAL translates any error here to
OS_ERROR
, which is what gets returned to the application.Ultimately this causes the filesystem unit test to fail when this filesystem type is in use.
Describe the solution you'd like
Preferable to return
OS_ERR_NOT_IMPLEMENTED
in this case. In particular, unit tests already check for this, and will skip the test cases for this API, avoiding failure. This makes it a soft error.Requester Info
Joseph Hickey, Vantage Systems, Inc.
The text was updated successfully, but these errors were encountered: