>>>> BTW, isn't this a similar to what should happen with the block io cgroup? >>>> What is the behavior with a fd writing to a file in the scenario you >>>> describe above? >>>> >>> >>> It forbids task moving in this case: >>> >>> /* >>> * We cannot support shared io contexts, as we have no mean to support >>> * two tasks with the same ioc in two different groups without major rework >>> * of the main cic data structures. For now we allow a task to change >>> * its cgroup only if it's the only owner of its ioc. >>> */ >>> static int blkcg_can_attach(struct cgroup *cgrp, struct cgroup_taskset *tset) >>> >> >> OK, I guess we should do something similar in the netprio, netcls >> cgroups and >> yes document it as you noted in your last comment. > > Here is my attempt to add such a check. I really don't know if this is the > correct way to do so. To test this I have written a test program, which > seems to test the right thing. Please have a look and let me know if > it is correct: http://www.monom.org/misc/scm_rights.c > > And here a dirty first version of the patch: > Adding new can_attach() is discouraged. It's considered bad, because if cgroup is mounted with multi subsystems binded, and if one of them can forbid task moving for some reason, this will add burden on users to use cgroup properly. -- To unsubscribe from this list: send the line "unsubscribe cgroups" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
