From: Xiaotian Feng <xtfeng@gmail.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Hugh Dickins <hughd@google.com>, Ying Han <yinghan@google.com>,
Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Oleg Nesterov <oleg@redhat.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [PATCH] [BUGFIX] update mm->owner even if no next owner.
Date: Fri, 10 Jun 2011 13:21:46 +0800 [thread overview]
Message-ID: <BANLkTi=_-md7tes5GPcYh5Bpd=g_FVaagw@mail.gmail.com> (raw)
In-Reply-To: <20110610133021.2eaaf0da.kamezawa.hiroyu@jp.fujitsu.com>
[-- Attachment #1: Type: text/plain, Size: 1779 bytes --]
On Fri, Jun 10, 2011 at 12:30 PM, KAMEZAWA Hiroyuki <
kamezawa.hiroyu@jp.fujitsu.com> wrote:
>
> I think this can be a fix.
> maybe good to CC Oleg.
==
> From dff52fb35af0cf36486965d19ee79e04b59f1dc4 Mon Sep 17 00:00:00 2001
> From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> Date: Fri, 10 Jun 2011 13:15:14 +0900
> Subject: [PATCH] [BUGFIX] update mm->owner even if no next owner.
>
> A panic is reported.
>
> > Call Trace:
> > [<ffffffff81139792>] mem_cgroup_from_task+0x15/0x17
> > [<ffffffff8113a75a>] __mem_cgroup_try_charge+0x148/0x4b4
> > [<ffffffff810493f3>] ? need_resched+0x23/0x2d
> > [<ffffffff814cbf43>] ? preempt_schedule+0x46/0x4f
> > [<ffffffff8113afe8>] mem_cgroup_charge_common+0x9a/0xce
> > [<ffffffff8113b6d1>] mem_cgroup_newpage_charge+0x5d/0x5f
> > [<ffffffff81134024>] khugepaged+0x5da/0xfaf
> > [<ffffffff81078ea0>] ? __init_waitqueue_head+0x4b/0x4b
> > [<ffffffff81133a4a>] ? add_mm_counter.constprop.5+0x13/0x13
> > [<ffffffff81078625>] kthread+0xa8/0xb0
> > [<ffffffff814d13e8>] ? sub_preempt_count+0xa1/0xb4
> > [<ffffffff814d5664>] kernel_thread_helper+0x4/0x10
> > [<ffffffff814ce858>] ? retint_restore_args+0x13/0x13
> > [<ffffffff8107857d>] ? __init_kthread_worker+0x5a/0x5a
>
> The code is.
> > return container_of(task_subsys_state(p, mem_cgroup_subsys_id),
> > struct mem_cgroup, css);
>
>
> What happens here is accssing a freed task struct "p" from mm->owner.
> So, it's doubtful that mm->owner points to freed task struct.
>
>
But from the bug itself, it looks more likely kernel is hitting a freed
p->cgroups, right?
If p is already freed, the kernel will fault on
781cc62d: 8b 82 fc 08 00 00 mov 0x8fc(%edx),%eax
Then you will not get a value of 6b6b6b87, right?
[-- Attachment #2: Type: text/html, Size: 2607 bytes --]
next prev parent reply other threads:[~2011-06-10 5:22 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 ` 3.0rc2 oops in mem_cgroup_from_task Ying Han
2011-06-09 23:42 ` Ying Han
2011-06-10 0:13 ` KAMEZAWA Hiroyuki
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 [this message]
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='BANLkTi=_-md7tes5GPcYh5Bpd=g_FVaagw@mail.gmail.com' \
--to=xtfeng@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=hughd@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oleg@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).