From: Oleg Nesterov <oleg@redhat.com>
To: Peter Chiang <pchiang@nvidia.com>
Cc: "ccross@android.com" <ccross@android.com>,
"lizefan@huawei.com" <lizefan@huawei.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"tj@kernel.org" <tj@kernel.org>, "pavel@ucw.cz" <pavel@ucw.cz>,
"ebiederm@xmission.com" <ebiederm@xmission.com>,
"guillaume@morinfr.org" <guillaume@morinfr.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm : Avoid candidate task is equal to current task
Date: Wed, 16 Apr 2014 15:57:42 +0200 [thread overview]
Message-ID: <20140416135741.GA9407@redhat.com> (raw)
In-Reply-To: <80341664FB79C2419999599F48F738410227327888@HKMAIL01.nvidia.com>
On 04/16, Peter Chiang wrote:
>
> mm_update_next_owner() call from exit_mm() , and exit_mm() change tsk->mm
> to NULL If p==c , It seems to be impossible that mm == c->mm (tsk->mm) .
> Because mm is non-NULL and c->mm is NULL .
Confused, please see below.
> Fix kernel panic when finding a new owner for the mm and the new owner is
> equal to current onwer
Did you actually observe the panic ?
> diff --git a/kernel/exit.c b/kernel/exit.c index 6ed6a1d..aa98422 100644
> --- a/kernel/exit.c
> +++ b/kernel/exit.c
> @@ -399,7 +399,7 @@ retry:
> * here often
> */
> do_each_thread(g, c) {
> - if (c->mm == mm)
> + if ((c != p) && (c->mm == mm))
> goto assign_new_owner;
> } while_each_thread(g, c);
p == current. This is always called with p->mm == NULL and mm != NULL.
So, if c->mm == mm then at least c->mm != NULL, and this means that
c == p is not possible?
And it seems that this is exactly what you meant above. So why do you
think we need this change?
Oleg.
next prev parent reply other threads:[~2014-04-16 13:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 3:02 [PATCH] mm : Avoid candidate task is equal to current task Peter Chiang
2014-04-16 12:31 ` Peter Chiang
2014-04-16 12:52 ` Peter Chiang
2014-04-16 13:57 ` Oleg Nesterov [this message]
2014-04-17 6:48 ` Peter Chiang
2014-04-18 16:23 ` Oleg Nesterov
2014-04-18 17:26 ` [PATCH 0/2] memcg: mm_update_next_owner() should skip kthreads Oleg Nesterov
2014-04-18 17:26 ` [PATCH 1/2] " Oleg Nesterov
2014-04-18 17:27 ` [PATCH 2/2] memcg: optimize the "Search everything else" loop in mm_update_next_owner() Oleg Nesterov
2014-04-18 18:24 ` [PATCH 0/2] memcg: mm_update_next_owner() should skip kthreads Michal Hocko
2014-04-18 18:44 ` Oleg Nesterov
2014-04-18 19:12 ` [PATCH 0/1] memcg: kill start_kernel()->mm_init_owner(init_mm) Oleg Nesterov
2014-04-18 19:13 ` [PATCH 1/1] " Oleg Nesterov
2014-04-22 13:34 ` Michal Hocko
2014-04-22 13:23 ` [PATCH 0/1] " Michal Hocko
2014-04-22 16:15 ` [PATCH 0/1] memcg: kill CONFIG_MM_OWNER Oleg Nesterov
2014-04-22 16:15 ` [PATCH 1/1] " Oleg Nesterov
2014-04-22 16:39 ` Johannes Weiner
2014-04-22 16:59 ` [PATCH 0/1] " Michal Hocko
2014-04-22 10:52 ` [PATCH 0/2] memcg: mm_update_next_owner() should skip kthreads Michal Hocko
2014-04-22 13:21 ` Michal Hocko
2014-04-22 21:35 ` Hugh Dickins
2014-04-23 7:04 ` Michal Hocko
2014-04-19 8:34 ` Pavel Machek
2014-04-19 18:14 ` Oleg Nesterov
2014-04-19 21:23 ` Hugh Dickins
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=20140416135741.GA9407@redhat.com \
--to=oleg@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ccross@android.com \
--cc=ebiederm@xmission.com \
--cc=guillaume@morinfr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--cc=pavel@ucw.cz \
--cc=pchiang@nvidia.com \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox