Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751673Ab0HSPvM (ORCPT ); Thu, 19 Aug 2010 11:51:12 -0400 Received: from e3.ny.us.ibm.com ([32.97.182.143]:34498 "EHLO e3.ny.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750935Ab0HSPvI (ORCPT ); Thu, 19 Aug 2010 11:51:08 -0400 Date: Thu, 19 Aug 2010 08:51:03 -0700 From: "Paul E. McKenney" To: David Howells Cc: torvalds@osdl.org, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, rientjes@google.com, kamezawa.hiroyu@jp.fujitsu.com, KOSAKI Motohiro Subject: Re: [PATCH] oom: __task_cred() need rcu_read_lock() Message-ID: <20100819155103.GB2425@linux.vnet.ibm.com> Reply-To: paulmck@linux.vnet.ibm.com References: <20100819152618.21246.68223.stgit@warthog.procyon.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20100819152618.21246.68223.stgit@warthog.procyon.org.uk> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2299 Lines: 62 On Thu, Aug 19, 2010 at 04:26:18PM +0100, David Howells wrote: > From: KOSAKI Motohiro > > dump_tasks() needs to hold the RCU read lock around its access of the target > task's UID. To this end it should use task_uid() as it only needs that one > thing from the creds. > > The fact that dump_tasks() holds tasklist_lock is insufficient to prevent the > target process replacing its credentials on another CPU. > > Then, this patch change to call rcu_read_lock() explicitly. > > > =================================================== > [ INFO: suspicious rcu_dereference_check() usage. ] > --------------------------------------------------- > mm/oom_kill.c:410 invoked rcu_dereference_check() without protection! > > other info that might help us debug this: > > rcu_scheduler_active = 1, debug_locks = 1 > 4 locks held by kworker/1:2/651: > #0: (events){+.+.+.}, at: [] > process_one_work+0x137/0x4a0 > #1: (moom_work){+.+...}, at: [] > process_one_work+0x137/0x4a0 > #2: (tasklist_lock){.+.+..}, at: [] > out_of_memory+0x164/0x3f0 > #3: (&(&p->alloc_lock)->rlock){+.+...}, at: [] > find_lock_task_mm+0x2e/0x70 > > Signed-off-by: KOSAKI Motohiro > Signed-off-by: David Howells Looks good to me! Acked-by: Paul E. McKenney > --- > > mm/oom_kill.c | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/mm/oom_kill.c b/mm/oom_kill.c > index 5014e50..7b03102 100644 > --- a/mm/oom_kill.c > +++ b/mm/oom_kill.c > @@ -372,7 +372,7 @@ static void dump_tasks(const struct mem_cgroup *mem) > } > > pr_info("[%5d] %5d %5d %8lu %8lu %3u %3d %5d %s\n", > - task->pid, __task_cred(task)->uid, task->tgid, > + task->pid, task_uid(task), task->tgid, > task->mm->total_vm, get_mm_rss(task->mm), > task_cpu(task), task->signal->oom_adj, > task->signal->oom_score_adj, task->comm); > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/