diff options
| author | Linus Torvalds <torvalds@linux-foundation.org> | 2016-05-27 16:44:39 -0700 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2016-05-27 16:44:39 -0700 |
| commit | 0121a32201dcc72933fb6019c41661e2f8a02fc5 (patch) | |
| tree | 3e4944d4c1c7f1213413ac99f779629d67373c85 /Documentation/filesystems | |
| parent | 559b6d90a0beb375c46dffe18133012bfa29f441 (diff) | |
| parent | 21765194cecf2e4514ad75244df459f188140a0f (diff) | |
| download | op-kernel-dev-0121a32201dcc72933fb6019c41661e2f8a02fc5.zip op-kernel-dev-0121a32201dcc72933fb6019c41661e2f8a02fc5.tar.gz | |
Merge branch 'overlayfs-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs
Pull overlayfs update from Miklos Szeredi:
"The meat of this is a change to use the mounter's credentials for
operations that require elevated privileges (such as whiteout
creation). This fixes behavior under user namespaces as well as being
a nice cleanup"
* 'overlayfs-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs:
ovl: Do d_type check only if work dir creation was successful
ovl: update documentation
ovl: override creds with the ones from the superblock mounter
Diffstat (limited to 'Documentation/filesystems')
| -rw-r--r-- | Documentation/filesystems/overlayfs.txt | 9 |
1 files changed, 0 insertions, 9 deletions
diff --git a/Documentation/filesystems/overlayfs.txt b/Documentation/filesystems/overlayfs.txt index 2809145..d6259c7 100644 --- a/Documentation/filesystems/overlayfs.txt +++ b/Documentation/filesystems/overlayfs.txt @@ -194,15 +194,6 @@ If a file with multiple hard links is copied up, then this will "break" the link. Changes will not be propagated to other names referring to the same inode. -Symlinks in /proc/PID/ and /proc/PID/fd which point to a non-directory -object in overlayfs will not contain valid absolute paths, only -relative paths leading up to the filesystem's root. This will be -fixed in the future. - -Some operations are not atomic, for example a crash during copy_up or -rename will leave the filesystem in an inconsistent state. This will -be addressed in the future. - Changes to underlying filesystems --------------------------------- |
