> But since you've been arguing that the project id should get preserved > across renames, they can evade quota usage by doing: > > touch /product/mail/huge_file > mv /product/mail/huge_file /product/maps I don't really understand why these commands can evade project quota since: 1) A newly created file will inherit project ID from its parent inode. 2) Project ID will be preserved across renames 3) Project quota won't be transfered unless its project ID is changed. 4) Only root user has the right to change project ID. The rule 2) and 3) are just the same sematics with UID/GID quotas. So, becasue of rule 1), after 'touch /product/mail/huge_file', the project ID of 'huge_file' is 'mail', and its usage is accouted as project 'mail'. Even we do 'mv /product/mail/huge_file /product/maps', because of rule 2), there is no project ID updating and no quota transfer. Since so, the project quota of file 'huge_file' is always accounted as 'mail', from the first beginning to the end. And that is why I think project quota of 'mail' can't be evaded in this way. According to the discription of Jan Kara, I think the current implementation of project quota support for ext4 is just a subset of XFS project quota, i.e. project quota without XFS_DIFLAG_PROJINHERIT flag. I would like to add such kind of flag for sure. Regards, Li Xi -- 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
