From: Nick Piggin <npiggin@suse.de>
To: David Rientjes <rientjes@google.com>
Cc: "Andrew Morton" <akpm@linux-foundation.org>,
"Greg Kroah-Hartman" <gregkh@suse.de>,
"San Mehat" <san@android.com>,
"Arve Hjønnevåg" <arve@android.com>,
linux-kernel@vger.kernel.org
Subject: Re: [patch 5/7] oom: fix possible oom_dump_tasks NULL pointer
Date: Tue, 5 May 2009 12:11:32 +0200 [thread overview]
Message-ID: <20090505101132.GA28917@wotan.suse.de> (raw)
In-Reply-To: <alpine.DEB.2.00.0905041725330.11756@chino.kir.corp.google.com>
On Mon, May 04, 2009 at 05:27:02PM -0700, David Rientjes wrote:
> When /proc/sys/vm/oom_dump_tasks is enabled, it is possible to get a NULL
> pointer for tasks that have detached mm's since task_lock() is not held
> during the tasklist scan.
>
> Cc: Nick Piggin <npiggin@suse.de>
> Signed-off-by: David Rientjes <rientjes@google.com>
I hope I'm not the oom killer maintainer ;) But anyway,
Acked-by: Nick Piggin <npiggin@suse.de>
> ---
> mm/oom_kill.c | 24 +++++++++++++++---------
> 1 files changed, 15 insertions(+), 9 deletions(-)
>
> diff --git a/mm/oom_kill.c b/mm/oom_kill.c
> --- a/mm/oom_kill.c
> +++ b/mm/oom_kill.c
> @@ -284,22 +284,28 @@ static void dump_tasks(const struct mem_cgroup *mem)
> printk(KERN_INFO "[ pid ] uid tgid total_vm rss cpu oom_adj "
> "name\n");
> do_each_thread(g, p) {
> - /*
> - * total_vm and rss sizes do not exist for tasks with a
> - * detached mm so there's no need to report them.
> - */
> - if (!p->mm)
> - continue;
> + struct mm_struct *mm;
> +
> if (mem && !task_in_mem_cgroup(p, mem))
> continue;
> if (!thread_group_leader(p))
> continue;
>
> task_lock(p);
> + mm = p->mm;
> + if (!mm) {
> + /*
> + * total_vm and rss sizes do not exist for tasks with no
> + * mm so there's no need to report them; they can't be
> + * oom killed anyway.
> + */
> + task_unlock(p);
> + continue;
> + }
> printk(KERN_INFO "[%5d] %5d %5d %8lu %8lu %3d %3d %s\n",
> - p->pid, __task_cred(p)->uid, p->tgid,
> - p->mm->total_vm, get_mm_rss(p->mm), (int)task_cpu(p),
> - p->oomkilladj, p->comm);
> + p->pid, __task_cred(p)->uid, p->tgid, mm->total_vm,
> + get_mm_rss(mm), (int)task_cpu(p), p->oomkilladj,
> + p->comm);
> task_unlock(p);
> } while_each_thread(g, p);
> }
next prev parent reply other threads:[~2009-05-05 10:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 0:26 [patch 1/7] lowmemorykiller: Only iterate over process list when needed David Rientjes
2009-05-05 0:26 ` [patch 2/7] lowmemorykiller: Don't count free space unless it meets the specified limit by itself David Rientjes
2009-05-05 0:26 ` [patch 3/7] oom: cleanup android low memory killer David Rientjes
2009-05-05 0:26 ` [patch 4/7] oom: fix possible android low memory killer NULL pointer David Rientjes
2009-05-05 0:27 ` [patch 5/7] oom: fix possible oom_dump_tasks " David Rientjes
2009-05-05 10:11 ` Nick Piggin [this message]
2009-05-05 0:27 ` [patch 6/7] oom: move oom_adj value from task_struct to mm_struct David Rientjes
2009-05-05 10:18 ` Nick Piggin
2009-05-05 18:29 ` David Rientjes
2009-05-05 0:27 ` [patch 7/7] oom: prevent possible OOM_DISABLE livelock David Rientjes
2009-05-05 10:22 ` Nick Piggin
2009-05-05 18:33 ` David Rientjes
2009-05-05 10:23 ` [patch 1/7] lowmemorykiller: Only iterate over process list when needed Nick Piggin
2009-05-05 16:31 ` Greg KH
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=20090505101132.GA28917@wotan.suse.de \
--to=npiggin@suse.de \
--cc=akpm@linux-foundation.org \
--cc=arve@android.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rientjes@google.com \
--cc=san@android.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
all inboxes | Powered by JetHome®