Hi! We did a small update to the schedule: > Christian Brauner will run the second session, discussing what idmapped > filesystem mounts are for and the current status of supporting more > filesystems. We have extended this session as we'd like to discuss and get some feedback from users about project quotas and project ids: Project quotas were originally mostly a collaborative feature and later got used by some container runtimes to implement limitation of used space on a filesystem shared by multiple containers. As a result current semantics of project quotas are somewhat surprising and handling of project ids is not consistent among filesystems. The main two contending points are: 1) Currently the inode owner can set project id of the inode to any arbitrary number if he is in init_user_ns. It cannot change project id at all in other user namespaces. 2) Should project IDs be mapped in user namespaces or not? User namespace code does implement the mapping, VFS quota code maps project ids when using them. However e.g. XFS does not map project IDs in its calls setting them in the inode. Among other things this results in some funny errors if you set project ID to (unsigned)-1. In the session we'd like to get feedback how project quotas / ids get used / could be used so that we can define the common semantics and make the code consistently follow these rules. Honza -- Jan Kara <jack@xxxxxxxx> SUSE Labs, CR
