You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mynewt.apache.org by GitBox <gi...@apache.org> on 2019/09/10 07:23:23 UTC

[GitHub] [mynewt-nffs] yashi opened a new issue #18: Invalid inode cache in nffs_write_append()

yashi opened a new issue #18: Invalid inode cache in nffs_write_append()
URL: https://github.com/apache/mynewt-nffs/issues/18
 
 
   ;; Even though README says we must report to Jira, I found that [Jira is deprecated](https://issues.apache.org/jira/browse/MYNEWT-894?focusedCommentId=16765822&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16765822).  So here I go.
   
   `nffs_write_append()` gets a pointer to `struct nffs_cache_inode` as the first argument.  Unfortunately, the function calls `nffs_block_entry_reserve()` as the first thing in the the function.  Because `nffs_block_entry_reserve()` might invalidate the given cache in low memory situation, subsequent accesses to the cache must be protected by `nffs_cache_inode_ensure()`.
   

----------------------------------------------------------------
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.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services