Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp4267960pxv; Tue, 29 Jun 2021 03:03:12 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxuAmMczVh30556kUQIonFwYDaCAeFAGUaf3piCj+XkzFmQAUnWVSKxEs30+I2gxpUaBIMH X-Received: by 2002:a17:906:49ce:: with SMTP id w14mr29342232ejv.273.1624960992100; Tue, 29 Jun 2021 03:03:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624960992; cv=none; d=google.com; s=arc-20160816; b=0s1KArprbnavVXIxUhGrrv/DnK2NTysnK38SdqQH5EyQ/wyQBUFYFuBR79k11IkyBM ib01b1oyEd3StfXVe2dgnn2tSKzO+w0kgMI3Z2pbtEiQVNoWeNQz/cpQuRSUSw7o/986 Oi9aofWdD55XYC0ts+vpt10skS1oL8PurUzfV64VmcFAV37+RrzafJfPwgL2rNnzGq92 ZRJ3kPOkc4IS1F/7T3rt7tWU+o9FGrjoOL6lVp+q/rzC6nvIj6rzZHq19drwQxg45+Dw 0kLjSOuWG5+EivJgFxBvG3Peado+joSH9vsGl9FYbe4R3F8G5/2ZtkedLceh2OH85zqg nMlA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=hzJ7KD+FefvY+PA5Kqxiz47KxgMjEOLWX6jpOn12NMs=; b=plborG6yGCGOD9KfCU2o/8CiUUVCLHGlv8TW/2XTNIG5oJzxVdcSZFcCuWy8j84i3H hBi+7KCRq8RVltzEZmOjTRrCmbK13ul1x7q+Y0SA0/Vgbox3HXvrzNp2fxmcvWMuFmKh 8HpBK89c8qkWBIJzmjhNTnTwG1c/bM2CbcHuE4L4inGQiJHESry9ww2J1VnqcP54/3QO 4EVVSrPOf3DP7ExZQINHaXdbF4nMBGKvPLmSx49GZTiisFmgiLHpn7szRF0EmZzrNEMM AVWHAcvAzlvgrv5FRXmmmayliWF3lQR0c/Ny7dI8j9DI+uJEYl6NrebXofGxnmx0Vr3V zcJA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=GWbEGsst; 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 hz7si11143842ejc.673.2021.06.29.03.02.47; Tue, 29 Jun 2021 03:03:12 -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=GWbEGsst; 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 S232796AbhF2Jie (ORCPT + 99 others); Tue, 29 Jun 2021 05:38:34 -0400 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:24039 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232614AbhF2Jid (ORCPT ); Tue, 29 Jun 2021 05:38:33 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1624959366; 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=hzJ7KD+FefvY+PA5Kqxiz47KxgMjEOLWX6jpOn12NMs=; b=GWbEGsst04hM4yEW5Z6ehk555m6wGFMv3nqE4pgEAKVdkXwYgKqrrTyCNYVz1rwzFZo3HM DW6r9R1QoFOqqFKOx2VEqsxqT45h6cRvf/+m2zVauzQgQTurThNqrZF4CtDcypPo9usyvc EZk5PBwZWpzILp2TxMwNy15dhzwWzt0= 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-300-l4KEPThVPf-MeR8oJmQ4gA-1; Tue, 29 Jun 2021 05:36:04 -0400 X-MC-Unique: l4KEPThVPf-MeR8oJmQ4gA-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 05BB6800D62; Tue, 29 Jun 2021 09:36:03 +0000 (UTC) Received: from T590 (ovpn-13-8.pek2.redhat.com [10.72.13.8]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 314C260C0F; Tue, 29 Jun 2021 09:35:55 +0000 (UTC) Date: Tue, 29 Jun 2021 17:35:51 +0800 From: Ming Lei To: Daniel Wagner Cc: Wen Xiong , james.smart@broadcom.com, linux-kernel@vger.kernel.org, sagi@grimberg.me, wenxiong@linux.vnet.ibm.com Subject: Re: [PATCH 1/1] block: System crashes when cpu hotplug + bouncing port Message-ID: References: <20210628090703.apaowrsazl53lza4@beryllium.lan> <71d1ce491ed5056bfa921f0e14fa646d@imap.linux.ibm.com> <20210629082542.vm3yh6k36d2zh3k5@beryllium.lan> <20210629083549.unco3f7atybqypw3@beryllium.lan> <20210629092719.n33t2pnjiwwe6qun@beryllium.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210629092719.n33t2pnjiwwe6qun@beryllium.lan> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.12 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 29, 2021 at 11:27:19AM +0200, Daniel Wagner wrote: > On Tue, Jun 29, 2021 at 05:01:16PM +0800, Ming Lei wrote: > > No, this way fails the request allocation, which isn't expected from > > NVMe fc/rdma/tcp/loop, since io queue can't be connected in this way. > > But __nvme_submit_sync_cmd() can return errors too and they need to be > handled in the connect path. So why is this so special? Not that I am > against your patch, I just like to understand the reasoning. With the two patches I posted, __nvme_submit_sync_cmd() shouldn't return error, can you observe the error? Thanks, Ming