Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 5 Dec 2018 19:20:01 +0900
From:   Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To:     Dave Rodgman <dave.rodgman@arm.com>
Cc:     Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
        "herbert@gondor.apana.org.au" <herbert@gondor.apana.org.au>,
        "davem@davemloft.net" <davem@davemloft.net>,
        Matt Sealey <Matt.Sealey@arm.com>,
        "nitingupta910@gmail.com" <nitingupta910@gmail.com>,
        "markus@oberhumer.com" <markus@oberhumer.com>,
        "minchan@kernel.org" <minchan@kernel.org>,
        "sonnyrao@google.com" <sonnyrao@google.com>,
        "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
        nd <nd@arm.com>, "sfr@canb.auug.org.au" <sfr@canb.auug.org.au>
Subject: Re: [PATCH v4 0/7] lib/lzo: performance improvements
Message-ID: <20181205102001.GA453@jagdpanzerIV>
References: <20181130142600.13782-1-dave.rodgman@arm.com>
 <20181205073029.GA30820@jagdpanzerIV>
 <c4a9e85f-498e-337a-5bb1-b9c5e58acacd@arm.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <c4a9e85f-498e-337a-5bb1-b9c5e58acacd@arm.com>
User-Agent: Mutt/1.11.1 (2018-12-01)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On (12/05/18 09:50), Dave Rodgman wrote:
> > lib/lzo/lzo1x_compress.c: In function ‘lzo1x_1_do_compress’:
> > lib/lzo/lzo1x_compress.c:239:14: warning: ‘m_pos’ may be used uninitialized in this function [-Wmaybe-uninitialized]
> > 239 |   m_off = ip - m_pos;
> > 
> > Care to take a look? (could be false positive)
> 
> Hi Sergey,

Hi,

> This warning (it's a false positive only seen with gcc) was fixed
> by v4 of this patchset.

OK, cool.

> I've just tested the latest linux-next/master (next-20181205)
> and it doesn't have this issue.

Indeed.

	-ss