From: Kirill Korotaev <dev@sw.ru>
To: Linus Torvalds <torvalds@osdl.org>,
simon.derr@bull.net, pj@sgi.com, linux-kernel@vger.kernel.org,
"Denis V. Lunev" <den@sw.ru>, Stanislav Protassov <st@sw.ru>
Subject: cpusets: BUG: cpuset_excl_nodes_overlap() may sleep under tasklist_lock
Date: Wed, 28 Dec 2005 15:48:22 +0300 [thread overview]
Message-ID: <43B28996.7060006@sw.ru> (raw)
FYI, there is an obvious bug in cpusets in 2.6.15-rcX:
cpuset_excl_nodes_overlap() may sleep (as it takes semaphore), but is
called from atomic context - select_bad_process() under tasklist_lock.
BUG. Found by Denis Lunev.
the same actually applies to cpuset_zone_allowed() which is called e.g.
from __alloc_pages()->get_page_from_freelist() and doesn't check for
GPF_NOATOMIC anyhow...
Kirill
next reply other threads:[~2005-12-28 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-28 12:48 Kirill Korotaev [this message]
2006-01-03 22:31 ` cpusets: BUG: cpuset_excl_nodes_overlap() may sleep under tasklist_lock Paul Jackson
2006-01-04 9:26 ` Kirill Korotaev
-- strict thread matches above, loose matches on Subject: below --
2006-01-09 22:42 Darrick J. Wong
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=43B28996.7060006@sw.ru \
--to=dev@sw.ru \
--cc=den@sw.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--cc=simon.derr@bull.net \
--cc=st@sw.ru \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox