All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	Borislav Petkov <bp@alien8.de>,
	linux-kernel@vger.kernel.org
Subject: [PATCH -tip] sched/cputime: do not scale when utime == 0
Date: Wed, 4 Sep 2013 14:08:58 +0200	[thread overview]
Message-ID: <20130904120857.GB2564@redhat.com> (raw)
In-Reply-To: <20130903183229.GB30757@gmail.com>

scale_stime() silently assumes that stime < rtime, otherwise when
stime == rtime and both values are big (operations on them do not fit
in 32 bits), the resulting scaling stime can be bigger than rtime.
In consequence utime = rtime - stime results in negative value.

Reported-and-tested-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: stable@vger.kernel.org
Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
---
 kernel/sched/cputime.c |   19 +++++++++++--------
 1 files changed, 11 insertions(+), 8 deletions(-)

diff --git a/kernel/sched/cputime.c b/kernel/sched/cputime.c
index ace34f9..9994791 100644
--- a/kernel/sched/cputime.c
+++ b/kernel/sched/cputime.c
@@ -551,10 +551,7 @@ static void cputime_adjust(struct task_cputime *curr,
 			   struct cputime *prev,
 			   cputime_t *ut, cputime_t *st)
 {
-	cputime_t rtime, stime, utime, total;
-
-	stime = curr->stime;
-	total = stime + curr->utime;
+	cputime_t rtime, stime, utime;
 
 	/*
 	 * Tick based cputime accounting depend on random scheduling
@@ -576,13 +573,19 @@ static void cputime_adjust(struct task_cputime *curr,
 	if (prev->stime + prev->utime >= rtime)
 		goto out;
 
-	if (total) {
+	stime = curr->stime;
+	utime = curr->utime;
+
+	if (utime == 0) {
+		stime = rtime;
+	} else if (stime == 0) {
+		utime = rtime;
+	} else {
+		cputime_t total = stime + utime;
+
 		stime = scale_stime((__force u64)stime,
 				    (__force u64)rtime, (__force u64)total);
 		utime = rtime - stime;
-	} else {
-		stime = rtime;
-		utime = 0;
 	}
 
 	/*
-- 
1.7.1


  reply	other threads:[~2013-09-04 12:11 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-20 11:14 [sched next] overflowed cpu time for kernel threads in /proc/PID/stat Sergey Senozhatsky
2013-08-20 15:15 ` Frederic Weisbecker
2013-08-20 15:35   ` Sergey Senozhatsky
2013-08-20 15:42     ` Frederic Weisbecker
2013-08-20 15:53       ` Sergey Senozhatsky
2013-08-20 18:48       ` Sergey Senozhatsky
2013-08-21 15:39       ` Sergey Senozhatsky
2013-08-30 23:04         ` Frederic Weisbecker
2013-08-31 19:01           ` Sergey Senozhatsky
2013-09-08 10:56             ` Frederic Weisbecker
2013-09-08 10:59             ` Frederic Weisbecker
2013-09-02 12:28           ` Sergey Senozhatsky
2013-09-02 13:07             ` Frederic Weisbecker
2013-09-02 13:39               ` Sergey Senozhatsky
2013-09-02 13:50               ` Stanislaw Gruszka
2013-09-02 14:00                 ` Sergey Senozhatsky
2013-09-03  8:43                   ` Stanislaw Gruszka
2013-09-03  9:33                     ` Sergey Senozhatsky
2013-09-03 13:15                     ` Sergey Senozhatsky
2013-09-03 18:09                     ` Sergey Senozhatsky
2013-09-03 18:32                       ` Ingo Molnar
2013-09-04 12:08                         ` Stanislaw Gruszka [this message]
2013-09-04 12:33                           ` [PATCH -tip] sched/cputime: do not scale when utime == 0 Ingo Molnar
2013-09-04 13:16                             ` [PATCH -tip v2] " Stanislaw Gruszka
2013-09-04 14:31                               ` Ingo Molnar
2013-09-04 14:37                               ` [tip:timers/urgent] sched/cputime: Do " tip-bot for Stanislaw Gruszka
2013-09-04 15:35                                 ` Frederic Weisbecker
2013-09-02 14:13                 ` [sched next] overflowed cpu time for kernel threads in /proc/PID/stat Frederic Weisbecker
2013-09-02 14:24                   ` Sergey Senozhatsky

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=20130904120857.GB2564@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=bp@alien8.de \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=peterz@infradead.org \
    --cc=sergey.senozhatsky@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.