From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Ying Han <yinghan@google.com>
Cc: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Hugh Dickins <hughd@google.com>
Subject: Re: 3.0rc2 oops in mem_cgroup_from_task
Date: Fri, 10 Jun 2011 09:13:55 +0900 [thread overview]
Message-ID: <20110610091355.2ce38798.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <BANLkTikF7=qfXAmrNzyMSmWm7Neh6yMAB8EbBp7oLcfQmrbDjA@mail.gmail.com>
On Thu, 9 Jun 2011 16:42:09 -0700
Ying Han <yinghan@google.com> wrote:
> ++cc Hugh who might have seen similar crashes on his machine.
>
Thank you for forwarding. Hmm. It seems the panic happens at khugepaged's
page collapse_huge_page().
==
count_vm_event(THP_COLLAPSE_ALLOC);
if (unlikely(mem_cgroup_newpage_charge(new_page, mm, GFP_KERNEL))) {
==
It passes target mm to memcg and memcg gets a cgroup by
==
mem = mem_cgroup_from_task(rcu_dereference(mm->owner));
==
Panic here means....mm->owner's task_subsys_state contains bad pointer ?
I'll dig. Thanks.
-Kame
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-06-10 0:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110609212956.GA2319@redhat.com>
2011-06-09 22:47 ` Ying Han
2011-06-09 23:42 ` Ying Han
2011-06-10 0:13 ` KAMEZAWA Hiroyuki [this message]
2011-06-10 1:30 ` Hugh Dickins
2011-06-10 2:33 ` KAMEZAWA Hiroyuki
2011-06-10 3:19 ` KAMEZAWA Hiroyuki
2011-06-10 3:55 ` KAMEZAWA Hiroyuki
2011-06-10 4:30 ` [PATCH] [BUGFIX] update mm->owner even if no next owner KAMEZAWA Hiroyuki
2011-06-10 5:06 ` Daisuke Nishimura
2011-06-10 5:21 ` Xiaotian Feng
2011-06-10 5:22 ` KAMEZAWA Hiroyuki
2011-06-10 21:49 ` Hugh Dickins
2011-06-10 23:54 ` Johannes Weiner
2011-06-11 17:51 ` Johannes Weiner
2011-06-11 18:44 ` Andrea Arcangeli
2011-06-11 23:04 ` Hiroyuki Kamezawa
2011-06-13 1:41 ` Hugh Dickins
2011-06-13 1:54 ` KAMEZAWA Hiroyuki
2011-06-13 14:03 ` Hugh Dickins
2011-06-11 0:46 ` Hiroyuki Kamezawa
2011-06-11 16:04 ` Hugh Dickins
2011-06-11 16:39 ` Andrea Arcangeli
2011-06-11 18:04 ` Johannes Weiner
2011-06-11 8:19 ` 3.0rc2 oops in mem_cgroup_from_task Michal Hocko
2011-06-11 15:46 ` Hugh Dickins
2011-06-12 9:09 ` Michal Hocko
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=20110610091355.2ce38798.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=davej@redhat.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=yinghan@google.com \
/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