[Fontconfig-bugs] [Bug 103237] FcCacheOffsetsValid() couldn't detect broken cache file

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=103237

--- Comment #7 from Youngbok Shin <youngb.shin at samsung.com> ---
The memory corruption could be one of possible reason. If the memory corruption
is the main reason of this, I suppose that we could reproduce it easily or find
other serious issues. But, I couldn’t still find memory corruption issues about
this. 

I found a write() call in FcDirCacheWrite() is used without calling fsync().
I supposed fsync() is called for better performance. The open-write-close code
without fsync() or O_SYNC flag does not make any guarantee that data has been
committed to disk. It can cause corrupted cache file when the device is
shutdown by power outage. How about your opinion about open-write-close without
fsync()?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/fontconfig-bugs/attachments/20171114/3ea0022e/attachment.html>