On 4/30/07, Srivatsa Vaddagiri <vatsa@xxxxxxxxxx> wrote:
On Sun, Apr 29, 2007 at 02:37:21AM -0700, Paul Jackson wrote: > It builds and boots and mounts the cpuset file system ok. > But trying to write the 'mems' file hangs the system hard. Basically we are attempting a read_lock(&tasklist_lock) in container_task_count() after taking write_lock_irq(&tasklist_lock) in update_nodemask()!
Paul, is there any reason why we need to do a write_lock() on tasklist_lock if we're just trying to block fork, or is it just historical accident? Wouldn't it be fine to do a read_lock()? Paul _______________________________________________ Containers mailing list Containers@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/containers
