Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751871AbaJPIQz (ORCPT ); Thu, 16 Oct 2014 04:16:55 -0400 Received: from relay.parallels.com ([195.214.232.42]:50743 "EHLO relay.parallels.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751178AbaJPIQu (ORCPT ); Thu, 16 Oct 2014 04:16:50 -0400 Message-ID: <1413447404.24793.67.camel@tkhai> Subject: Re: [PATCH RFC] sched: Revert delayed_put_task_struct() and fix use after free From: Kirill Tkhai To: Peter Zijlstra CC: Kirill Tkhai , Oleg Nesterov , , Ingo Molnar , "Vladimir Davydov" Date: Thu, 16 Oct 2014 12:16:44 +0400 In-Reply-To: <20141016075950.GC7369@worktop.fdxtended.com> References: <1413376300.24793.55.camel@tkhai> <20141015150641.GA2755@redhat.com> <20141015194044.GA4557@redhat.com> <543EEB1F.3040900@yandex.ru> <20141016075950.GC7369@worktop.fdxtended.com> Organization: Parallels Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.8.5-2+b3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Originating-IP: [10.30.26.172] Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org В Чт, 16/10/2014 в 09:59 +0200, Peter Zijlstra пишет: > On Thu, Oct 16, 2014 at 01:46:07AM +0400, Kirill Tkhai wrote: > > > --- x/kernel/sched/fair.c > > > +++ x/kernel/sched/fair.c > > > @@ -1165,7 +1165,7 @@ static void task_numa_compare(struct tas > > > > > > rcu_read_lock(); > > > cur = ACCESS_ONCE(dst_rq->curr); > > > - if (cur->pid == 0) /* idle */ > > > + if (is_idle_task(cur) || (curr->flags & PF_EXITING)) > > > cur = NULL; > > > > > > /* > > > > > > > Looks like, we have to use the same fix for task_numa_group(). > > Don't think so, task_numa_group() is only called from task_numa_fault() > which is on 'current' and neither idle and PF_EXITING should be > faulting. Isn't task_numa_group() fully preemptible? It seems cpu_rq(cpu)->curr is not always equal to p. -- 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/