On 05/20, Michal Hocko wrote: > > So I assume the leader simply waits for its threads to finish and it > stays in the sibling list. __unhash_process seems like it does the final > cleanup and unlinks the leader from the lists. Which means that > mm_update_next_owner never sees !group_leader. Is that correct Oleg? Yes, yes, the group leader can't go away until the whole thread-group dies. But can't we kill mm->owner somehow? I mean, turn it into something else, ideally into "struct mem_cgroup *" although I doubt this is possible. It would be nice to kill mm_update_next_owner()/etc, this looks really ugly. We only need it for mem_cgroup_from_task(), and it would be much more clean to have mem_cgroup_from_mm(struct mm_struct *mm), imho. Oleg. -- 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
