On Mon, Feb 25, 2013 at 12:04:42PM +0800, Liu Bo wrote: > Before we forced to change a file's NOCOW and COMPRESS flag due to > the parent directory's, but this ends up a bad idea, because it > confuses end users a lot about file's NOCOW status, eg. if someone > change a file to NOCOW via 'chattr' and then rename it in the current > directory which is without NOCOW attribute, the file will lose the > NOCOW flag silently. > > This diables 'change flags in rename', so from now on we'll only > inherit flags from the parent directory on creation stage while in > other places we can use 'chattr' to set NOCOW or COMPRESS flags. > > Reported-by: Marios Titas <redneb8...@gmail.com> > Signed-off-by: Liu Bo <bo.li....@oracle.com>
Thank you! Reviewed-by: David Sterba <dste...@suse.cz> -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
