From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=NSF0=DQ=vger.kernel.org=linux-block-owner@kernel.org>
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=-4.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH,
	DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,
	SPF_PASS 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 A4F17C43457
	for <linux-block@archiver.kernel.org>; Fri,  9 Oct 2020 15:29:32 +0000 (UTC)
Received: from vger.kernel.org (vger.kernel.org [23.128.96.18])
	by mail.kernel.org (Postfix) with ESMTP id 6830B222D5
	for <linux-block@archiver.kernel.org>; Fri,  9 Oct 2020 15:29:32 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
	s=default; t=1602257372;
	bh=+a0QD0XOHMqpJMDLxqtDZCq4Dwlwyp9i1c41fzMX1OI=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From;
	b=Pc1eucEzn+T/RiJIinmQSmP9NH9KfqEL/b9GRnGfQKclnufPqAGyDdIzYXNgsuUH9
	 IGIIjad7U1ICW6HCy5vJb3IPdCtmOzaSfJY9djhysQ/WntvdtSyvGnSXhNHZieNpLU
	 flxoq8Ct8nPV5+mw2fmE/IaH41c0sBmuKfo2oY/o=
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S2389035AbgJIP3b (ORCPT <rfc822;linux-block@archiver.kernel.org>);
        Fri, 9 Oct 2020 11:29:31 -0400
Received: from mail.kernel.org ([198.145.29.99]:44064 "EHLO mail.kernel.org"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1732056AbgJIP3a (ORCPT <rfc822;linux-block@vger.kernel.org>);
        Fri, 9 Oct 2020 11:29:30 -0400
Received: from dhcp-10-100-145-180.wdl.wdc.com (unknown [199.255.45.60])
        (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
        (No client certificate requested)
        by mail.kernel.org (Postfix) with ESMTPSA id 6556F22261;
        Fri,  9 Oct 2020 15:29:29 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
        s=default; t=1602257370;
        bh=+a0QD0XOHMqpJMDLxqtDZCq4Dwlwyp9i1c41fzMX1OI=;
        h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
        b=WisCFbIltSHyFXLFhQO4rA5pwBjFv/nI+bjQ8ReG69XF0XaKek5yAsO40Yhn+GiVG
         nqNr4K9oEVOBYyADjiYWFr4LxShsVK5a8sOK5DyUC5K9HrFrNzXl9cxycpDtBRBGl/
         HDWTV3nJTzzP6RpdrhbXyKe207PlVvW7/JXd+s60=
Date:   Fri, 9 Oct 2020 08:29:27 -0700
From:   Keith Busch <kbusch@kernel.org>
To:     axboe@kernel.dk
Cc:     linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
        linux-scsi@vger.kernel.org, hch@lst.de, linux-api@vger.kernel.org,
        Niklas Cassel <niklas.cassel@wdc.com>,
        Damien Le Moal <damien.lemoal@wdc.com>,
        Johannes Thumshirn <johannes.thumshirn@wdc.com>,
        "Martin K . Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCHv4 1/3] block: add zone specific block statuses
Message-ID: <20201009152927.GA1023921@dhcp-10-100-145-180.wdl.wdc.com>
References: <20200924205330.4043232-1-kbusch@kernel.org>
 <20200924205330.4043232-2-kbusch@kernel.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200924205330.4043232-2-kbusch@kernel.org>
Precedence: bulk
List-ID: <linux-block.vger.kernel.org>
X-Mailing-List: linux-block@vger.kernel.org

On Thu, Sep 24, 2020 at 01:53:28PM -0700, Keith Busch wrote:
> A zoned device with limited resources to open or activate zones may
> return an error when the host exceeds those limits. The same command may
> be successful if retried later, but the host needs to wait for specific
> zone states before it should expect a retry to succeed. Have the block
> layer provide an appropriate status for these conditions so applications
> can distinuguish this error for special handling.

Hi Jens,

Can be considered for inclusion? The series still applies cleanly to
block for-next.