lkml.org 
[lkml]   [2007]   [Apr]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 0/9] Containers (V9): Generic Process Containers
    On 4/30/07, Srivatsa Vaddagiri <vatsa@in.ibm.com> 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
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2007-04-30 19:13    [W:0.021 / U:0.208 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site