Miklos Szeredi: > file, so most applications should handle this behavior fine. The truth > is a bit more complicated and the effect of the copy-up is more like > this: > > cp /foo/bar /tmp/ttt > mount --bind /tmp/ttt /foo/bar Good example. 'mount' instead of simple 'cp' means struct stat.st_dev differs. And it will make some applications confused such as find -x, du -x, df, chmod/own -R, rm -r, or etc. > The credentials of the current task are not modified but replaced by > new, temporary credentials. This will only have an affect on a single > thread. I see. I think I can understand about multi threads. Other threads will not be affected. I will test about a signal handler someday. J. R. Okajima -- 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
