[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191006181439.GU22609@kadam>
Date: Sun, 6 Oct 2019 21:14:40 +0300
From: Dan Carpenter <dan.carpenter@...cle.com>
To: Jonathan Cameron <jic23@...nel.org>
Cc: "Ardelean, Alexandru" <alexandru.Ardelean@...log.com>,
"lars@...afoo.de" <lars@...afoo.de>,
"kernel-janitors@...r.kernel.org" <kernel-janitors@...r.kernel.org>,
"Popa, Stefan Serban" <StefanSerban.Popa@...log.com>,
"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Hennerich, Michael" <Michael.Hennerich@...log.com>,
"pmeerw@...erw.net" <pmeerw@...erw.net>,
"knaack.h@....de" <knaack.h@....de>
Subject: Re: [PATCH] iio: imu: adis16480: clean up a condition
On Sun, Oct 06, 2019 at 09:51:33AM +0100, Jonathan Cameron wrote:
> On Thu, 26 Sep 2019 14:36:30 +0300
> Dan Carpenter <dan.carpenter@...cle.com> wrote:
>
> > On Thu, Sep 26, 2019 at 11:06:39AM +0000, Ardelean, Alexandru wrote:
> > > On Thu, 2019-09-26 at 11:10 +0300, Dan Carpenter wrote:
> > > > [External]
> > > >
> > > > The "t" variable is unsigned so it can't be less than zero. We really
> > > > are just trying to prevent divide by zero bugs so just checking against
> > > > zero is sufficient.
>
> I'm not sure that true. It if were signed we'd be detecting that the
> input from userspace was negative.
It does a really bad job of that though so it raises more questions than
answers. Maybe just one of the parameters is negative or maybe the
multiply or the addition overflowed? Should scenarios those be checked?
It turns out none of those situations matter, only divide by zero needs
to be checked.
regards,
dan carpenter
Powered by blists - more mailing lists