public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Max R. P. Grossmann" <m@max.pm>
To: linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, john.stultz@linaro.org,
	"Max R. P. Grossmann" <m@max.pm>
Subject: [PATCH] time: POSIX CPU timers: Ensure that variable is initialized
Date: Mon,  8 Jan 2018 20:01:57 +0100	[thread overview]
Message-ID: <20180108190157.10048-1-m@max.pm> (raw)

If cpu_timer_sample_group returns -EINVAL, it will not have written into
*sample. Checking for cpu_timer_sample_group's return value precludes the
potential use of an uninitialized value of now in the following block.
Given an invalid clock_idx, the previous code could otherwise overwrite
*oldval in an undefined manner. This is now prevented. We also exploit
short-circuiting of && to sample the timer only if the result will
actually be used to update *oldval.

Signed-off-by: Max R. P. Grossmann <m@max.pm>
---
 kernel/time/posix-cpu-timers.c | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/kernel/time/posix-cpu-timers.c b/kernel/time/posix-cpu-timers.c
index 1f27887aa194..e54638be6e19 100644
--- a/kernel/time/posix-cpu-timers.c
+++ b/kernel/time/posix-cpu-timers.c
@@ -1189,9 +1189,8 @@ void set_process_cpu_timer(struct task_struct *tsk, unsigned int clock_idx,
 	u64 now;
 
 	WARN_ON_ONCE(clock_idx == CPUCLOCK_SCHED);
-	cpu_timer_sample_group(clock_idx, tsk, &now);
 
-	if (oldval) {
+	if (oldval && cpu_timer_sample_group(clock_idx, tsk, &now) != -EINVAL) {
 		/*
 		 * We are setting itimer. The *oldval is absolute and we update
 		 * it to be relative, *newval argument is relative and we update
-- 
2.15.1

             reply	other threads:[~2018-01-08 19:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08 19:01 Max R. P. Grossmann [this message]
2018-01-14 19:37 ` [PATCH] time: POSIX CPU timers: Ensure that variable is initialized Thomas Gleixner
2018-01-14 19:55 ` [tip:timers/core] posix-cpu-timers: Make set_process_cpu_timer() more robust tip-bot for Max R. P. Grossmann

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=20180108190157.10048-1-m@max.pm \
    --to=m@max.pm \
    --cc=john.stultz@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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