Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753962AbdLMUsc (ORCPT ); Wed, 13 Dec 2017 15:48:32 -0500 Received: from mail.free-electrons.com ([62.4.15.54]:46778 "EHLO mail.free-electrons.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753860AbdLMUrk (ORCPT ); Wed, 13 Dec 2017 15:47:40 -0500 Date: Wed, 13 Dec 2017 21:47:38 +0100 From: Boris Brezillon To: Colin Ian King Cc: Richard Weinberger , David Woodhouse , Brian Norris , Marek Vasut , Cyrille Pitchen , linux-mtd@lists.infradead.org, kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH][mtd-next] mtd: nand: remove redundant check of len Message-ID: <20171213214738.7ce39659@bbrezillon> In-Reply-To: References: <20171213201743.27324-1-colin.king@canonical.com> <20171213212425.6fe999cb@bbrezillon> <20171213213844.78efe253@bbrezillon> X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1194 Lines: 34 On Wed, 13 Dec 2017 20:44:45 +0000 Colin Ian King wrote: > On 13/12/17 20:38, Boris Brezillon wrote: > > On Wed, 13 Dec 2017 20:30:04 +0000 > > Colin Ian King wrote: > > > >> On 13/12/17 20:24, Boris Brezillon wrote: > >>> On Wed, 13 Dec 2017 20:17:43 +0000 > >>> Colin King wrote: > >>> > >>>> From: Colin Ian King > >>>> > >>>> The check of len being zero is redundant as it has already been > >>>> sanity checked for this value at the start of the function. Hence > >>>> it is impossible for this test to be true and so the redundant > >>>> code can be removed. > >>> > >>> Nope, it's not the same test, the initial test is > >>> > >>> if (len && !buf) > >> > >> Ah, the current tip from linux-next has: > >> > >> 1912 if (!len || !buf) > >> 1913 return -EINVAL; > >> > >> ..so I guess that's why it got picked up by static analysis. > > > > Hm, that's weird, that's not what I see [1] in linux-next. > > I see my mistake, I fixed the *wrong* function, I'll send a v2. Doh. Yep, just noticed that too. No need to send a patch though.