On 06/16, Srikar Dronamraju wrote: > > In which case, shouldnt traversing all the tasks of all siblings of > parent of mm->owner should provide us all the the tasks that have linked > to mm. Right? I don't think so. Even if the initial mm->ovner never exits (iow, mm->owner is never changed), the "deep" CLONE_VM child can be reparented to init if its parent exits. > Agree that we can bother about this a little later. Agreed. Oh. We should move ->mm from task_struct to signal_struct, but we need to change the code like get_task_mm(). And then instead of mm->owner we can have mm->processes list. Perhaps. This can be used by zap_threads() too. Oleg. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>