public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-tip-commits@vger.kernel.org" 
	<linux-tip-commits@vger.kernel.org>
Cc: Lukas Hannen <lukas.hannen@opensource.tttech-industrial.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"x86@kernel.org" <x86@kernel.org>
Subject: RE: [tip: timers/urgent] time: Handle negative seconds correctly in timespec64_to_ns()
Date: Wed, 8 Sep 2021 16:01:43 +0000	[thread overview]
Message-ID: <a4bbf640306c42429afda8a4fc396f98@AcuMS.aculab.com> (raw)
In-Reply-To: <163111620295.25758.18154572095175068828.tip-bot2@tip-bot2>

> Committer:     Thomas Gleixner <tglx@linutronix.de>
> CommitterDate: Wed, 08 Sep 2021 17:44:26 +02:00
> 
> time: Handle negative seconds correctly in timespec64_to_ns()
> 
> timespec64_ns() prevents multiplication overflows by comparing the seconds
> value of the timespec to KTIME_SEC_MAX. If the value is greater or equal it
> returns KTIME_MAX.
> 
> But that check casts the signed seconds value to unsigned which makes the
> comparision true for all negative values and therefore return wrongly
> KTIME_MAX.
> 
> Negative second values are perfectly valid and required in some places,
> e.g. ptp_clock_adjtime().
> 
> Remove the cast and add a check for the negative boundary which is required
> to prevent undefined behaviour due to multiplication underflow.
> 
> Fixes: cb47755725da ("time: Prevent undefined behaviour in timespec64_to_ns()")'
> Signed-off-by: Lukas Hannen <lukas.hannen@opensource.tttech-industrial.com>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Cc: stable@vger.kernel.org
> Link:
> https://lore.kernel.org/r/AM6PR01MB541637BD6F336B8FFB72AF80EEC69@AM6PR01MB5416.eurprd01.prod.exchangel
> abs.com
> ---
>  include/linux/time64.h |  9 +++++++--
>  1 file changed, 7 insertions(+), 2 deletions(-)
> 
> diff --git a/include/linux/time64.h b/include/linux/time64.h
> index 5117cb5..81b9686 100644
> --- a/include/linux/time64.h
> +++ b/include/linux/time64.h
> @@ -25,7 +25,9 @@ struct itimerspec64 {
>  #define TIME64_MIN			(-TIME64_MAX - 1)
> 
>  #define KTIME_MAX			((s64)~((u64)1 << 63))
> +#define KTIME_MIN			(-KTIME_MAX - 1)
>  #define KTIME_SEC_MAX			(KTIME_MAX / NSEC_PER_SEC)
> +#define KTIME_SEC_MIN			(KTIME_MIN / NSEC_PER_SEC)
> 
>  /*
>   * Limits for settimeofday():
> @@ -124,10 +126,13 @@ static inline bool timespec64_valid_settod(const struct timespec64 *ts)
>   */
>  static inline s64 timespec64_to_ns(const struct timespec64 *ts)
>  {
> -	/* Prevent multiplication overflow */
> -	if ((unsigned long long)ts->tv_sec >= KTIME_SEC_MAX)
> +	/* Prevent multiplication overflow / underflow */
> +	if (ts->tv_sec >= KTIME_SEC_MAX)
>  		return KTIME_MAX;
> 
> +	if (ts->tv_sec <= KTIME_SEC_MIN)
> +		return KTIME_MIN;
> +
>  	return ((s64) ts->tv_sec * NSEC_PER_SEC) + ts->tv_nsec;
>  }

Adding tv_nsec can still overflow -  even if tv_nsec is bounded to +/- 1 second.
This is no more 'garbage in' => 'garbage out' than the code without the
multiply under/overflow check.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

  reply	other threads:[~2021-09-08 16:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AM6PR01MB541637BD6F336B8FFB72AF80EEC69@AM6PR01MB5416.eurprd01.prod.exchangelabs.com>
2021-09-08 15:50 ` [tip: timers/urgent] time: Handle negative seconds correctly in timespec64_to_ns() tip-bot2 for Lukas Hannen
2021-09-08 16:01   ` David Laight [this message]
2021-09-08 20:11     ` Thomas Gleixner

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=a4bbf640306c42429afda8a4fc396f98@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=lukas.hannen@opensource.tttech-industrial.com \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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