From: Miklos Szeredi Date: Thu, 1 Sep 2016 09:12:00 +0000 (+0200) Subject: ovl: update doc X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=026e5e0cc12474495515275d9c176ef823238c70;p=GitHub%2FLineageOS%2Fandroid_kernel_motorola_exynos9610.git ovl: update doc Some of the documented quirks no longer apply. Signed-off-by: Miklos Szeredi --- 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