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 X-Spam-Level: X-Spam-Status: No, score=-5.2 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E64EAC433ED for ; Fri, 2 Apr 2021 17:16:53 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id B48C361151 for ; Fri, 2 Apr 2021 17:16:53 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235746AbhDBRQx (ORCPT ); Fri, 2 Apr 2021 13:16:53 -0400 Received: from verein.lst.de ([213.95.11.211]:44403 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234759AbhDBRQw (ORCPT ); Fri, 2 Apr 2021 13:16:52 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id 7601268BEB; Fri, 2 Apr 2021 19:16:48 +0200 (CEST) Date: Fri, 2 Apr 2021 19:16:48 +0200 From: Christoph Hellwig To: Niklas Cassel Cc: Keith Busch , Jens Axboe , Christoph Hellwig , Sagi Grimberg , "minwoo.im.dev@gmail.com" , "javier@javigon.com" , "linux-nvme@lists.infradead.org" , "linux-kernel@vger.kernel.org" Subject: Re: [RFC PATCH] nvme: allow NVME_IOCTL_IO_CMD on controller char dev even when multiple ns Message-ID: <20210402171648.GA22651@lst.de> References: <20210326205943.431185-1-Niklas.Cassel@wdc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210326205943.431185-1-Niklas.Cassel@wdc.com> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Well, there is at least one good reason for not allowing this retroactively: Old users of the ioctl could have complete garbage in the field, and might send the command to a random namespace now instead of the first one. So unles we have a very good reason I think we should keep NVME_IOCTL_IO_CMD on the controller char dev deprecated and maybe eventually remove it.