yamt commented on PR #2913:
URL: https://github.com/apache/nuttx/pull/2913#issuecomment-2774250147
> > @xiaoxiang781216 can you explain
> >
> > * why O_TRUNC should be immediately committed
>
> If the storage is near exhausted, the next write will fail without commit.
is it a problem? how?
> > * why you don't need to check errors from lfs_file_sync
>
> since it isn't a fatal error
why?
if it isn't fatal, what's the point of the lfs_file_sync call?
> > * why this needs to be fixed here (not in littlefs itself or in your
user application)
>
> it's a general problem, should be fixed inside littlefs or nuttx wrapper.
sorry, i don't understand.
if an application opens a file with O_TRUNC and assumes the truncation is in
the stable storage,
it sounds like a problem in the application to me.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
