bl_iot_sdk/components/fs
Paul Capron c546054984 vfs: Fix counting in inode_avail_count
As seen in `inode_del` (and `inode_alloc`), a free (`NOT_INIT`) node can be found anywhere in `g_vfs_dev_nodes`; it’s a “sparse” list.
So when checking for free nodes, the iterating index variable (`e`) shall be used, not the counter (`count`). The code got that wrong.
For instance, if the first node is not available (type is not `VFS_TYPE_NOT_INIT`), then the function previously returned 0, no matter what, and was iterating the node list in vain.
2020-10-31 21:51:30 +08:00
..
romfs Initial Commit 2020-10-26 20:35:25 +08:00
vfs vfs: Fix counting in inode_avail_count 2020-10-31 21:51:30 +08:00