On Tue, May 05, 2009 at 02:32:06PM -0700, Joel Becker wrote:
> The same as what? If you reflink your own file, it preserves
> the security context of the original or it appears with the default
> security context of yourself? They are not the same. "Treat it like
> link(2)" argues for the former - which precludes changing ownership.
> That's what reflink is designed to do. "Treat it like cp" is a
> different behavior.
The reason why I don't like the default to be "preserve the inode
ownership" is because it's *not* just like link(2). If it were just
like link(2), the inode number would also be preserved. If the inode
number is changing, then it arguably is ***much*** more like a copy.
And a copy operation also has many useful properties.
- Ted
--
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
