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,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,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 1004BC433E2 for ; Fri, 11 Sep 2020 06:10:32 +0000 (UTC) Received: from merlin.infradead.org (merlin.infradead.org [205.233.59.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 38B3D21D7E for ; Fri, 11 Sep 2020 06:10:31 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="sNhFp/P9" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 38B3D21D7E Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=lst.de Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-nvme-bounces+linux-nvme=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=merlin.20170209; h=Sender:Content-Transfer-Encoding: Content-Type:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References:Message-ID: Subject:To:From:Date:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=NJ8nQJwM+CMptvZob1UpgsfexQXibkQtCOyzh4fSboU=; b=sNhFp/P9k41QehZ/0mPC1mgqD lazdvIpdjEKGUmVTUMjK7Jvw8nbUpy/THXcsmDqxKUmR9nEtCpbodwozOiOz1Sf5M0FaiQz7gUAz+ VZ5Inytt/3FR9Yp4Cz1T78t5g/nSIStbek9GfPlWsKdWyFynf+sE/aU0q0lNtfD66QAav5kob5PBW Wp57gas59Y1R1cqZNLIQxBz4WXFGobDQAn84BcsezaqZH5eE9i2zJHhZ+6aW5lXEqed9GgVvKJ9v/ 8lWTfFD+a7DiWB/HB9CvaH2jbFPbcc4zmrYO0D7Or8E3HZIMZALgHQiWWfl7iJBncGE3WJXBwfjxB SG7WrD2wA==; Received: from localhost ([::1] helo=merlin.infradead.org) by merlin.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1kGcGS-0003lC-4x; Fri, 11 Sep 2020 06:10:28 +0000 Received: from verein.lst.de ([213.95.11.211]) by merlin.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1kGcGP-0003kR-Hm for linux-nvme@lists.infradead.org; Fri, 11 Sep 2020 06:10:26 +0000 Received: by verein.lst.de (Postfix, from userid 2407) id 1126D67373; Fri, 11 Sep 2020 08:10:23 +0200 (CEST) Date: Fri, 11 Sep 2020 08:10:22 +0200 From: Christoph Hellwig To: Damien Le Moal Subject: Re: [PATCH] nvme: translate zns errors to blk_status_t Message-ID: <20200911061022.GA21597@lst.de> References: <20200909203324.3356679-1-kbusch@kernel.org> <20200910052643.GA18283@lst.de> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: 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-20200911_021025_701959_16433692 X-CRM114-Status: GOOD ( 13.78 ) X-BeenThere: linux-nvme@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Keith Busch , Christoph Hellwig , "linux-nvme@lists.infradead.org" , "sagi@grimberg.me" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "Linux-nvme" Errors-To: linux-nvme-bounces+linux-nvme=archiver.kernel.org@lists.infradead.org On Thu, Sep 10, 2020 at 10:25:24PM +0000, Damien Le Moal wrote: > > I'm not sure this is the best idea, we probably need specific error codes > > if we want file systems to be aware of the limit. > > Do you mean something else than -EBUSY being returned to the user by the block > layer ? Or a different/specific BLK_STS_XXX code which translates into -EBUSY in > blk_status_to_errno() ? My primary aim is a different BLK_STS_ code. But given that I think that we should not map different BLK_STS_ codes to the same errno if we can avoid it, we should probably also use a different errno. _______________________________________________ Linux-nvme mailing list Linux-nvme@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-nvme