From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932672AbcIGGvH (ORCPT ); Wed, 7 Sep 2016 02:51:07 -0400 Received: from merlin.infradead.org ([205.233.59.134]:44780 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932260AbcIGGvG (ORCPT ); Wed, 7 Sep 2016 02:51:06 -0400 Date: Wed, 7 Sep 2016 08:50:57 +0200 From: Peter Zijlstra To: Stanislaw Gruszka Cc: linux-kernel@vger.kernel.org, Giovanni Gherdovich , Linus Torvalds , Mel Gorman , Mike Galbraith , Paolo Bonzini , Rik van Riel , Thomas Gleixner , Wanpeng Li , Ingo Molnar Subject: Re: [PATCH v3] sched/cputime: Protect some other sum_exec_runtime reads on 32 bit cpus Message-ID: <20160907065057.GM10168@twins.programming.kicks-ass.net> References: <1473166148-8466-1-git-send-email-sgruszka@redhat.com> <20160906190129.GO10153@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160906190129.GO10153@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.23.1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Sep 06, 2016 at 09:01:29PM +0200, Peter Zijlstra wrote: > > diff --git a/kernel/time/posix-cpu-timers.c b/kernel/time/posix-cpu-timers.c > > index 39008d7..a2d753b 100644 > > --- a/kernel/time/posix-cpu-timers.c > > +++ b/kernel/time/posix-cpu-timers.c > > @@ -848,7 +848,7 @@ static void check_thread_timers(struct task_struct *tsk, > > tsk_expires->virt_exp = expires_to_cputime(expires); > > > > tsk_expires->sched_exp = check_timers_list(++timers, firing, > > - tsk->se.sum_exec_runtime); > > + read_sum_exec_runtime(tsk)); > > > > /* > > * Check for the special case thread timers. > > @tsk == current and IRQs are disabled, sum_exec_runtime cannot be > updated. > > > @@ -1115,7 +1115,7 @@ static inline int fastpath_timer_check(struct task_struct *tsk) > > struct task_cputime task_sample; > > > > task_cputime(tsk, &task_sample.utime, &task_sample.stime); > > - task_sample.sum_exec_runtime = tsk->se.sum_exec_runtime; > > + task_sample.sum_exec_runtime = read_sum_exec_runtime(tsk); > > if (task_cputime_expired(&task_sample, &tsk->cputime_expires)) > > return 1; > > } > > Same. Sorry, I forgot syscalls, those can muck with update_curr() remotely. So yes, those are needed.