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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 6913ECD98F3 for ; Wed, 11 Oct 2023 06:36:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344710AbjJKGgW (ORCPT ); Wed, 11 Oct 2023 02:36:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39356 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1345438AbjJKGgV (ORCPT ); Wed, 11 Oct 2023 02:36:21 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 64081D3 for ; Tue, 10 Oct 2023 23:36:19 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 779CA6732A; Wed, 11 Oct 2023 08:36:15 +0200 (CEST) Date: Wed, 11 Oct 2023 08:36:15 +0200 From: Christoph Hellwig To: Kanchan Joshi Cc: Christoph Hellwig , Kanchan Joshi , kbusch@kernel.org, axboe@kernel.dk, sagi@grimberg.me, linux-nvme@lists.infradead.org, vincentfu@gmail.com, ankit.kumar@samsung.com, cpgs@samsung.com, stable@vger.kernel.org, Vincent Fu Subject: Re: [PATCH v3] nvme: fix memory corruption for passthrough metadata Message-ID: <20231011063615.GA2323@lst.de> References: <1891546521.01696823881551.JavaMail.epsvc@epcpadp4> <20231010074634.GA6514@lst.de> <20231011050254.GA32444@lst.de> <1296674576.21697005984297.JavaMail.epsvc@epcpadp4> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1296674576.21697005984297.JavaMail.epsvc@epcpadp4> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org On Wed, Oct 11, 2023 at 10:56:44AM +0530, Kanchan Joshi wrote: > > Fixing just a subset of these problems is pointless. If people want > > to use metadata on vendor specific commands they need to work with > > NVMe to figure out a generic way to pass the length. > > Do you suggest that vendor specific opcodes should be blocked here? We have to block everything that we can't calculate the length for. Otherwise you still leave the hole open.