diff options
author | Miklos Szeredi <mszeredi@redhat.com> | 2016-05-27 02:55:26 -0400 |
---|---|---|
committer | Miklos Szeredi <mszeredi@redhat.com> | 2016-05-27 02:55:26 -0400 |
commit | 942fd803e6dfc64d32f2ae4f160b2986bc5897b8 (patch) | |
tree | 8b6f8b0d9d014a3447750fa4648ac7a0bb323148 | |
parent | 3fe6e52f062643676eb4518d68cee3bc1272091b (diff) |
ovl: update documentation
Two "fixme" items are actually fixed now.
Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
-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 28091457b71a..d6259c786316 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 | |||
194 | "break" the link. Changes will not be propagated to other names | 194 | "break" the link. Changes will not be propagated to other names |
195 | referring to the same inode. | 195 | referring to the same inode. |
196 | 196 | ||
197 | Symlinks in /proc/PID/ and /proc/PID/fd which point to a non-directory | ||
198 | object in overlayfs will not contain valid absolute paths, only | ||
199 | relative paths leading up to the filesystem's root. This will be | ||
200 | fixed in the future. | ||
201 | |||
202 | Some operations are not atomic, for example a crash during copy_up or | ||
203 | rename will leave the filesystem in an inconsistent state. This will | ||
204 | be addressed in the future. | ||
205 | |||
206 | Changes to underlying filesystems | 197 | Changes to underlying filesystems |
207 | --------------------------------- | 198 | --------------------------------- |
208 | 199 | ||