Received: by 2002:a05:6358:c692:b0:131:369:b2a3 with SMTP id fe18csp5569464rwb; Tue, 1 Aug 2023 05:00:39 -0700 (PDT) X-Google-Smtp-Source: APBJJlGq7/2khHXH7afDHgwHvkQVz1Fid/fJ7rMdV2Co160beImfr9uBVjibPAB0j+s4Mca6Iv1+ X-Received: by 2002:a05:6a20:8f06:b0:13e:b6b0:72a2 with SMTP id b6-20020a056a208f0600b0013eb6b072a2mr436632pzk.6.1690891239399; Tue, 01 Aug 2023 05:00:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1690891239; cv=none; d=google.com; s=arc-20160816; b=ivLgO/9Db0rUVnLnwDBgIV1ORN4hidiRhtBj2B8qnosLi2F8pgBZkIxXy+9ZEhGhug 4Fn4wwEXc7GCv9LUoc6VLkyVYep9faFAPOOzpnZ/csz4EHXibY+PrFnaRrw9earoELtc MFZg9QcRBKjXS7OsLgAtLHlu7xMSTB1R1KYMTIApqU4GBGp/jaDeK5LT8al7x/c8sova MnZuhlAya+67VDtxSTC0+o6UaNAnEm7y7iiP5S+ero5w7HIWCzOTUe1evfrCAeO5X3/F NX7j2r2GMu/ePn0jQtjAeAxmoUo9u/GHDxslcnhCNnflU6O68Oh76UKj3BA6kbIKs7KQ HkHQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=OrKLmIm8rSN6fQb3wTpyM7s13FV47whzXvai8eweME4=; fh=cil3qQ+YX9IGLhgkzZ7lR/Chotnh7rPKJmhg+1X8J90=; b=jF/UoDNkMvjVUGEANKg7T+hmUJYWG+s8MvtMY7vuALlQP2dGpebEoa1Ct9u9YeYKJ2 MbG01sb5vJhF6FULemXtf41UiElxqrCrIWM18CdrAxNimg6A78DdhbCG+KsEziaHIHP0 3ybBZ9a6cQULUGhq+N+L7EFKnFc6SwnpBN2tO+uSkHItmloImTQXpd4anGagA2z995Im Ev+akNPcG4n9bjCNjiSDHKo+dJbT0xpN3Vp3pFRCGb41fK2cKQzLzp9wToT97P9TUWAz BZ4RnID8526BfYJd3uPCL+HN7+uflK69te83bA1exK+W6yOl7y7ckViQxsVUVIyq48pE LuTg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id w67-20020a636246000000b005638ffaa993si7477046pgb.4.2023.08.01.05.00.23; Tue, 01 Aug 2023 05:00:39 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233807AbjHALZL (ORCPT + 99 others); Tue, 1 Aug 2023 07:25:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56278 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231862AbjHALY5 (ORCPT ); Tue, 1 Aug 2023 07:24:57 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D91F53AA6 for ; Tue, 1 Aug 2023 04:24:12 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id B64B76732D; Tue, 1 Aug 2023 13:24:03 +0200 (CEST) Date: Tue, 1 Aug 2023 13:24:03 +0200 From: Christoph Hellwig To: "Limonciello, Mario" Cc: Christoph Hellwig , August Wikerfors , Keith Busch , axboe@fb.com, sagi@grimberg.me, linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org, nilskruse97@gmail.com, David.Chang@amd.com Subject: Re: [PATCH] nvme: Don't fail to resume if NSIDs change Message-ID: <20230801112403.GA3972@lst.de> References: <20230731185103.18436-1-mario.limonciello@amd.com> <040c5788-1a7b-26ea-23cc-ba239c76efa9@augustwikerfors.se> <39697f68-9dc8-7692-7210-b75cce32c6ce@amd.com> <20230731201047.GA14034@lst.de> <36319a0f-34a6-9353-bc52-4d4d0fac27a5@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <36319a0f-34a6-9353-bc52-4d4d0fac27a5@amd.com> User-Agent: Mutt/1.5.17 (2007-11-01) X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, RCVD_IN_DNSWL_BLOCKED,SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 31, 2023 at 03:14:54PM -0500, Limonciello, Mario wrote: >> No. There are tons of NVMe devices that only support creating and >> deleting namespace out of band, especially in virtualized and cloud >> setups. > > Even if it's only the error handling path only that it's checked? Do you mean nvme_validate_ns with the error code? I wouldn't really call that an error case, that's the function called to check namespaces are still the same after we did a rescan (either manually or triggered by the AEN). > If you don't want more changes or heuristics on the error handling path for > this case, I think the best solution is probably to pick up > > https://lore.kernel.org/all/20221116171727.4083-1-git@augustwikerfors.se/t/ > > instead then and hopefully we don't end up with more disks like this. That's probably the better idea. I know at least one of the early quirked devices also IDs that changed for subsequent identify calls.