On Mon, 11 May 2009 13:40:11 -0700, Joel Becker wrote: > > Here's v4 of reflink(). If you have the privileges, you get the > full snapshot. If you don't, you must have read access, and then you > get the entire snapshot (data and extended attributes) except that the > security context is reinitialized. That's it. It fits with most of the > other ops, and it's a clean degradation. Let me see if I understand this correctly. File "/tmp/foo" belongs to Joel, file "/tmp/bar" belongs to Joern. Everyone has read access to those files. Now if you reflink them to your home directory, both files belong to you. If I reflink them to my home directory, both files belong to me. And if root reflinks them to /root, one file belongs to Joel, the other to Joern. Is that correct? Because if it is, I would call that behaviour rather confusing. A system call that behaves differently depending on who calls it - or on whether the binary is installed suid root - is something I would like to avoid. Jörn -- A surrounded army must be given a way out. -- Sun Tzu -- 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
