From: Kirill Korotaev <dev@sw.ru>
To: KUROSAWA Takahiro <kurosawa@valinux.co.jp>
Cc: linux-kernel@vger.kernel.org
Subject: Re: oom-killer causes lockups in cpuset_excl_nodes_overlap()
Date: Sat, 31 Dec 2005 16:23:59 +0300 [thread overview]
Message-ID: <43B6866F.9080701@sw.ru> (raw)
In-Reply-To: <20051228004026.72F3474005@sv1.valinux.co.jp>
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,
>
next prev parent reply other threads:[~2005-12-31 13:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-28 0:40 oom-killer causes lockups in cpuset_excl_nodes_overlap() KUROSAWA Takahiro
2005-12-31 13:23 ` Kirill Korotaev [this message]
2006-01-03 21:34 ` Paul Jackson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43B6866F.9080701@sw.ru \
--to=dev@sw.ru \
--cc=kurosawa@valinux.co.jp \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.