What triggers flush/fsync of dirty pages on last (file) close of inode?
I was hunting through the sys_close code and did not see a call
to fsync or filemap_write_and_wait there. Is it something done in libc
above the vfs?
Someone had reported a problem with a writepages call coming in on with
no open files (so presumably the file was closed, with dirty pages not
written).
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
