Sorry, just trivial typos: On Wed, Aug 15, 2012 at 05:48:14PM +0200, Miklos Szeredi wrote: > +Directories > +----------- > + > +Overlaying mainly involved directories. If a given name appears in both s/involved/involves/. > +Non-standard behavior > +--------------------- > + > +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. > + > +On a file is opened with O_RDONLY fchmod(2), fchown(2), futimesat(2) s/is // > +and fsetxattr(2) will fail with EROFS. > + > +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 vaid absolute paths, only s/vaid/valid/ --b. -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
