On Mon, Jan 4, 2021 at 5:40 PM Vivek Goyal <vgoyal@xxxxxxxxxx> wrote: > > On Mon, Jan 04, 2021 at 05:22:07PM +0200, Amir Goldstein wrote: > > > > Since Jeff's patch is minimal, I think that it should be the fix applied > > > > first and proposed for stable (with adaptations for non-volatile overlay). > > > > > > Does stable fix has to be same as mainline fix. IOW, I think atleast in > > > mainline we should first fix it the right way and then think how to fix > > > it for stable. If fixes taken in mainline are not realistic for stable, > > > can we push a different small fix just for stable? > > > > We can do a lot of things. > > But if we are able to create a series with minimal (and most critical) fixes > > followed by other fixes, it would be easier for everyone involved. > > I am not sure this is really critical. writeback error reporting for > overlayfs are broken since the beginning for regular mounts. There is no > notion of these errors being reported to user space. If that did not > create a major issue, then why suddenly volatile mounts make it > a critical issue. > Volatile mounts didn't make this a critical issue. But this discussion made us notice a mildly serious issue. It is not surprising to me that users did not report this issue. Do you know what it takes for a user to notice that writeback had failed, but an application did fsync and error did not get reported? Filesystem durability guaranties are hard to prove especially with so many subsystem layers and with fsync that does return an error correctly. I once found a durability bug in fsync of xfs that existed for 12 years. That fact does not at all make it any less critical. > To me we should fix the issue properly which is easy to maintain > down the line and then worry about doing a stable fix if need be. > > > > > > > > > IOW, because we have to push a fix in stable, should not determine > > > what should be problem solution for mainline, IMHO. > > > > > > > I find in this case there is a correlation between the simplest fix and the > > most relevant fix for stable. > > > > > The porblem I have with Jeff's fix is that its only works for volatile > > > mounts. While I prefer a solution where syncfs() is fixed both for > > > volatile as well as non-volatile mount and then there is less confusion. > > > > > > > I proposed a variation on Jeff's patch that covers both cases. > > Sargun is going to work on it. > > What's the problem with my patches which fixes syncfs() error reporting > for overlayfs both for volatile and non-volatile mount? > - mount 1000 overlays - 1 writeback error recorded in upper sb - syncfs (new fd) inside each of the 1000 containers With your patch 3/3 only one syncfs will report an error for both volatile and non-volatile cases. Right? What I would rather see is: - Non-volatile: first syncfs in every container gets an error (nice to have) - Volatile: every syncfs and every fsync in every container gets an error (important IMO) This is why I prefer to sample upper sb error on mount and propagate new errors to overlayfs sb (Jeff's patch). I am very much in favor of your patch 1/3 and I am not against the concept of patches 2-3/3. Just think that ovl_errseq_check_advance() is not the implementation that gives the most desirable result. If people do accept my point of view that proxying the stacked error check is preferred over "passthrough" to upper sb error check, then as a by-product, the new ->check_error() method is not going to make much of a difference for overlayfs. Maybe it can be used to fine tune some corner cases. I am not sure. If we do agree on the propagate error concept then IMO all other use cases for not consuming the unseen error from upper fs are nice-to-have. Before we continue to debate on the implementation, let's first try to agree on the desired behavior, what is a must vs. what is nice to have. Without consensus on this, it will be quite hard to converge. Another thing, to help everyone, I think it is best that any patch on ovl_syncfs "solutions" will include detailed description of the use cases it solves and the use cases that it leaves unsolved. Thanks, Amir.
