Received: by 2002:a25:ca44:0:0:0:0:0 with SMTP id a65csp841240ybg; Mon, 27 Jul 2020 00:32:19 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy+0rtUIwVynmnJE38PIj12ui/fxWJBAYqCgYt/QOBZcYof3XC3ay8cfwhsgBn9Zs2NoKN9 X-Received: by 2002:a50:c044:: with SMTP id u4mr20977358edd.366.1595835138792; Mon, 27 Jul 2020 00:32:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1595835138; cv=none; d=google.com; s=arc-20160816; b=opHS4WxZHP6EuJLsKu5bh46K19T2ZV9Ea8TkTM/HbwNsHZc1tm3UCVMpI0YmAsOZRB yNJ0EkpltoE4A3cAFLUjhI4gGfRc/nxyJuAU6kuoHCMW2yHqT0xDf9+KCQM4ZIcN65g/ jVdpDCMzJ0/APCrIpiDJ66BFqrIrERo0HfrbYM8rsVwEEiI0J4ML7mR/8bgPHXXcV3r0 bZBmIavkXF2M8uWU+1qt+9Ov7zIpVLOyrPujSFbzyeADyMBJH4Ac41unSvRcCvfVne9R eK9QFej9mlY5KfB+R12dwA6R9Uksn2lh/W5vH9YlLylsy2kcoZmqhS4Qzq3JE+8Xcc2z CUKA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:message-id:references :in-reply-to:subject:cc:to:from:date:content-transfer-encoding :mime-version:dkim-signature; bh=CVDJovx8o6kxZAd7Siw03nCa0NOSEKdy2eVnCp0MImQ=; b=kX08lDUbUQI60G6DqCSE+ZKzZ+3TKKUNSz7EpTbeRHvm1w4rtmYhCLHafpKKFIDCWp Qp+KhPcCIo3eAsz4Groe0lPcsMWxloGUmAazNqyx3WvBsWWBmiva6B7OFNABs0I4AeVz qGoPlctgVTQczftRhH+JpaEyWfLZoYTx9ph/Htt6qN0Vn5LGzJrHCqeWw28/+GsyJznb 0/533XX2frAHybrS1eEheA/hLWssp7Cg1hs10jHgAGO0CK5AgfCJ7I7L5qlqSOe7HbKf Hf8au0v2AXExk7RxX7ZI87d3DeKJSKgpo5AonPkMnyxK/+wx8KIMn5Fwp52iXYOcbWgD j3PA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@mg.codeaurora.org header.s=smtp header.b=XrzxGc0k; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dg23si4049827edb.12.2020.07.27.00.31.56; Mon, 27 Jul 2020 00:32:18 -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; dkim=fail header.i=@mg.codeaurora.org header.s=smtp header.b=XrzxGc0k; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727014AbgG0Haf (ORCPT + 99 others); Mon, 27 Jul 2020 03:30:35 -0400 Received: from m43-7.mailgun.net ([69.72.43.7]:44078 "EHLO m43-7.mailgun.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726891AbgG0Hae (ORCPT ); Mon, 27 Jul 2020 03:30:34 -0400 DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=mg.codeaurora.org; q=dns/txt; s=smtp; t=1595835033; h=Message-ID: References: In-Reply-To: Subject: Cc: To: From: Date: Content-Transfer-Encoding: Content-Type: MIME-Version: Sender; bh=CVDJovx8o6kxZAd7Siw03nCa0NOSEKdy2eVnCp0MImQ=; b=XrzxGc0kcC0g0Mv1zBjQ5DoJKw6PaY1tiyc09i2+npig/PNNjCOjJrRyJElBP7ugPX76/loA lRBpAOgyv7R8moOziy/rvV58UhF9ZqtyZO/oOS55grd94LcI3BHMEtmaSnuC9swGWaARrl8L fJcpNBSpAfkdYANv65RgozVBBSE= X-Mailgun-Sending-Ip: 69.72.43.7 X-Mailgun-Sid: WyI0MWYwYSIsICJsaW51eC1rZXJuZWxAdmdlci5rZXJuZWwub3JnIiwgImJlOWU0YSJd Received: from smtp.codeaurora.org (ec2-35-166-182-171.us-west-2.compute.amazonaws.com [35.166.182.171]) by smtp-out-n14.prod.us-west-2.postgun.com with SMTP id 5f1e8284298a38b61655f804 (version=TLS1.2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256); Mon, 27 Jul 2020 07:30:12 GMT Received: by smtp.codeaurora.org (Postfix, from userid 1001) id 08794C43391; Mon, 27 Jul 2020 07:30:11 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-caf-mail-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=2.0 tests=ALL_TRUSTED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.codeaurora.org (localhost.localdomain [127.0.0.1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: cang) by smtp.codeaurora.org (Postfix) with ESMTPSA id CB45FC433C9; Mon, 27 Jul 2020 07:30:10 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 27 Jul 2020 15:30:10 +0800 From: Can Guo To: Stanley Chu Cc: linux-scsi@vger.kernel.org, martin.petersen@oracle.com, avri.altman@wdc.com, alim.akhtar@samsung.com, jejb@linux.ibm.com, bvanassche@acm.org, beanhuo@micron.com, asutoshd@codeaurora.org, matthias.bgg@gmail.com, linux-mediatek@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, kuohong.wang@mediatek.com, peter.wang@mediatek.com, chun-hung.wu@mediatek.com, andy.teng@mediatek.com, chaotian.jing@mediatek.com, cc.chou@mediatek.com Subject: Re: [PATCH v4] scsi: ufs: Quiesce all scsi devices before shutdown In-Reply-To: <20200724140140.18186-1-stanley.chu@mediatek.com> References: <20200724140140.18186-1-stanley.chu@mediatek.com> Message-ID: <84510fc12ada0de8284e6a689b7a2358@codeaurora.org> X-Sender: cang@codeaurora.org User-Agent: Roundcube Webmail/1.3.9 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Stanley, On 2020-07-24 22:01, Stanley Chu wrote: > Currently I/O request could be still submitted to UFS device while > UFS is working on shutdown flow. This may lead to racing as below > scenarios and finally system may crash due to unclocked register > accesses. > > To fix this kind of issues, specifically quiesce all SCSI devices > before UFS shutdown to block all I/O request sending from block > layer. > > Example of racing scenario: While UFS device is runtime-suspended > > Thread #1: Executing UFS shutdown flow, e.g., > ufshcd_suspend(UFS_SHUTDOWN_PM) > Thread #2: Executing runtime resume flow triggered by I/O request, > e.g., ufshcd_resume(UFS_RUNTIME_PM) > I don't quite get it, how can you prevent block layer PM from iniating hba runtime resume by quiescing the scsi devices? Block layer PM iniates hba async runtime resume in blk_queue_enter(). But quiescing the scsi devices can only prevent general I/O requests from passing through scsi_queue_rq() callback. Say hba is runtime suspended, if an I/O request to sda is sent from block layer (sda must be runtime suspended as well at this time), blk_queue_enter() initiates async runtime resume for sda. But since sda's parents are also runtime suspended, the RPM framework shall do runtime resume to the devices in the sequence hba->host->target->sda. In this case, ufshcd_resume() still runs concurrently, no? Thanks, Can Guo. > This breaks the assumption that UFS PM flows can not be running > concurrently and some unexpected racing behavior may happen. > > Signed-off-by: Stanley Chu > --- > drivers/scsi/ufs/ufshcd.c | 29 +++++++++++++++++++++++++++++ > 1 file changed, 29 insertions(+) > > diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c > index 9d180da77488..2e18596f3a8e 100644 > --- a/drivers/scsi/ufs/ufshcd.c > +++ b/drivers/scsi/ufs/ufshcd.c > @@ -159,6 +159,12 @@ struct ufs_pm_lvl_states ufs_pm_lvl_states[] = { > {UFS_POWERDOWN_PWR_MODE, UIC_LINK_OFF_STATE}, > }; > > +#define ufshcd_scsi_for_each_sdev(fn) \ > + list_for_each_entry(starget, &hba->host->__targets, siblings) { \ > + __starget_for_each_device(starget, NULL, \ > + fn); \ > + } > + > static inline enum ufs_dev_pwr_mode > ufs_get_pm_lvl_to_dev_pwr_mode(enum ufs_pm_level lvl) > { > @@ -8620,6 +8626,13 @@ int ufshcd_runtime_idle(struct ufs_hba *hba) > } > EXPORT_SYMBOL(ufshcd_runtime_idle); > > +static void ufshcd_quiesce_sdev(struct scsi_device *sdev, void *data) > +{ > + /* Suspended devices are already quiesced so can be skipped */ > + if (!pm_runtime_suspended(&sdev->sdev_gendev)) > + scsi_device_quiesce(sdev); > +} > + > /** > * ufshcd_shutdown - shutdown routine > * @hba: per adapter instance > @@ -8631,6 +8644,7 @@ EXPORT_SYMBOL(ufshcd_runtime_idle); > int ufshcd_shutdown(struct ufs_hba *hba) > { > int ret = 0; > + struct scsi_target *starget; > > if (!hba->is_powered) > goto out; > @@ -8644,6 +8658,21 @@ int ufshcd_shutdown(struct ufs_hba *hba) > goto out; > } > > + /* > + * Quiesce all SCSI devices to prevent any non-PM requests sending > + * from block layer during and after shutdown. > + * > + * Here we can not use blk_cleanup_queue() since PM requests > + * (with BLK_MQ_REQ_PREEMPT flag) are still required to be sent > + * through block layer. Therefore SCSI command queued after the > + * scsi_target_quiesce() call returned will block until > + * blk_cleanup_queue() is called. > + * > + * Besides, scsi_target_"un"quiesce (e.g., scsi_target_resume) can > + * be ignored since shutdown is one-way flow. > + */ > + ufshcd_scsi_for_each_sdev(ufshcd_quiesce_sdev); > + > ret = ufshcd_suspend(hba, UFS_SHUTDOWN_PM); > out: > if (ret)