From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Paul Jackson <pj@sgi.com>, stable@kernel.org
Cc: chrisw@osdl.org, akpm@osdl.org, Simon.Derr@bull.net, pj@sgi.com,
linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH 2.6.13-stable] cpuset semaphore double trip fix
Date: Fri, 9 Sep 2005 18:56:05 -0700 [thread overview]
Message-ID: <20050909185605.0f8e53e6.rdunlap@xenotime.net> (raw)
In-Reply-To: <20050910004403.29717.51121.sendpatchset@jackhammer.engr.sgi.com>
On Fri, 9 Sep 2005 17:44:03 -0700 (PDT) Paul Jackson wrote:
> Code reading uncovered a potential deadlock on the global cpuset
> semaphore, cpuset_sem.
>
> ==> This patch is only useful in the 2.6.13-stable series.
Paul,
stable patch candidates should be sent to stable@kernel.org
Chris/Greg,
maybe that should be listed in MAINTAINERS as well as in
Documentation/stable_kernel_rules.txt (it's here already).
> (It's harmless, and useless, in the pre 2.6.14 fork)
>
> The pre-2.6.14 fork has already diverged, with an additional patch
> that further aggrevated this problem, and a more thorough overhaul
> of the cpuset locking, to fix the problems.
>
> All code paths in kernel/cpuset.c (2.6.13 or earlier) that first
> grab cpuset_sem and then allocate memory _must_ call the routine
> 'refresh_mems()', after getting cpuset_sem, before any possible
> allocation.
>
> If this refresh_mems() call is not done, then there is a risk that one
> of the cpuset_zone_allowed() calls made from within the page allocator
> (__alloc_pages) will find that the mems_generation of the current task
> doesn't match that of its cpuset, causing it to try to grab cpuset_sem.
> Since it already held cpuset_sem, this deadlocks that task, and any
> subsequent task wanting cpuset_sem.
>
> ==> The code paths leading to the kmalloc in check_for_release(), from
> cpuset_exit, cpuset_rmdir and attach_task (for the detached cpuset),
> fail to invoke refresh_mems() as required.
>
> The fix is easy enough - add the requisite refresh_mems() call.
>
> Unless someone is rapidly creating, modifying and destroying cpusets,
> they are unlikely to have any chance of encountering this deadlock.
> And even then, it is apparently difficult to do so.
>
> In the case we got here from cpuset_exit(), we have already torn
> down the tasks connection to this cpuset and current->cpuset is NULL.
> Don't call refresh_mems() in that case - it oops the kernel.
>
> Signed-off-by: Paul Jackson <pj@sgi.com>
>
> Index: linux-2.6.13-mem_exclusive_oom/kernel/cpuset.c
> ===================================================================
> --- linux-2.6.13-mem_exclusive_oom.orig/kernel/cpuset.c
> +++ linux-2.6.13-mem_exclusive_oom/kernel/cpuset.c
> @@ -458,7 +458,10 @@ static void check_for_release(struct cpu
> if (notify_on_release(cs) && atomic_read(&cs->count) == 0 &&
> list_empty(&cs->children)) {
> char *buf;
> + static void refresh_mems(void);
>
> + if (current->cpuset)
> + refresh_mems();
> buf = kmalloc(PAGE_SIZE, GFP_KERNEL);
> if (!buf)
> return;
>
---
~Randy
next prev parent reply other threads:[~2005-09-10 1:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-10 0:44 Paul Jackson
2005-09-10 1:56 ` Randy.Dunlap [this message]
2005-09-10 2:31 ` Paul Jackson
2005-09-10 3:01 ` Chris Wright
2005-09-10 3:20 ` Paul Jackson
2005-09-10 3:28 ` Chris Wright
2005-09-10 3:40 ` 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=20050909185605.0f8e53e6.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=Simon.Derr@bull.net \
--cc=akpm@osdl.org \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
--cc=stable@kernel.org \
--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
all inboxes | Powered by JetHome®