From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Giovanni Gherdovich <ggherdovich@suse.cz>,
Linus Torvalds <torvalds@linux-foundation.org>,
Mel Gorman <mgorman@techsingularity.net>,
Mike Galbraith <mgalbraith@suse.de>,
Paolo Bonzini <pbonzini@redhat.com>,
Rik van Riel <riel@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Wanpeng Li <wanpeng.li@hotmail.com>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH v3] sched/cputime: Protect some other sum_exec_runtime reads on 32 bit cpus
Date: Wed, 7 Sep 2016 08:38:27 +0200 [thread overview]
Message-ID: <20160907063826.GA16999@redhat.com> (raw)
In-Reply-To: <20160906190129.GO10153@twins.programming.kicks-ass.net>
On Tue, Sep 06, 2016 at 09:01:29PM +0200, Peter Zijlstra wrote:
> On Tue, Sep 06, 2016 at 02:49:08PM +0200, Stanislaw Gruszka wrote:
> > diff --git a/kernel/exit.c b/kernel/exit.c
> > index 2f974ae..a46f96f 100644
> > --- a/kernel/exit.c
> > +++ b/kernel/exit.c
> > @@ -134,7 +134,7 @@ static void __exit_signal(struct task_struct *tsk)
> > sig->inblock += task_io_get_inblock(tsk);
> > sig->oublock += task_io_get_oublock(tsk);
> > task_io_accounting_add(&sig->ioac, &tsk->ioac);
> > - sig->sum_sched_runtime += tsk->se.sum_exec_runtime;
> > + sig->sum_sched_runtime += read_sum_exec_runtime(tsk);
> > sig->nr_threads--;
> > __unhash_process(tsk, group_dead);
> > write_sequnlock(&sig->stats_lock);
>
> If I'm not mistaken, at this point @p is dead, sum_exec_runtime will not
> ever be updated again.
I think at this point find_task_by_vpid() will still return not-null
pointer, hence we can update sum_exec_runtime via:
posix_cpu_{clock_get(),timer_set(),timer_get()} ->
cpu_clock_sample() -> task_sched_runtime() -> update_curr()
if some thread will do cpuclock/cputimer related syscall for
different thread and CPUCLOCK_SCHED clock.
> > 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.
It still can be updated via syscalls on different thread, same paths
as above.
> > @@ -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.
Same :-) But this could be optimized to avoid taking lock if not needed:
if (expires->sum_exec_runtime != 0)
task_sample.sum_exec_runtime = read_sum_exec_runtime(tsk);
Stanislaw
next prev parent reply other threads:[~2016-09-07 6:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-06 12:49 [PATCH v3] sched/cputime: Protect some other sum_exec_runtime reads on 32 bit cpus Stanislaw Gruszka
2016-09-06 19:01 ` Peter Zijlstra
2016-09-07 6:38 ` Stanislaw Gruszka [this message]
2016-09-07 7:01 ` Peter Zijlstra
2016-09-07 6:50 ` Peter Zijlstra
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=20160907063826.GA16999@redhat.com \
--to=sgruszka@redhat.com \
--cc=ggherdovich@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mgalbraith@suse.de \
--cc=mgorman@techsingularity.net \
--cc=mingo@kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=wanpeng.li@hotmail.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