OverlayFS limitation
Hello fsdevel,
I've been poking around overlayfs recently and it appears one of the major remaining barriers to general usage as a posix-ish filesystem is reader file handles accessing stale (lower) instances of copy_up'd files.
Can't we do something to invalidate the struct address_space * of the lower instance's inode referenced by the open files when the copy_up occurs? I don't see any formal infrastructure supporting this currently, other than maybe the scaffolding for truncate, but it seems tractable, if perhaps a bit invasive, to make happen.
Anyone already been down this rabbit hole?
Cheers,
Vito Caputo