Hello, I have a question reguarding mmap(2)ed files which are modified.
After reading the manual page of msync(2), I have the impression that if invoked with the MS_SYNC flag, it should be safe enough not to need a further fdatasync(2)/fsync_range(2) call afterwards? And how about the metadata? Would sync(2) be the only true way to ensure it's synchronized (considering fsync(2) seems fd-specific)? Also, I am auditing an application which seems to modify mmaped files but which does not use msync(2) at all (and I can see that an older fsync(2) call was used, but is now commented out). Should this be considered a bug? Thanks, -- Matt