Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: G6vT32osA0Q/ofMatKuW9b9NnA92bU8+1HXqTzg4fQcEYPvgKi/HVl2LI7wH8HSO4ac1jysNQ5
 TC3HI4bHIHdup8cTDSgFRh8R36BZxv9iQ0zBPA44dTGKufu525Y3hcqDafJFnDKfeCXTvnXFJ7
 DoRc7XmhJsBVOxvm5dyK5pFszUMEXRYWmoUd9k+HhtCSCiomV9pNsN8K37dcL6EcLj5F6C8WtG
 kuArSh4HIYianLGIBeXkjiYhKnB8Z+T1PVl5ksA1dFEjYli7ZjqzKzDrePjh3KMZk8tcaXvTNk
 nAI=
From:   Niklas Cassel <Niklas.Cassel@wdc.com>
To:     Kanchan Joshi <joshiiitr@gmail.com>
CC:     Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@fb.com>,
        Christoph Hellwig <hch@lst.de>,
        Sagi Grimberg <sagi@grimberg.me>,
        "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Revert "nvme: cleanup zone information initialization"
Thread-Topic: [PATCH] Revert "nvme: cleanup zone information initialization"
Thread-Index: AQHXFAe/O1qthbSdYkihoP//+y7iVap6SRaAgAAFYoA=
Date:   Mon, 8 Mar 2021 16:51:22 +0000
Message-ID: <YEZWCUBvbh11Z7yJ@localhost.localdomain>
References: <20210308104226.165814-1-niklas.cassel@wdc.com>
 <CA+1E3rLY_FrjhXSFr4_V0OEiv6uFnD4bvY-XLyi9O4C3n_0CGA@mail.gmail.com>
In-Reply-To: <CA+1E3rLY_FrjhXSFr4_V0OEiv6uFnD4bvY-XLyi9O4C3n_0CGA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
wdcipoutbound: EOP-TRUE
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7434A807933FE74C86BD3BE521F1CDB4@namprd04.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: c6da0267-3eab-4413-76ae-08d8e252678a
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Mar 2021 16:51:22.4488
 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: b61c8803-16f3-4c35-9b17-6f65f441df86
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: naQXiRobAQaRzFvFHZTuAiYl0ucaksgRJomRJSENNTdJlY4q8Y+YF3wLT2XZzRnK6LMH2VMVOLsHO0di41x80g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR04MB4122
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Mon, Mar 08, 2021 at 10:02:05PM +0530, Kanchan Joshi wrote:
> On Mon, Mar 8, 2021 at 4:21 PM Niklas Cassel <Niklas.Cassel@wdc.com> wrot=
e:
> >
> > From: Niklas Cassel <niklas.cassel@wdc.com>
> >
> > This reverts commit 73d90386b559d6f4c3c5db5e6bb1b68aae8fd3e7.
> >
> > Commit 73d90386b559 ("nvme: cleanup zone information initialization")
> > introduced the following warning at boot:
> > WARNING: CPU: 0 PID: 7 at block/blk-settings.c:252 blk_queue_max_zone_a=
ppend_sectors+0x7d/0x90
> >
> > The warning is the result of chunk_sectors being 0.
>=20
> This looks same as what Chaitanya posted the fix for -
> https://lore.kernel.org/linux-nvme/20210303224717.51633-1-chaitanya.kulka=
rni@wdc.com/

Hello Kanchan,

Indeed, thanks for telling me.

Kind regards,
Niklas=