Re: [PATCH] ovl: make fsync after metadata copy-up opt-in mount option
Christoph Hellwig <[email protected]>
| Newsgroups | org.kernel.vger.linux-unionfs,org.kernel.vger.linux-fsdevel,org.kernel.vger.stable |
|---|---|
| Message-ID | <[email protected]> |
On Tue, Mar 24, 2026 at 03:57:50PM +0100, Amir Goldstein wrote: > From: Fei Lv <[email protected]> > > Commit 7d6899fb69d25 ("ovl: fsync after metadata copy-up") was done to > fix durability of overlayfs copy up on an upper filesystem which does > not enforce ordering on storing of metadata changes (e.g. ubifs). I'm trying to understand this previous commit more than this one, but what 'enforce ordering on storing of metadata changes' does overlayfs encode right now? There is no real ordering requirements anywhere in the Linux file system API, so it does sounds like ovl is making some assumptions by default? Are those documented somewhere?