From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id C3FDDC79FB7 for ; Thu, 10 Sep 2026 05:25:20 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=bgDpYWgS2xbCUsNjkziCXA4+Ane3G2tbmdJJRlnK360=; b=P96PLlDIZIOElUmi+5rU5Tg1XP HPSSXAP3NSHgbLgrZ/div0A0FnbOxufD73KUmMqrAXztXXUvSLfoK7rwpkyIoQfFJcS5wdpajifHc SJOG73S8sm/7bYZS0m7+DSgtXCe/5Ovv1yeWtRo+HuCkHMAgPsg9riasLNlAW2oZTWJMpP6iLt423 9E5g9aB47OPTdNk2AwbJIV1pYKLB3s/aPpoqEfk0TfsIhCLDmQCzgw/kHw7cJeVp/WXL0cPkJGi93 ywKRq/cbYBEeY7ecA34c4ze3iGrodc9HAN4Tw5VyY4c6BZMt3Od7rDwPDS4bsepKNFFFRWvmb8J0j SlnAxG6A==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1x4XHi-0000000DR2G-0GLJ; Thu, 10 Sep 2026 05:25:18 +0000 Received: from verein.lst.de ([213.95.11.211]) by bombadil.infradead.org with esmtps (Exim 4.99.1 #2 (Red Hat Linux)) id 1x4XHa-0000000DR15-3YwD for linux-nvme@lists.infradead.org; Thu, 10 Sep 2026 05:25:12 +0000 Received: by verein.lst.de (Postfix, from userid 2407) id 2DA0668BFE; Thu, 10 Sep 2026 07:25:04 +0200 (CEST) Date: Thu, 10 Sep 2026 07:25:03 +0200 From: Christoph Hellwig To: Julian Sun Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me, kch@nvidia.com, armenx.baloyan@intel.com, james.p.freyensee@intel.com, ming.l@ssi.samsung.com, Runyu Xiao Subject: Re: [PATCH 1/2] nvmet: preserve device path on allocation failure. Message-ID: <20260910052503.GB27133@lst.de> References: <20260908033519.2721210-1-sunjunchao@bytedance.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260908033519.2721210-1-sunjunchao@bytedance.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.9.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20260909_222511_040340_EA0AB227 X-CRM114-Status: UNSURE ( 8.72 ) X-CRM114-Notice: Please train this message. X-BeenThere: linux-nvme@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "Linux-nvme" Errors-To: linux-nvme-bounces+linux-nvme=archiver.kernel.org@lists.infradead.org Can you coordinate this with the configfs path checking series from Runyu Xiao? That one had a few resends, so I'd like to get it in first.