From: Andrew Morton <akpm@linux-foundation.org>
To: Hugh Dickins <hugh@veritas.com>
Cc: balbir@linux.vnet.ibm.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH 2.6.26-rc8-mm1] memrlimit: fix mmap_sem deadlock
Date: Thu, 3 Jul 2008 16:01:17 -0700 [thread overview]
Message-ID: <20080703160117.b3781463.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0807032143110.10641@blonde.site>
On Thu, 3 Jul 2008 21:50:31 +0100 (BST)
Hugh Dickins <hugh@veritas.com> wrote:
> "ps -f" hung after "killall make" of make -j20 kernel builds. It's
> generally considered bad manners to down_write something you already
> have down_read. exit_mm up_reads before calling mm_update_next_owner,
> so I guess exec_mmap can safely do so too. (And with that repositioning
> there's not much point in mm_need_new_owner allowing for NULL mm.)
>
thanks
> ---
> Fix to memrlimit-cgroup-mm-owner-callback-changes-to-add-task-info.patch
> quite independent of its recent sleeping-inside-spinlock fix; could even
> be applied to 2.6.26, though no deadlock there. Gosh, I see those patches
> have spawned "Reviewed-by" tags in my name: sorry, no, just "Bug-found-by".
I switched
memrlimit-add-memrlimit-controller-accounting-and-control-memrlimit-improve-fork-and-error-handling.patch
and
memrlimit-cgroup-mm-owner-callback-changes-to-add-task-info-memrlimit-fix-sleep-inside-sleeplock-in-mm_update_next_owner.patch
to Cc:you.
There doesn't seem to have been much discussion regarding your recent
objections to the memrlimit patches. But it caused me to put a big
black mark on them. Perhaps sending it all again would be helpful.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-07-03 23:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 20:50 Hugh Dickins
2008-07-03 23:01 ` Andrew Morton [this message]
2008-07-04 1:49 ` Balbir Singh
2008-07-04 2:01 ` Andrew Morton
2008-07-04 3:20 ` Balbir Singh
2008-07-04 4:27 ` Andrew Morton
2008-07-04 7:07 ` Balbir Singh
2008-07-04 1:49 ` Balbir Singh
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=20080703160117.b3781463.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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