Received: by 10.213.65.68 with SMTP id h4csp522197imn; Sat, 17 Mar 2018 12:58:59 -0700 (PDT) X-Google-Smtp-Source: AG47ELtHb1dXuRHWQ+xq+HUo56Asquu9oQXvV4SWtthzTfhh+1FK5ZR11S0NKnrOL9x5QPpX7wlx X-Received: by 10.99.163.67 with SMTP id v3mr4958944pgn.298.1521316738969; Sat, 17 Mar 2018 12:58:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1521316738; cv=none; d=google.com; s=arc-20160816; b=qnEa4vvWsj3OX0pP3UZ3ksCdttLXLxyOKEjVAmMaseA6eoSpfxsc/OnA8TBvGZViVA JhJ+XcukmZaB0dCp6XiOUwiw+LIjw4vbsQab00hAAhppmR6NNMysQ/qaaper7/MkkcxB J17KT3fYwC2Jxf/eB5NeQOqOWXAmltRW/JTgFw2VD9W9KcsAz9ZL7ZCEJ8N9NjSB726l nlQofs/UvrkDE1Mvm/1C8z5UiB+GYxuKqPsXC2NfyRsIv5xkQXsWq3wpy6Nazypc5otz 8qV+BsAvd+RN6a5uxBRv2ussJdj0QANPSRYvjrDxSpzsGIrkNK2/QzRRyFDhcR1MIVNG MG6A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dmarc-filter:arc-authentication-results; bh=Lpn2dGuM0vux9I3PZVlytpD70K99WK3x+VvgbeBxTGg=; b=C7U2TqRErW7oiG58U8WX4y6ZhV2FEi0Gf798jcb4rSlE5liFB0yGy3Vxhm7O7DYM0e r23yeigr0yXsWEEyMHNXXdCYwiSSDKBSQPTgVAFxczACe7ypWAFb/WF+IXlTh3e8sY9S qNaE5aDg7VWvm1hxbxa25tNwo2ddydeA9pmPhZdcM+872kkdrurxMWPCYfPjd/nG3QCX b5h4qv5r+IiU2JPDLAhxn30bZ0Xn2TnLbQWNThyFA+b4h4VmOiwPM0BrMQi35MEm6SoY RG7esUPc1qFxpDe0E6F3miexJtkLm/zjlnNajJu0Ru6djIykjaz8umIfkYtZ2m+947N4 HSoQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s14si4857571pgf.780.2018.03.17.12.58.44; Sat, 17 Mar 2018 12:58:58 -0700 (PDT) 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; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753911AbeCQTya (ORCPT + 99 others); Sat, 17 Mar 2018 15:54:30 -0400 Received: from mail.kernel.org ([198.145.29.99]:51044 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752836AbeCQTy2 (ORCPT ); Sat, 17 Mar 2018 15:54:28 -0400 Received: from archlinux (cpc91196-cmbg18-2-0-cust659.5-4.cable.virginm.net [81.96.234.148]) (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 81CF521720; Sat, 17 Mar 2018 19:54:25 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 81CF521720 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=kernel.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=jic23@kernel.org Date: Sat, 17 Mar 2018 19:54:22 +0000 From: Jonathan Cameron To: SF Markus Elfring Cc: linux-iio@vger.kernel.org, Greg Kroah-Hartman , Hartmut Knaack , Lars-Peter Clausen , Peter Meerwald-Stadler , Pravin Shedge , Quentin Schulz , LKML , kernel-janitors@vger.kernel.org Subject: Re: [PATCH] iio/gyro/bmg160_core: Improve unlocking of a mutex in five functions Message-ID: <20180317195422.037a8b57@archlinux> In-Reply-To: <16623de4-351d-135b-f3ff-701a465c5d92@users.sourceforge.net> References: <16623de4-351d-135b-f3ff-701a465c5d92@users.sourceforge.net> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; 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 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 14 Mar 2018 16:15:32 +0100 SF Markus Elfring wrote: > From: Markus Elfring > Date: Wed, 14 Mar 2018 16:06:49 +0100 > > * Add jump targets so that a call of the function "mutex_unlock" is stored > only once in these function implementations. > > * Replace 19 calls by goto statements. > > This issue was detected by using the Coccinelle software. > > Signed-off-by: Markus Elfring Hi Markus, Some of these are good and sensible changes - others break the code. Please be careful to fully check all the resulting paths and ensure we don't change wether the lock is still held in all exit paths. Note a function that isn't lockdep annotated should not be holding any locks, that it took, upon exit. > --- > drivers/iio/gyro/bmg160_core.c | 103 ++++++++++++++++++----------------------- > 1 file changed, 45 insertions(+), 58 deletions(-) > > diff --git a/drivers/iio/gyro/bmg160_core.c b/drivers/iio/gyro/bmg160_core.c > index 63ca31628a93..fa367fd7bc8c 100644 > --- a/drivers/iio/gyro/bmg160_core.c > +++ b/drivers/iio/gyro/bmg160_core.c > @@ -499,21 +499,19 @@ static int bmg160_get_temp(struct bmg160_data *data, int *val) > > mutex_lock(&data->mutex); > ret = bmg160_set_power_state(data, true); > - if (ret < 0) { > - mutex_unlock(&data->mutex); > - return ret; > - } > + if (ret < 0) > + goto unlock; > > ret = regmap_read(data->regmap, BMG160_REG_TEMP, &raw_val); > if (ret < 0) { > dev_err(dev, "Error reading reg_temp\n"); > bmg160_set_power_state(data, false); > - mutex_unlock(&data->mutex); > - return ret; > + goto unlock; > } > > *val = sign_extend32(raw_val, 7); > ret = bmg160_set_power_state(data, false); > +unlock: > mutex_unlock(&data->mutex); > if (ret < 0) > return ret; > @@ -529,22 +527,20 @@ static int bmg160_get_axis(struct bmg160_data *data, int axis, int *val) > > mutex_lock(&data->mutex); > ret = bmg160_set_power_state(data, true); > - if (ret < 0) { > - mutex_unlock(&data->mutex); > - return ret; > - } > + if (ret < 0) > + goto unlock; > > ret = regmap_bulk_read(data->regmap, BMG160_AXIS_TO_REG(axis), &raw_val, > sizeof(raw_val)); > if (ret < 0) { > dev_err(dev, "Error reading axis %d\n", axis); > bmg160_set_power_state(data, false); > - mutex_unlock(&data->mutex); > - return ret; > + goto unlock; > } > > *val = sign_extend32(le16_to_cpu(raw_val), 15); > ret = bmg160_set_power_state(data, false); > +unlock: > mutex_unlock(&data->mutex); > if (ret < 0) > return ret; > @@ -632,19 +628,16 @@ static int bmg160_write_raw(struct iio_dev *indio_dev, > * mode to power on for other writes. > */ > ret = bmg160_set_power_state(data, true); > - if (ret < 0) { > - mutex_unlock(&data->mutex); > - return ret; > - } > + if (ret < 0) > + goto unlock; > + > ret = bmg160_set_bw(data, val); > if (ret < 0) { > bmg160_set_power_state(data, false); > - mutex_unlock(&data->mutex); > - return ret; > + goto unlock; > } > - ret = bmg160_set_power_state(data, false); > - mutex_unlock(&data->mutex); > - return ret; > + > + goto set_power_state; > case IIO_CHAN_INFO_LOW_PASS_FILTER_3DB_FREQUENCY: > if (val2) > return -EINVAL; > @@ -653,18 +646,15 @@ static int bmg160_write_raw(struct iio_dev *indio_dev, > ret = bmg160_set_power_state(data, true); > if (ret < 0) { > bmg160_set_power_state(data, false); > - mutex_unlock(&data->mutex); > - return ret; > + goto unlock; > } > ret = bmg160_set_filter(data, val); > if (ret < 0) { > bmg160_set_power_state(data, false); > - mutex_unlock(&data->mutex); > - return ret; > + goto unlock; > } > - ret = bmg160_set_power_state(data, false); > - mutex_unlock(&data->mutex); > - return ret; > + > + goto set_power_state; > case IIO_CHAN_INFO_SCALE: > if (val) > return -EINVAL; > @@ -672,24 +662,27 @@ static int bmg160_write_raw(struct iio_dev *indio_dev, > mutex_lock(&data->mutex); > /* Refer to comments above for the suspend mode ops */ > ret = bmg160_set_power_state(data, true); > - if (ret < 0) { > - mutex_unlock(&data->mutex); > - return ret; > - } > + if (ret < 0) > + goto unlock; > + > ret = bmg160_set_scale(data, val2); > if (ret < 0) { > bmg160_set_power_state(data, false); > - mutex_unlock(&data->mutex); > - return ret; > + goto unlock; > } > - ret = bmg160_set_power_state(data, false); > - mutex_unlock(&data->mutex); Please keep the mutex_unlock in the same scope as the mutex_lock. I may make sense to take both outside the switch statement but that needs careful consideration. > - return ret; > + > + goto set_power_state; > default: > return -EINVAL; We exit with the mutex locked now and it should not be. > } > > return -EINVAL; Mutex is still locked here and the return is wrong. > + > +set_power_state: > + ret = bmg160_set_power_state(data, false); > +unlock: > + mutex_unlock(&data->mutex); blank line before the return. > + return ret; > } > > static int bmg160_read_event(struct iio_dev *indio_dev, > @@ -763,8 +756,8 @@ static int bmg160_write_event_config(struct iio_dev *indio_dev, > > if (!state && data->motion_trigger_on) { > data->ev_enable_state = 0; > - mutex_unlock(&data->mutex); > - return 0; > + ret = 0; Put this in as the value at instantiation. int ret = 0; > + goto unlock; > } > /* > * We will expect the enable and disable to do operation in > @@ -776,22 +769,19 @@ static int bmg160_write_event_config(struct iio_dev *indio_dev, > * is always on so sequence doesn't matter > */ > ret = bmg160_set_power_state(data, state); > - if (ret < 0) { > - mutex_unlock(&data->mutex); > - return ret; > - } > + if (ret < 0) > + goto unlock; > > ret = bmg160_setup_any_motion_interrupt(data, state); > if (ret < 0) { > bmg160_set_power_state(data, false); > - mutex_unlock(&data->mutex); > - return ret; > + goto unlock; > } > > data->ev_enable_state = state; > +unlock: > mutex_unlock(&data->mutex); > - Blank line preferred before the return ret. > - return 0; > + return ret; > } > > static IIO_CONST_ATTR_SAMP_FREQ_AVAIL("100 200 400 1000 2000"); > @@ -919,8 +909,8 @@ static int bmg160_data_rdy_trigger_set_state(struct iio_trigger *trig, > > if (!state && data->ev_enable_state && data->motion_trigger_on) { > data->motion_trigger_on = false; > - mutex_unlock(&data->mutex); > - return 0; > + ret = 0; Setting ret where it is originally defined to 0 would be tidier. int ret = 0; > + goto unlock; > } > > /* > @@ -928,27 +918,24 @@ static int bmg160_data_rdy_trigger_set_state(struct iio_trigger *trig, > * enable/disable operation order > */ > ret = bmg160_set_power_state(data, state); > - if (ret < 0) { > - mutex_unlock(&data->mutex); > - return ret; > - } > + if (ret < 0) > + goto unlock; > + > if (data->motion_trig == trig) > ret = bmg160_setup_any_motion_interrupt(data, state); > else > ret = bmg160_setup_new_data_interrupt(data, state); > if (ret < 0) { > bmg160_set_power_state(data, false); > - mutex_unlock(&data->mutex); > - return ret; > + goto unlock; > } > if (data->motion_trig == trig) > data->motion_trigger_on = state; > else > data->dready_trigger_on = state; > - > +unlock: > mutex_unlock(&data->mutex); > - > - return 0; I would prefer a blank line between the mutex_unlock and the return. > + return ret; > } > > static const struct iio_trigger_ops bmg160_trigger_ops = {