On Fri, May 20, 2016 at 05:45:12AM +0200, Adam Borowski wrote: > (Only btrfs currently implements dedupe_file_range.) > > Instead of checking the mode of the file descriptor, let's check whether > it could have been opened rw. This allows fixing failures when deduping > a live system: anyone trying to exec a file currently being deduped gets > ETXTBSY. > > Issuing this ioctl on a ro file was already allowed for root/cap. > fs/read_write.c | 2 +- I'm unsure whom to bother with this patch. I've sent it to -btrfs as it's relevant only to btrfs (at least currently), but technically the file changed belongs to vfs. Was CCing -fsdevel enough or should I retarget/resend the patch? Apologies for a newbish question. Meow! -- An imaginary friend squared is a real enemy. -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
