diff options
| author | Miklos Szeredi <mszeredi@redhat.com> | 2016-09-01 12:12:00 +0300 |
|---|---|---|
| committer | Miklos Szeredi <mszeredi@redhat.com> | 2016-09-01 12:12:00 +0300 |
| commit | 026e5e0cc12474495515275d9c176ef823238c70 (patch) | |
| tree | 8bddbbbc20fb69d948b54d2edb90e191a2291d30 | |
| parent | 7cb35119d067191ce9ebc380a599db0b03cbd9d9 (diff) | |
| download | linux-026e5e0cc12474495515275d9c176ef823238c70.tar.xz | |
ovl: update doc
Some of the documented quirks no longer apply.
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
| -rw-r--r-- | Documentation/filesystems/overlayfs.txt | 8 |
1 files changed, 3 insertions, 5 deletions
diff --git a/Documentation/filesystems/overlayfs.txt b/Documentation/filesystems/overlayfs.txt index d6259c786316..bcbf9710e4af 100644 --- a/Documentation/filesystems/overlayfs.txt +++ b/Documentation/filesystems/overlayfs.txt @@ -183,12 +183,10 @@ The copy_up operation essentially creates a new, identical file and moves it over to the old name. The new file may be on a different filesystem, so both st_dev and st_ino of the file may change. -Any open files referring to this inode will access the old data and -metadata. Similarly any file locks obtained before copy_up will not -apply to the copied up file. +Any open files referring to this inode will access the old data. -On a file opened with O_RDONLY fchmod(2), fchown(2), futimesat(2) and -fsetxattr(2) will fail with EROFS. +Any file locks (and leases) obtained before copy_up will not apply +to the copied up file. If a file with multiple hard links is copied up, then this will "break" the link. Changes will not be propagated to other names |