[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1485546128.4267.25.camel@sandisk.com>
Date: Fri, 27 Jan 2017 19:42:28 +0000
From: Bart Van Assche <Bart.VanAssche@...disk.com>
To: "augustocaringi@...il.com" <augustocaringi@...il.com>
CC: "jejb@...ux.vnet.ibm.com" <jejb@...ux.vnet.ibm.com>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"emilne@...hat.com" <emilne@...hat.com>,
"andriy.shevchenko@...ux.intel.com"
<andriy.shevchenko@...ux.intel.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"martin.petersen@...cle.com" <martin.petersen@...cle.com>,
"sagi@...mberg.me" <sagi@...mberg.me>
Subject: Re: [PATCH] scsi: srp_transport: Fix 'always false comparison' in
srp_tmo_valid()
On Fri, 2017-01-27 at 10:06 +0000, Augusto Mecking Caringi wrote:
> On Thu, Jan 26, 2017 at 3:11 PM, Bart Van Assche
> <Bart.VanAssche@...disk.com> wrote:
> > This patch is wrong. The purpose of the dev_loss_tmo >= LONG_MAX / HZ check
> > is to avoid that the expression 1UL * dev_loss_tmo * HZ further down
> > overflows. Can you check whether changing the if-statement into if (1UL *
> > dev_loss_tmo >= LONG_MAX / HZ) also suppresses the compiler warning?
>
> Hi Bart,
>
> Right, now a I see...
>
> Doing your proposed change the warning go away...
>
> Do you want me to send a new patch for that?
Hello Augusto,
If you want your patch to go upstream you will have to repost it.
Bart.
Powered by blists - more mailing lists