Messages in this thread | | | Date | Sat, 31 Dec 2005 16:23:59 +0300 | From | Kirill Korotaev <> | Subject | Re: oom-killer causes lockups in cpuset_excl_nodes_overlap() |
| |
yes, we found the same problem while looking at the code. and this is not the only cpuset function which might sleep, but is called from atomic context... :(
> The oom-killer causes lockups because it calls > cpuset_excl_nodes_overlap() with tasklist_lock read-locked. > cpuset_excl_nodes_overlap() gets cpuset_sem (or callback_sem in > later linux versions) semaphore, which might_sleep even if the > semaphore could be down without sleeping. If processes call > exit() or fork() when the oom-killer sleeps in the down(), they > lockup because they call write_lock_irq(&tasklist_lock). > > The lockup occurred on linux-2.6.14. The problem also seems to exist > in linux-2.6.15-rc5-mm3 and linux-2.6.15-rc7. > > Regards, > - 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/
| |