Received: by 2002:a05:6a10:c604:0:0:0:0 with SMTP id y4csp2073827pxt; Sun, 8 Aug 2021 10:33:40 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz46b7bVKP1kQX1Fum6Z4GkUod9+vJV0b3qunWGBKd13VG/u6vtGZfyl7XHLD7sIve5RzRf X-Received: by 2002:a92:2e12:: with SMTP id v18mr93202ile.100.1628444020102; Sun, 08 Aug 2021 10:33:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1628444020; cv=none; d=google.com; s=arc-20160816; b=Q67GGAeNVEkTWM56abOr1wGQhHkWeMRWLCG9EhXb5GeFVFwFlnYCOv7Vx10cXxJ1vi wh7dyaAox6gIJLmcauu4J1UbWWouCMr8nLiOlc9WD4ih89kuW/GygrVH7y5JqnZSMA9Y KUbX4TPzdvQdu7Wktea8wyr9QhsZBXR8GoiVtv4McZYDJQASuCnvngEbv5gfpzJBOCxl 0YzuY+0RsIy/HMlzHFZa14NzKb54CTukdgr2G37Qxh8WVkvCB/1qQgC8wQNGfJAJQLLi X0/kB33p5PSlzU7WDk83IjbTRFz1PJC8tEtrvRI0Ud1DtJGP85yw9KCPwWwIMcT5iDF+ QcZg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=8IARKbQ8Q6eCBhC9iPOef4XOPjlYXJLweWup8o6cgvM=; b=JPIcxThgTJeyn8k0Gr/mSHZlgMA9uLJbvMigVc6l5kcEEw75R46GfYlxHfMPis5OMt wni7Tba/9fsQIV9T3IIkVWRhSX7HmMb+MjTzVHeuDdomaYBfhixy46bsgv8reL+1gIfp tmtLM0LkY9Qmwpe2gUMtW1TMl5WwcsKaMUVY7FpEnV3kYMcKrwa067nS/VlMvzGxLOZc e+Y9rrYdM6Pkw7GwL4pGYH9Q5bkjMy3paRgnxIUDEcK8N18uc5GC2NyMjmtz2IS7LgG6 LLjB7pHsWZb1Ty1swtRdnjYLqj+03UbOXoA1FPUF5GJ7eiI1ShG3ygShdFFHuph827sc Y1DQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s18si18095635jan.72.2021.08.08.10.33.29; Sun, 08 Aug 2021 10:33:40 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232210AbhHHRaR (ORCPT + 99 others); Sun, 8 Aug 2021 13:30:17 -0400 Received: from mail.kernel.org ([198.145.29.99]:57808 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230448AbhHHRaQ (ORCPT ); Sun, 8 Aug 2021 13:30:16 -0400 Received: from jic23-huawei (cpc108967-cmbg20-2-0-cust86.5-4.cable.virginm.net [81.101.6.87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 075EE60EE9; Sun, 8 Aug 2021 17:29:53 +0000 (UTC) Date: Sun, 8 Aug 2021 18:32:43 +0100 From: Jonathan Cameron To: Yizhuo Cc: Lars-Peter Clausen , Maxime Coquelin , Alexandre Torgue , Andy Shevchenko , Mark Brown , Mugilraj Dhavachelvan , Olivier Moysan , Krzysztof Kozlowski , Arnaud Pouliquen , linux-iio@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] iio: adc: stm32-dfsdm: Fix the uninitialized use if regmap_read() fails Message-ID: <20210808183243.70619aa8@jic23-huawei> In-Reply-To: <20210724164840.7381053b@jic23-huawei> References: <20210719195313.40341-1-yzhai003@ucr.edu> <20210724164840.7381053b@jic23-huawei> X-Mailer: Claws Mail 4.0.0 (GTK+ 3.24.30; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 24 Jul 2021 16:48:40 +0100 Jonathan Cameron wrote: > On Mon, 19 Jul 2021 19:53:11 +0000 > Yizhuo wrote: > > > Inside function stm32_dfsdm_irq(), the variable "status", "int_en" > > could be uninitialized if the regmap_read() fails and returns an error > > code. However, they are directly used in the later context to decide > > the control flow, which is potentially unsafe. > > > > Fixes: e2e6771c64625 ("IIO: ADC: add STM32 DFSDM sigma delta ADC support") > > > > Signed-off-by: Yizhuo > > Hi Yizhou > > I want to get some review of this from people familiar with the > hardware as there is a small possibility your reordering might have > introduced a problem. To stm32 people, can someone take a look at this? Thanks, Jonathan > > > --- > > drivers/iio/adc/stm32-dfsdm-adc.c | 9 +++++++-- > > 1 file changed, 7 insertions(+), 2 deletions(-) > > > > diff --git a/drivers/iio/adc/stm32-dfsdm-adc.c b/drivers/iio/adc/stm32-dfsdm-adc.c > > index 1cfefb3b5e56..d8b78aead942 100644 > > --- a/drivers/iio/adc/stm32-dfsdm-adc.c > > +++ b/drivers/iio/adc/stm32-dfsdm-adc.c > > @@ -1292,9 +1292,11 @@ static irqreturn_t stm32_dfsdm_irq(int irq, void *arg) > > struct stm32_dfsdm_adc *adc = iio_priv(indio_dev); > > struct regmap *regmap = adc->dfsdm->regmap; > > unsigned int status, int_en; > > + int ret; > > > > - regmap_read(regmap, DFSDM_ISR(adc->fl_id), &status); > > - regmap_read(regmap, DFSDM_CR2(adc->fl_id), &int_en); > > Moving this later is only valid if there aren't any side effects. > The current ordering is strange enough it makes me wonder if there might be! > > Jonathan > > > + ret = regmap_read(regmap, DFSDM_ISR(adc->fl_id), &status); > > + if (ret) > > + return IRQ_HANDLED; > > > > if (status & DFSDM_ISR_REOCF_MASK) { > > /* Read the data register clean the IRQ status */ > > @@ -1303,6 +1305,9 @@ static irqreturn_t stm32_dfsdm_irq(int irq, void *arg) > > } > > > > if (status & DFSDM_ISR_ROVRF_MASK) { > > + ret = regmap_read(regmap, DFSDM_CR2(adc->fl_id), &int_en); > > + if (ret) > > + return IRQ_HANDLED; > > if (int_en & DFSDM_CR2_ROVRIE_MASK) > > dev_warn(&indio_dev->dev, "Overrun detected\n"); > > regmap_update_bits(regmap, DFSDM_ICR(adc->fl_id), >