Union mounts and file locks (was Re: [PATCH 14/39] union-mount: Union mounts documentation)
Quoted 9 lines · J. R. Okajima
Also here is my concern about UnionMount. All these issues have been reported before.
- for users, the inode number may change silently. eg. copy-up.
- link(2) may break by copy-up.
- read(2) may get an obsoleted filedata (fstat(2) too).
-fcntl(F_SETLK)may be broken by copy-up.
- unnecessary copy-up may happen, for examplemmap(MAP_PRIVATE)afteropen(O_RDWR).
You forgot fchmod()/fchown()/fsetxattr()/utimensat() failing on O_RDONLY file descriptors. :)
These are all known limitations of union mounts, with the exception of fcntl(F_SETLK). Several people asked about this at the LSF workshop and I said I'd look into it.
The short version is that in-kernel file copyup will affect locks the same way as a concurrent rename() over the target. If an application opens a file read-only and gets a lock on it, and another application (or the same one) opens the file read-write and takes a lock on it, the first lock will be on the read-only file on the lower layer, and the second lock will be on the file copied up to the top layer. This isn't what you want, obviously.
Union mounts behaves this way with locks for the same reason as fchmod(), etc. on O_RDONLY file descriptors fails. In-kernel copyup only happens before a file descriptor is open. Once it is open, it is very difficult to switch the open file with the newly copied up file ("very difficult" meaning "Al Viro refuses to even discuss it"). fcntl() is called on an open file descriptor, so the decision to copyup or not has already been made, based on the mode given to open().
However, fcntl(F_SETLK) on a file opened read-write will behave exactly as expected. The question is how many applications call fcntl(F_SETLK) on a read-only file descriptor as the first lock operation on a file? Of those applications, how many could easily be rewritten to open that file descriptor with write permissions?
-VAL
Valerie Aurora:
Quoted 5 lines
Union mounts behaves this way with locks for the same reason as
fchmod(), etc. onO_RDONLYfile descriptors fails. In-kernel copyup only happens before a file descriptor is open. Once it is open, it is very difficult to switch the open file with the newly copied up file ("very difficult" meaning "Al Viro refuses to even discuss it").
Laugh, laugh, laugh.
But this is one of the major difference between "union in VFS" and "union as FS". By the union implemented as FS, the file object will be a virtual one in a virtual FS, and you can switch two real files on the layers in the virtual object.
Quoted 5 lines
However,
fcntl(F_SETLK)on a file opened read-write will behave exactly as expected. The question is how many applications callfcntl(F_SETLK)on a read-only file descriptor as the first lock operation on a file? Of those applications, how many could easily be rewritten to open that file descriptor with write permissions?
I don't know.
If users never use such AP or never meet the problem, then there will be no actual problem.
J. R. Okajima