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 1880FC74A5B for ; Thu, 30 Mar 2023 02:27:40 +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=nkRRyKCGWjBk8Mz1fC5DMSyOPz+ftJeqWRA6ily3Ggk=; b=YAcWXTWUR5VYDeD1uGCL5HxO0l HBVajWu+nDazByOVk9sAjGbBoCfGkstI9JtTTL9tv+xZ9LPematzxWs+c2c3cAMErpoKMCfEIpyAn VNd3h/Cv40qQAn8gtKY5YwPYMoa+sLwiLOk9iI+yNeHIPxGNQS9jfvUvBSxB8h0lBbkkJ4kul4A9K gfOurpYlWu+7jnXHJJ6KcaLtOD1i8AGRFKKbi7f+JH8wViTm94jKqT62vMsGzAdEIYJV/vqX6jhvD J/c+z8Z5vSAexONctiWcR7hWO+BDNMg84E2/OhLV8VA9T7I9v9SfsiWpX9c4fboCsOAW4qJyV/Xie 69sROXog==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1phi0m-002Lis-2F; Thu, 30 Mar 2023 02:27:36 +0000 Received: from verein.lst.de ([213.95.11.211]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1phi0k-002Lhw-02 for linux-nvme@lists.infradead.org; Thu, 30 Mar 2023 02:27:35 +0000 Received: by verein.lst.de (Postfix, from userid 2407) id 2E08668C7B; Thu, 30 Mar 2023 04:27:28 +0200 (CEST) Date: Thu, 30 Mar 2023 04:27:28 +0200 From: Christoph Hellwig To: zhangyanjun@cestc.cn Cc: sagi@grimberg.me, hch@lst.de, kbusch@kernel.org, Chaitanya.Kulkarni@wdc.com, hare@suse.de, linux-nvme@lists.infradead.org, Yanjun Zhang Subject: Re: [PATCH v3] nvme-tcp: fix a possible UAF when failing to allocate an io queue Message-ID: <20230330022728.GA4660@lst.de> References: <20230329062353.156283-1-zhangyanjun@cestc.cn> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230329062353.156283-1-zhangyanjun@cestc.cn> User-Agent: Mutt/1.5.17 (2007-11-01) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20230329_192734_191864_8EC3CA26 X-CRM114-Status: UNSURE ( 8.26 ) 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 Thanks, I've added this to nvme-6.3.