aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorrelan <relan@users.noreply.github.com>2015-11-07 11:10:29 +0300
committerrelan <relan@users.noreply.github.com>2015-11-07 11:25:48 +0300
commitc4d1bc1e671c875d7fa6a1db105fe8fb6a0aeafe (patch)
treefc3cd1ce033d8f58e2ffbde7e54c5a3d09d1dadf
parent01be539e4d2855dca34e1734501115e880eb905e (diff)
downloadandroid_external_exfat-c4d1bc1e671c875d7fa6a1db105fe8fb6a0aeafe.tar.gz
android_external_exfat-c4d1bc1e671c875d7fa6a1db105fe8fb6a0aeafe.tar.bz2
android_external_exfat-c4d1bc1e671c875d7fa6a1db105fe8fb6a0aeafe.zip
Flush clusters bitmap on each file close.
Put FS into a clean state when all files are closed. Flush to the non-volatile storage is not enforced though, so there can (and most probably will) be some dirty data in various OS- and hardware-controlled caches.
-rw-r--r--libexfat/node.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/libexfat/node.c b/libexfat/node.c
index f3d10e0..d05f20d 100644
--- a/libexfat/node.c
+++ b/libexfat/node.c
@@ -664,7 +664,7 @@ int exfat_flush_node(struct exfat* ef, struct exfat_node* node)
}
node->flags &= ~EXFAT_ATTRIB_DIRTY;
- return 0;
+ return exfat_flush(ef);
}
static bool erase_entry(struct exfat* ef, struct exfat_node* node)