Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp4249054pxv; Tue, 29 Jun 2021 02:31:03 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwYhl6qUEyBxk17NqUL+25IRfoIH0E6mywqfNK2LvOoakKrq9Nknj+lsNdGfJUBMzRORMwS X-Received: by 2002:a50:f0c1:: with SMTP id a1mr3453552edm.293.1624959062945; Tue, 29 Jun 2021 02:31:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624959062; cv=none; d=google.com; s=arc-20160816; b=t19EWTK9LnRE44I0efn+zk605uOJgvL2kIYCAjcFL6OUW7L9MLE3igAIXCp6MR/xZu T8BnUsbijhq20K6p0UJ8SOIhXGJrFs80iTZsmxu5lFxxaKOza9ckB74gbfOA3ARygIBx CGh9hnDWZtuVtw0Jr7lZIwfI0M3045GH85KMLy4bUijJf6inw4ZsKV7KxbnaDlZbFTQ7 EidlpOnngiRQ9KjEOnvTtVXe9KLEzJsqA2R29saF5AzjuepUbjvByJc3pm8ocbuK7sei dNew4ii58SkK4IGjRTVOpfy0xyxS93RB4shUABY95fXSIrh0AvpGWZ98dIItaSUnxEQ3 YgNA== 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 :dkim-signature:dkim-signature:dkim-signature; bh=K4q4LmD7SOlQLXLUrGAnOIJm9Fl0zLoCmgA3rdoB1z0=; b=cJGsj1ZHbShx6sNEuKpXDvhxBsfPkUGg8Alkm29iwDfVUqcKW9Ew9RcBWM4anYJ9Cq cuNMQaYZZutbZGHXpNG/WU1a3uq38lJPZCqrYN5kr73DKDsecyvoENhz3DQ1cfRCKVYV nLQLOBMxwk1M6DcN+9rTglGPYfWnaq+8kCwxU9vpS25mQj6YH4OiIIOmNnilM/OqBvSB 6BnodaUmgYQrdQYp9wX2yJpIfG/F2PJm09Pbz9Scs/O38B5U4948re8bc8xM15evsIaa rZTqaDntSmisWEBIbrpafcobEB75JcWAsGtrn5L4mpq2G2GnWd0mNKHDaO5i6RYrXrkU Kbnw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=q1u+jMWQ; dkim=neutral (no key) header.i=@suse.de header.s=susede2_ed25519 header.b="B/b29eDz"; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=q1u+jMWQ; dkim=neutral (no key) header.i=@suse.de header.b="B/b29eDz"; 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 w11si20074534ede.594.2021.06.29.02.30.39; Tue, 29 Jun 2021 02:31:02 -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=@suse.de header.s=susede2_rsa header.b=q1u+jMWQ; dkim=neutral (no key) header.i=@suse.de header.s=susede2_ed25519 header.b="B/b29eDz"; dkim=pass header.i=@suse.de header.s=susede2_rsa header.b=q1u+jMWQ; dkim=neutral (no key) header.i=@suse.de header.b="B/b29eDz"; 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 S232735AbhF2J3s (ORCPT + 99 others); Tue, 29 Jun 2021 05:29:48 -0400 Received: from smtp-out1.suse.de ([195.135.220.28]:43342 "EHLO smtp-out1.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232614AbhF2J3s (ORCPT ); Tue, 29 Jun 2021 05:29:48 -0400 Received: from imap.suse.de (imap-alt.suse-dmz.suse.de [192.168.254.47]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp-out1.suse.de (Postfix) with ESMTPS id 50C9F2265F; Tue, 29 Jun 2021 09:27:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1624958840; h=from:from:reply-to: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=K4q4LmD7SOlQLXLUrGAnOIJm9Fl0zLoCmgA3rdoB1z0=; b=q1u+jMWQ6NgqT1dtiAfWRKU3wKi95ikkm5CIwXjHJDentJ+D0S/3fY20d0rHWJR5r2op3b ZKJKWPxgdTcwe9yclmkzsrTopViIQ3fsAw9oPV08lk1117CAt9v1pLuP0DITkZCrRdAx+q Ws52nTS1hkvNtiGSYNEVcBHZsPO6HDU= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1624958840; h=from:from:reply-to: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=K4q4LmD7SOlQLXLUrGAnOIJm9Fl0zLoCmgA3rdoB1z0=; b=B/b29eDzS5RLMOjf4DSibfCir317dBtBRHNCpdc0DLq+BiK/3aHJJaG879nqgUyHoy5zBO y3eHyG04OksKW+Cw== Received: from imap3-int (imap-alt.suse-dmz.suse.de [192.168.254.47]) by imap.suse.de (Postfix) with ESMTP id 3764411906; Tue, 29 Jun 2021 09:27:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa; t=1624958840; h=from:from:reply-to: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=K4q4LmD7SOlQLXLUrGAnOIJm9Fl0zLoCmgA3rdoB1z0=; b=q1u+jMWQ6NgqT1dtiAfWRKU3wKi95ikkm5CIwXjHJDentJ+D0S/3fY20d0rHWJR5r2op3b ZKJKWPxgdTcwe9yclmkzsrTopViIQ3fsAw9oPV08lk1117CAt9v1pLuP0DITkZCrRdAx+q Ws52nTS1hkvNtiGSYNEVcBHZsPO6HDU= DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_ed25519; t=1624958840; h=from:from:reply-to: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=K4q4LmD7SOlQLXLUrGAnOIJm9Fl0zLoCmgA3rdoB1z0=; b=B/b29eDzS5RLMOjf4DSibfCir317dBtBRHNCpdc0DLq+BiK/3aHJJaG879nqgUyHoy5zBO y3eHyG04OksKW+Cw== Received: from director2.suse.de ([192.168.254.72]) by imap3-int with ESMTPSA id WJSGDHjn2mDKXgAALh3uQQ (envelope-from ); Tue, 29 Jun 2021 09:27:20 +0000 Date: Tue, 29 Jun 2021 11:27:19 +0200 From: Daniel Wagner To: Ming Lei 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: <20210629092719.n33t2pnjiwwe6qun@beryllium.lan> References: <1624850072-17776-1-git-send-email-wenxiong@linux.vnet.ibm.com> <20210628090703.apaowrsazl53lza4@beryllium.lan> <71d1ce491ed5056bfa921f0e14fa646d@imap.linux.ibm.com> <20210629082542.vm3yh6k36d2zh3k5@beryllium.lan> <20210629083549.unco3f7atybqypw3@beryllium.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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.