You are right [1]. I thought that this would be allowed. This bug can be closed.
I needed to modify the underlying filesystems because of the following: rename() on the overlayfs gave me EOVERFLOW. Maybe you got an idea about what may cause EOVERFLOW as result to rename syscall?
[1]:
Last paragraph of Documentation/filesystems/overlayfs.txt:
Changes to the underlying filesystems while part of a mounted overlay
filesystem are not allowed. If the underlying filesystem is changed,
the behavior of the overlay is undefined, though it will not result in
a crash or deadlock.
You are right [1]. I thought that this would be allowed. This bug can be closed.
I needed to modify the underlying filesystems because of the following: rename() on the overlayfs gave me EOVERFLOW. Maybe you got an idea about what may cause EOVERFLOW as result to rename syscall?
[1]: filesystems/ overlayfs. txt:
Last paragraph of Documentation/
Changes to the underlying filesystems while part of a mounted overlay
filesystem are not allowed. If the underlying filesystem is changed,
the behavior of the overlay is undefined, though it will not result in
a crash or deadlock.