TARUISI Hiroaki wrote:
Hi, I don't know how a hard link becomes to a soft link, hard link across subvolumes should not allowed in btrfs. Hard link contains target inode number but not target tree. So, if we can create such hard link normally, it points to a file which has same inode number in same subvolume. As for this problem, Christian Parpart posted a patch, and I rebased it.
Can you post a link? I'd like to test it, and it should probably go into -stable (since it fixes an oops that can be triggered without privileges).
Thanks, Andy -- 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
