Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp1799443pxa; Sun, 2 Aug 2020 22:06:56 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwzP0OxW1vJtCFrts4cZ8kTQAE2QlRNmoF0seMZys+ll2xfS+3tgWUuwpoZx/EWApowY8nP X-Received: by 2002:a17:906:7e57:: with SMTP id z23mr14730049ejr.294.1596431215936; Sun, 02 Aug 2020 22:06:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1596431215; cv=none; d=google.com; s=arc-20160816; b=L2YhHBz82w/tdnaGkyJ65t1IDtGgsy1GjL0gC2m3YAwfVs5JVwItALXpCP3iohZr1Y KdnA67TIe/n8p4lNDxxi/IWe5FpWtmd8mIGCTYCiA4TnttUc6QGRh8z9bHr5+EsXVkz0 zVJzzYzdSQpP53FpguKBsVkDrNln+VSN/kLuEmMXW/0dKD3peGQmpkfpiMqwi0U+27jt aUuQj25xCyVE71zoqiuJa/Bm3qGlYcPbMmRQOUG1vnC4dGOl1wH2Wx9dMjNP0ENeIWgR +WJH9lSyBANZTuE9kXJz4f3SOHEfWBqA7x6vci8WYtn8pQjSZOPVpLEnJeS7NW+u7H2Y d4SA== 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=ZEq3dQL1T4rfyaJOBFm/8UoCpiFNlnou1J2+YfKngHo=; b=Zxu0oXGLcVJhHUIoI46qNhmmpxjg5QH8N5p5Mm9A1NgZSS4abIJvMKX9dd2CYU5XMQ DFSUSyp4QqlmNW/qD67jJwvHpsjjZMkO2mJQy3gnqXJg98nhqw+6miPB8Fji9MARAUM4 X6uUx/z8lWhtZl3/goFPbfXy2QTsexa187O98uDtSutyG4i3iRSQsvrQBVcS+H8yCW5i 48r2UzVlUJgDUhP6o8FEGOHv/JDnjuBrzJHpz/XTiQdzTHGnXz0ToyaleUpp7+5NFzNn x+NRnRBczmuLasoO37Rm5RRtzd+s9mDrtIlRsKhm9UNC/CjbDOg/ntWlb+DMG2CP5XXz OBow== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@mg.codeaurora.org header.s=smtp header.b=bS+QIwK0; 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 a11si3276886edk.332.2020.08.02.22.06.34; Sun, 02 Aug 2020 22:06:55 -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=bS+QIwK0; 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 S1726143AbgHCFDg (ORCPT + 99 others); Mon, 3 Aug 2020 01:03:36 -0400 Received: from m43-7.mailgun.net ([69.72.43.7]:54402 "EHLO m43-7.mailgun.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725268AbgHCFDg (ORCPT ); Mon, 3 Aug 2020 01:03:36 -0400 DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=mg.codeaurora.org; q=dns/txt; s=smtp; t=1596431015; h=Message-ID: References: In-Reply-To: Subject: Cc: To: From: Date: Content-Transfer-Encoding: Content-Type: MIME-Version: Sender; bh=ZEq3dQL1T4rfyaJOBFm/8UoCpiFNlnou1J2+YfKngHo=; b=bS+QIwK0a6Gh7x4/kG4K0MKjr3pC09lXiNa+E1muUSEnialacWeTpPOwOK8ohzkKrWlpTlt5 dc+DnTPj9OfpMMONcVUeY1zB12pZ82P/R2uI2EUo966+PBJ648zjyqZry0RVDQUtlYi9WWqY ZGnIsxeNTlAzOLNac4AA1/30k6k= 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-n11.prod.us-west-2.postgun.com with SMTP id 5f279a96498d6102394b66a2 (version=TLS1.2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256); Mon, 03 Aug 2020 05:03:18 GMT Received: by smtp.codeaurora.org (Postfix, from userid 1001) id 733C4C4339C; Mon, 3 Aug 2020 05:03:17 +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 198A3C433C6; Mon, 3 Aug 2020 05:03:16 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Mon, 03 Aug 2020 13:03:16 +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, jiajie.hao@mediatek.com Subject: Re: [PATCH v6] scsi: ufs: Quiesce all scsi devices before shutdown In-Reply-To: <20200803042514.7111-1-stanley.chu@mediatek.com> References: <20200803042514.7111-1-stanley.chu@mediatek.com> Message-ID: 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-08-03 12:25, 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, in ufshcd_shutdown(), > > 1. Use pm_runtime_get_sync() instead of resuming UFS device by > ufshcd_runtime_resume() "internally" to let runtime PM framework > manage and prevent concurrent runtime operations by incoming I/O > requests. > > 2. Specifically quiesce all SCSI devices to block all I/O requests > after device is resumed. > > 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) > > 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 > --- > Changes: > - Since v4: Use pm_runtime_get_sync() instead of resuming UFS device > by ufshcd_runtime_resume() "internally". > --- > drivers/scsi/ufs/ufshcd.c | 39 ++++++++++++++++++++++++++++++++++----- > 1 file changed, 34 insertions(+), 5 deletions(-) > > diff --git a/drivers/scsi/ufs/ufshcd.c b/drivers/scsi/ufs/ufshcd.c > index 307622284239..fc01171d13b1 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) > { > @@ -8629,6 +8635,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 */ Why can runtime suspended sdevs be skipped? Block layer can still resume them at any time, no? > + if (!pm_runtime_suspended(&sdev->sdev_gendev)) > + scsi_device_quiesce(sdev); > +} > + > /** > * ufshcd_shutdown - shutdown routine > * @hba: per adapter instance > @@ -8640,6 +8653,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; > @@ -8647,11 +8661,26 @@ int ufshcd_shutdown(struct ufs_hba *hba) > if (ufshcd_is_ufs_dev_poweroff(hba) && ufshcd_is_link_off(hba)) > goto out; > > - if (pm_runtime_suspended(hba->dev)) { > - ret = ufshcd_runtime_resume(hba); > - if (ret) > - goto out; > - } > + /* > + * Let runtime PM framework manage and prevent concurrent runtime > + * operations with shutdown flow. > + */ > + pm_runtime_get_sync(hba->dev); > + > + /* > + * 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); Any reasons why don't use scsi_target_quiesce() here? Thanks, Can Guo. > > ret = ufshcd_suspend(hba, UFS_SHUTDOWN_PM); > out: