Re: [PATCH v2] fuse: use newer inode info when writeback cache is enabled
From: Miklos Szeredi <miklos@szeredi.hu>
Date: 2021-06-22 08:00:00
On Sat, 30 Jan 2021 at 09:50, Fengnan Chang [off-list ref] wrote:
When writeback cache is enabled, the inode information in cached is considered new by default, and the inode information of lowerfs is stale. When a lower fs is mount in a different directory through different connection, for example PATHA and PATHB, since writeback cache is enabled by default, when the file is modified through PATHA, viewing the same file from the PATHB, PATHB will think that cached inode is newer than lowerfs, resulting in file size and time from under PATHA and PATHB is inconsistent. Add a judgment condition to check whether to use the info in the cache according to mtime.
This seems to break the fsx-linux stress test. I suspect a better direction would be looking at whether the inode has any files open for write (i_writecount > 0)... Thanks, Miklos