Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp9902910imu; Wed, 5 Dec 2018 12:17:01 -0800 (PST) X-Google-Smtp-Source: AFSGD/UX2AJYawc9wCxjHAzOWNPlF8FzR9+7asTHHRWWFMIqJ6C7q2Y27K7+ltzyRJgZacxTqf9Y X-Received: by 2002:a63:101:: with SMTP id 1mr21733933pgb.152.1544041021319; Wed, 05 Dec 2018 12:17:01 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544041021; cv=none; d=google.com; s=arc-20160816; b=wQ3+fafZL41OBQDc6fvn/1r+q8W9fq/x3g6xeryM84Rojb7H1kMmbQSfyp+9MEVXP0 S2Eb+kv9D21cVOXapBcVaWYvxBy9zCmUgko3fljOc9ZYobngdXTiHl+irRK1y5FKkOHL LU/jJUUkP8X2AnZKcpi9sgHWy+VzEXh1sz+JUWP6LMGamYKsLP8Bj3T85fC3Co4dbPWO rECLQFnaRiel3nRtzhsIDfIqeuDfQyP/7OPZw7mWRaf/V4f2ZGEwIM5DP9cIKNBHG9SY Qp0zATzmGagHm2s4OHiJQ/NNOR7mtcLm3ioZF6ZifNu4HmbmszXEoEsVx2rM7nrGTvEu 8I6w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:references:in-reply-to :message-id:subject:cc:to:from:date:dkim-signature; bh=lipye6iQUwdemJOdf5NCMMGHiDOl2DVHeX6ghVxvvYU=; b=HI69mtQtfVdJM2XBSwUYFNwpEKGay8EoaPn7QAD+KSc0z5XUYv202rLClW0/Spy3E+ pXw2GFESWOwGo4AFY6f1h211H4hMJJJ9/gz36LIW+OdMOHSO+mylF6Ohw98hhkchkvN+ oMTPSpeHNjX5Z1CFZ+S2pauRDBt/qXN8z6/x8t29zfF+a0qBTTY2AguLBasuA7hDz+Z2 s6QKqOUjy33JDmfl0akdEOg7Xmr5MBb/8oFL3/sCAMpFONMH060fyCrRySOhuRwrzIAD 36BfcgoHOcXkV66BKZOkAeOs0IaUiaqHxecDqPMC7O7VolTTuFLOmwDS0s4qEOThY/nZ iD8g== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@kemnade.info header.s=20180802 header.b=eVpR3vJy; 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 m8si19874584pls.400.2018.12.05.12.16.46; Wed, 05 Dec 2018 12:17:01 -0800 (PST) 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; dkim=fail header.i=@kemnade.info header.s=20180802 header.b=eVpR3vJy; 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 S1728411AbeLEUOz (ORCPT + 99 others); Wed, 5 Dec 2018 15:14:55 -0500 Received: from mail.andi.de1.cc ([85.214.239.24]:52192 "EHLO h2641619.stratoserver.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727592AbeLEUOz (ORCPT ); Wed, 5 Dec 2018 15:14:55 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kemnade.info; s=20180802; h=Content-Type:MIME-Version:References: In-Reply-To:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=lipye6iQUwdemJOdf5NCMMGHiDOl2DVHeX6ghVxvvYU=; b=eVpR3vJyBgHAP7TGz2ueJJN/s 6ZAArIqtj4oyMk/O6R2+BxH5fAC1IeJrBkWEzNCT5vzOMCAzU2j0uK+PCeRVc/5Kt+viygcQF5nRg 8MTwoKHSQz5RuYctujxmgiyDggmcCIL7chUCVSsYw53WGzLNxfDD2i9b7nV87dnNxrCqQ=; Received: from p5dcc3ed6.dip0.t-ipconnect.de ([93.204.62.214] helo=aktux) by h2641619.stratoserver.net with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1gUdZM-0004RM-Bu; Wed, 05 Dec 2018 21:14:52 +0100 Date: Wed, 5 Dec 2018 21:14:42 +0100 From: Andreas Kemnade To: Johan Hovold Cc: robh+dt@kernel.org, mark.rutland@arm.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Discussions about the Letux Kernel Subject: Re: [PATCH 1/5] gnss: sirf: write data to gnss only when the gnss device is open Message-ID: <20181205211442.63dc33df@aktux> In-Reply-To: <20181205144739.GE15689@localhost> References: <20181118215801.12280-1-andreas@kemnade.info> <20181118215801.12280-2-andreas@kemnade.info> <20181205144739.GE15689@localhost> X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; boundary="Sig_/P0wFCYhvudvg=8epL0WOEBR"; protocol="application/pgp-signature" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --Sig_/P0wFCYhvudvg=8epL0WOEBR Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Wed, 5 Dec 2018 15:47:39 +0100 Johan Hovold wrote: > On Sun, Nov 18, 2018 at 10:57:57PM +0100, Andreas Kemnade wrote: > > The api forbids writing data there otherwise. Prepare for the > > serdev_open()/close() being a part of runtime pm. > >=20 > > Signed-off-by: Andreas Kemnade > > --- > > drivers/gnss/sirf.c | 16 +++++++++++++++- > > 1 file changed, 15 insertions(+), 1 deletion(-) =20 > =20 > > @@ -73,6 +76,7 @@ static void sirf_close(struct gnss_device *gdev) > > serdev_device_close(serdev); > > =20 > > pm_runtime_put(&serdev->dev); > > + data->opened =3D false; > > } > > =20 > > static int sirf_write_raw(struct gnss_device *gdev, const unsigned cha= r *buf, > > @@ -105,7 +109,17 @@ static int sirf_receive_buf(struct serdev_device *= serdev, > > struct sirf_data *data =3D serdev_device_get_drvdata(serdev); > > struct gnss_device *gdev =3D data->gdev; > > =20 > > - return gnss_insert_raw(gdev, buf, count); > > + /* > > + * we might come here everytime when runtime is resumed > > + * and data is received. Two cases are possible > > + * 1. device is opened during initialisation > > + * 2. kernel is compiled without runtime pm > > + * and device is opened all the time > > + */ > > + if (data->opened) > > + return gnss_insert_raw(gdev, buf, count); =20 >=20 > This can race with sirf_close() when you move serdev handling out of > sirf_open()/close(). Not sure how best to handle that yet. >=20 Ok, first lets check whether we have a common idea of the problem before coming to a solution. So race condition here can happen if the serdev is still opened after the pm_runtime_put in sirf_close() which might happen if runtime is not suspended after that. I missed that case. Then if (data->opened)=20 is checked, data->opened set to false then gnss_insert_raw() is executed. There is data inserted into the fifo which will be read by the next one opening the gnss device. And there might be trouble at deregistering time. And now if we simply add locks: For sirf_receive_buf(), it somehow feels dangerous if we call gnss_insert_raw() with a lock held but I have not analyzed it thoroughly. For sirf_close(), we could simply put a lock around data->opened =3D false; Am I missing something? I will check if anything changes when I move the serdev_open()/close() calls a bit. In the end me end to have the serdev open whenever the userspace wants data or we want to change the state of the gnss chip without wakeup. Maybe add a special driver state for that situation where the power state of the gps chip is changed without having it opened. If we check that at the beginning of that action, we might have luck. Regards, Andreas --Sig_/P0wFCYhvudvg=8epL0WOEBR Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEE7sDbhY5mwNpwYgrAfb1qx03ikyQFAlwIMbIACgkQfb1qx03i kyQMjg//eHFBUJmOa5AywirLIgeFGZxiqlSaHGADIrkOmdNADeOGKliiNDyLR4Gu dAtPSU4rhyNlxTgozPZHFUdQrWFwvB2epOGOU5nX11XPBwYUtKALSU31MsKzEE5z hVHLnf0uyQ8TD/FYZXdv3d0xCGxOhaNGiEZ4eXFMorDonmcTPIcy4A6ljHHrHWBi IcjpBea/vztz9bur7RG3KOi3kNAyPIsrKcQpbKgF9H0AHowjkj84CADoEIJh0V6C Gw6oQVAXtj271x7Aq9V3LXDmJVfZmfWMLnz2WtV6Z66zDQECPBNLhDafhu0t1ZCx XrtshTd/cq2+Mpt8wDQlmCsBuqf4AuYhaWH3XkUnhesHM0/xrHsz2m1Nd//wKjLV i6Frqj0+VKaScJXofHA+9+KOaW0iEhzKCrV5hLbj+qHkIspuEBwSDrpUQuec6MgZ HY6M3CQXVbAabthjgDkrBK5slnrqI8OtRqQyfowF/dXn9qaQ3/PCUjJXGQYj8UD8 Kaq/S8Om7FfnNpngKIH9AsA1IGZ25JaXHNRCKvrrTcK4fso27Lb11zeVI/CqyJdw UvYjTGvC/6bycexV9fW7gaseonPEBOht3QhzbZ+sp54fAGa6hTGEOT/USYZpVnoO JkugDGsr9SAZH55T6znKZ7d2qDJ4nQ/dxn07eB6b0MZX51iakRU= =SNfM -----END PGP SIGNATURE----- --Sig_/P0wFCYhvudvg=8epL0WOEBR--