Return-Path: <cyrus@holtmann.org>
From: Szymon Janc <szymon.janc@gmail.com>
To: Andrei Emeltchenko <Andrei.Emeltchenko.news@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 09/17] mcap: Fix possible overflow
Date: Tue, 17 Jun 2014 23:11:01 +0200
Message-ID: <13363908.gOkADGD5ib@athlon>
In-Reply-To: <1402905472-17643-9-git-send-email-Andrei.Emeltchenko.news@gmail.com>
References: <1402905472-17643-1-git-send-email-Andrei.Emeltchenko.news@gmail.com> <1402905472-17643-9-git-send-email-Andrei.Emeltchenko.news@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: linux-bluetooth-owner@vger.kernel.org
List-ID: <linux-bluetooth.vger.kernel.org>

Hi Andrei,

On Monday 16 June 2014 10:57:44 Andrei Emeltchenko wrote:
> From: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
> 
> ---
>  profiles/health/mcap_sync.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/profiles/health/mcap_sync.c b/profiles/health/mcap_sync.c
> index cc89d47..a0cc02a 100644
> --- a/profiles/health/mcap_sync.c
> +++ b/profiles/health/mcap_sync.c
> @@ -187,7 +187,7 @@ void mcap_sync_stop(struct mcap_mcl *mcl)
> 
>  static uint64_t time_us(struct timespec *tv)
>  {
> -	return tv->tv_sec * 1000000 + tv->tv_nsec / 1000;
> +	return tv->tv_sec * 1000000ll + tv->tv_nsec / 1000ll;
>  }
> 
>  static int64_t bt2us(int bt)

Commit message explaining why there is possible overflow would be nice.


-- 
Szymon K. Janc
szymon.janc@gmail.com