Received: by 10.192.165.156 with SMTP id m28csp2936831imm; Sun, 15 Apr 2018 12:48:00 -0700 (PDT) X-Google-Smtp-Source: AIpwx4+TZ77ewebqC8pO++U5/gVCRxVWhssI+/EZ0+3SMEphRQVMvGmwcqtryR4z3ly0C7TVZ0// X-Received: by 10.98.161.10 with SMTP id b10mr10223049pff.214.1523821679954; Sun, 15 Apr 2018 12:47:59 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523821679; cv=none; d=google.com; s=arc-20160816; b=EI6iHKkJ93sUSCntVAypiXUFRMl+ZLSvAKdCExTZb3DfuFeDJXce1ilXZzlv9HKEel VxQqitMU/Uz/EAA4lcmzsriqXYVqI70cLZR/Olaa5Iv5I6EKnjvNpceAnEEMW3xnW3fH hVLxdxZnK0mo7bgkUbgFrFq2/zNdLjhM2GBaOFXiskXjac3NhjxoB7aKiwuYGmkHsc2a nelg+WeQcZgvMxDy7xYQR3khDiJaj1oV2Po3xxewyN7IHDnRF98/ZS4j2ojDRKctzrKW VEP45HEC3hLPDGL70NE66Cv6I6cu3nz6B9+wyU3y3X0aypEBOxobSVMcDJ0hc+v4Qnme fS0Q== 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=p6VkosM2kQlq9usUBuKD4fiaCPCH78blNbbNe16/yQY=; b=0gUQDOsDNp4SZORWVyoHIDDW04hW+ADXh/i3rUMFbeJHQvXAMnoiHSbMgu+i7I7DcS Dc1P88KLBlmfrE7zU8CA2SZEI8Ecc9P5OKv2IfWtMbFTAfTP0yL5IOApSNBLEgao4EUJ UtjLAhP95ZJvU4GqY148FCn2erZCDfF5wXCNqDY1HbopL0ZG7JdyoKhQkD94YMSeZi1F NnN1f7O7Xh7AE/zyc7W4A265SxhoDfGsboc/ALyCYuwrlOJHE1NfFvzTx3Y1ZO2fPxxR 87hv6nQ6QqaqzHWmEAozCp4dnJAhoddSGyl1+H8uv1GB/hxoADAxwOOO+2A6m4Sn83TX 7ayw== 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 o14si8351957pgn.36.2018.04.15.12.47.34; Sun, 15 Apr 2018 12:47:59 -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 S1752840AbeDOTd3 (ORCPT + 99 others); Sun, 15 Apr 2018 15:33:29 -0400 Received: from mail.kernel.org ([198.145.29.99]:52012 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752464AbeDOTd1 (ORCPT ); Sun, 15 Apr 2018 15:33:27 -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 E0DC82172D; Sun, 15 Apr 2018 19:33:24 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E0DC82172D 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: Sun, 15 Apr 2018 20:33:21 +0100 From: Jonathan Cameron To: Eugen Hristev Cc: , , , , , , , , , Subject: Re: [PATCH v3 06/11] iio: inkern: add module put/get on iio dev module when requesting channels Message-ID: <20180415203321.1aaaf91e@archlinux> In-Reply-To: <1523350677-27106-7-git-send-email-eugen.hristev@microchip.com> References: <1523350677-27106-1-git-send-email-eugen.hristev@microchip.com> <1523350677-27106-7-git-send-email-eugen.hristev@microchip.com> 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 Tue, 10 Apr 2018 11:57:52 +0300 Eugen Hristev wrote: > When requesting channels for a particular consumer device, > besides requesting the device (incrementing the reference counter), also > do it for the driver module of the iio dev. This will avoid the situation > where the producer IIO device can be removed and the consumer is still > present in the kernel. > > Signed-off-by: Eugen Hristev > --- > drivers/iio/inkern.c | 8 +++++++- > 1 file changed, 7 insertions(+), 1 deletion(-) > > diff --git a/drivers/iio/inkern.c b/drivers/iio/inkern.c > index ec98790..68d9b87 100644 > --- a/drivers/iio/inkern.c > +++ b/drivers/iio/inkern.c > @@ -11,6 +11,7 @@ > #include > #include > #include > +#include > > #include > #include "iio_core.h" > @@ -152,6 +153,7 @@ static int __of_iio_channel_get(struct iio_channel *channel, > if (index < 0) > goto err_put; > channel->channel = &indio_dev->channels[index]; > + try_module_get(channel->indio_dev->driver_module); And if it fails? (the module we are trying to get is going away...) We should try and handle it I think. Be it by just erroring out of here. > > return 0; > > @@ -256,8 +258,10 @@ static struct iio_channel *of_iio_channel_get_all(struct device *dev) > return chans; > > error_free_chans: > - for (i = 0; i < mapind; i++) > + for (i = 0; i < mapind; i++) { > + module_put(chans[i].indio_dev->driver_module); > iio_device_put(chans[i].indio_dev); > + } > kfree(chans); > return ERR_PTR(ret); > } > @@ -351,6 +355,7 @@ void iio_channel_release(struct iio_channel *channel) > { > if (!channel) > return; > + module_put(channel->indio_dev->driver_module); > iio_device_put(channel->indio_dev); > kfree(channel); > } > @@ -482,6 +487,7 @@ void iio_channel_release_all(struct iio_channel *channels) > struct iio_channel *chan = &channels[0]; > > while (chan->indio_dev) { > + module_put(chan->indio_dev->driver_module); > iio_device_put(chan->indio_dev); > chan++; > }