Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp215888ybz; Tue, 21 Apr 2020 19:05:30 -0700 (PDT) X-Google-Smtp-Source: APiQypLxq+XCfRRJHURvIaFxruY5GlL4/HYlxh8T6BH79gQaSlrSoWv84hpal0xG3fQoO8Jr2t8F X-Received: by 2002:a17:906:6944:: with SMTP id c4mr24189751ejs.96.1587521130789; Tue, 21 Apr 2020 19:05:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587521130; cv=none; d=google.com; s=arc-20160816; b=RZZ0rlKmoEGLYM1ZP1cQWuvFSPLujbTUUXk5zuIGy3wiLHt1I3KZGve3VssoVfaV2/ +V0UxV2uuccj73gBNZWvxw8ZOZz/Z0PLXGngxhkRtFuxyQBie0c6qw+o4kCj2elv5vvY Rzi91kpbDBP+Pe4uXG5sJ0oiWF09WNaFcMIxFXacSF/He1jCP3TmuhSML4X5ZryLBRF1 NyTsQj2XQOc+h6Wb6ZRXOBXeIyCuNlTvIR/jzG+pr8JhyoLQZzjkWTOKjCJaunhi7S3u EK6tGK8Yq0PWKos+o5p7uIJAGYCZQaOs878ipBpQxQYmf3F9lGlr5dMyoOwsMQmbq1ux KVDg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=EgRJrbHiIYx7tqQv75AnFSUU4SNz3Vc//pk52VU28Sc=; b=MWkatNOLFBBct1UCvM9KDw9RrRBfE+o+Vjv1HLzoEIqd1BwEVLToZGIvXcN6Q+0cVm Zj/wFtWTG713oo1nEpxGwHtZorT6lcE+xnWRdyJ6NsyaCaWvnTW71rTVW+noOnDlK0c5 fXQ1RiWnikON+njSCv5tDxzb6OZV0YEh8DCc1qkZb7eaLwjpWLJjR3YNErnQt3n7qSas IvtEAQ7kwKAZntFHIBetblRTfpjba5dZGVtIzM9tsq7oA89994Co/Lb/THkYMWwRA+PW K38/JKBQk10Ht8Xqhc/HV1/K/96FBohi11x3prJvCemZmxxD8oOsrA1zaxga9elOzH2W 4oQw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b="bo/DkEG6"; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dk4si2541134ejb.529.2020.04.21.19.05.07; Tue, 21 Apr 2020 19:05:30 -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=pass header.i=@redhat.com header.s=mimecast20190719 header.b="bo/DkEG6"; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726363AbgDVCCC (ORCPT + 99 others); Tue, 21 Apr 2020 22:02:02 -0400 Received: from us-smtp-1.mimecast.com ([207.211.31.81]:43461 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726024AbgDVCCC (ORCPT ); Tue, 21 Apr 2020 22:02:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1587520920; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=EgRJrbHiIYx7tqQv75AnFSUU4SNz3Vc//pk52VU28Sc=; b=bo/DkEG6UwYYMymXMIShwnNN4F4PeFxTH4rS1C1hPgSc6XxtTIo3MtQFBfkNhT0fe4wADM fa/KNCrnY5LI/S8RP3Kn+H9ruhBpd9aAcRhCt/dEu9x8knIMBBPznIPCscrlIxEPVDzQhH kGuM2/qPDAFLTMDJ+ZyT7SqahLmY2+k= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-157-w_qjtyPLMe2kyULFcRKRCA-1; Tue, 21 Apr 2020 22:01:56 -0400 X-MC-Unique: w_qjtyPLMe2kyULFcRKRCA-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 840088024D4; Wed, 22 Apr 2020 02:01:53 +0000 (UTC) Received: from T590 (ovpn-8-28.pek2.redhat.com [10.72.8.28]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 5E28926578; Wed, 22 Apr 2020 02:01:39 +0000 (UTC) Date: Wed, 22 Apr 2020 10:01:34 +0800 From: Ming Lei To: Dexuan Cui , "Paul E. McKenney" , Josh Triplett , "Rafael J. Wysocki" Cc: "jejb@linux.ibm.com" , "martin.petersen@oracle.com" , "linux-scsi@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "hch@lst.de" , "bvanassche@acm.org" , "hare@suse.de" , Michael Kelley , Long Li , "linux-hyperv@vger.kernel.org" , "wei.liu@kernel.org" , Stephen Hemminger , Haiyang Zhang , KY Srinivasan , linux-pm@vger.kernel.org Subject: Re: [PATCH] scsi: storvsc: Fix a panic in the hibernation procedure Message-ID: <20200422020134.GC299948@T590> References: <1587514644-47058-1-git-send-email-decui@microsoft.com> <20200422012814.GB299948@T590> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Scanned-By: MIMEDefang 2.84 on 10.5.11.23 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 22, 2020 at 01:48:25AM +0000, Dexuan Cui wrote: > > From: Ming Lei > > Sent: Tuesday, April 21, 2020 6:28 PM > > To: Dexuan Cui > > > > On Tue, Apr 21, 2020 at 05:17:24PM -0700, Dexuan Cui wrote: > > > During hibernation, the sdevs are suspended automatically in > > > drivers/scsi/scsi_pm.c before storvsc_suspend(), so after > > > storvsc_suspend(), there is no disk I/O from the file systems, but there > > > can still be disk I/O from the kernel space, e.g. disk_check_events() -> > > > sr_block_check_events() -> cdrom_check_events() can still submit I/O > > > to the storvsc driver, which causes a paic of NULL pointer dereference, > > > since storvsc has closed the vmbus channel in storvsc_suspend(): refer > > > to the below links for more info: > > > > > > Fix the panic by blocking/unblocking all the I/O queues properly. > > > > > > Note: this patch depends on another patch "scsi: core: Allow the state > > > change from SDEV_QUIESCE to SDEV_BLOCK" (refer to the second link > > above). > > > > > > Fixes: 56fb10585934 ("scsi: storvsc: Add the support of hibernation") > > > Signed-off-by: Dexuan Cui > > > --- > > > drivers/scsi/storvsc_drv.c | 10 ++++++++++ > > > 1 file changed, 10 insertions(+) > > > > > > diff --git a/drivers/scsi/storvsc_drv.c b/drivers/scsi/storvsc_drv.c > > > index fb41636519ee..fd51d2f03778 100644 > > > --- a/drivers/scsi/storvsc_drv.c > > > +++ b/drivers/scsi/storvsc_drv.c > > > @@ -1948,6 +1948,11 @@ static int storvsc_suspend(struct hv_device > > *hv_dev) > > > struct storvsc_device *stor_device = hv_get_drvdata(hv_dev); > > > struct Scsi_Host *host = stor_device->host; > > > struct hv_host_device *host_dev = shost_priv(host); > > > + int ret; > > > + > > > + ret = scsi_host_block(host); > > > + if (ret) > > > + return ret; > > > > > > storvsc_wait_to_drain(stor_device); > > > > > > @@ -1968,10 +1973,15 @@ static int storvsc_suspend(struct hv_device > > *hv_dev) > > > > > > static int storvsc_resume(struct hv_device *hv_dev) > > > { > > > + struct storvsc_device *stor_device = hv_get_drvdata(hv_dev); > > > + struct Scsi_Host *host = stor_device->host; > > > int ret; > > > > > > ret = storvsc_connect_to_vsp(hv_dev, storvsc_ringbuffer_size, > > > hv_dev_is_fc(hv_dev)); > > > + if (!ret) > > > + ret = scsi_host_unblock(host, SDEV_RUNNING); > > > + > > > return ret; > > > } > > > > scsi_host_block() is actually too heavy for just avoiding > > scsi internal command, which can be done simply by one atomic > > variable. > > > > Not mention scsi_host_block() is implemented too clumsy because > > nr_luns * synchronize_rcu() are required in scsi_host_block(), > > which should have been optimized to just one. > > > > Also scsi_device_quiesce() is heavy too, still takes 2 > > synchronize_rcu() for one LUN. > > > > That is said SCSI suspend may take (3 * nr_luns) sysnchronize_rcu() in > > case that the HBA's suspend handler needs scsi_host_block(). > > > > Thanks, > > Ming > > When we're in storvsc_suspend(), all the userspace processes have been > frozen and all the file systems have been flushed, and there should not > be too much I/O from the kernel space, so IMO scsi_host_block() should be > pretty fast here. I guess it depends on RCU's implementation, so CC RCU guys. Hello Paul & Josh, Could you clarify that if sysnchronize_rcu becomes quickly during system suspend? Thanks, Ming