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=-3.7 required=3.0 tests=BAYES_00,DATE_IN_PAST_03_06, 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 37F03C55179 for ; Wed, 28 Oct 2020 22:27:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id EB74720704 for ; Wed, 28 Oct 2020 22:27:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1733286AbgJ1W1d (ORCPT ); Wed, 28 Oct 2020 18:27:33 -0400 Received: from verein.lst.de ([213.95.11.211]:45305 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1733282AbgJ1W13 (ORCPT ); Wed, 28 Oct 2020 18:27:29 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id 0DC5D6736F; Wed, 28 Oct 2020 18:17:26 +0100 (CET) Date: Wed, 28 Oct 2020 18:17:26 +0100 From: Christoph Hellwig To: Jongpil Jung Cc: Keith Busch , Jens Axboe , Christoph Hellwig , Sagi Grimberg , linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org, gloria.tsai@ssstc.com, jongpil19.jung@samsung.com, jongheony.kim@samsung.com, dj54.sohn@samsung.com Subject: Re: [PATCH V3 1/1] nvme: Add quirk for LiteON CL1 devices running FW 220TQ,22001 Message-ID: <20201028171726.GA9897@lst.de> References: <20201028091421.GA667673@image-900X5T-900X5U> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20201028091421.GA667673@image-900X5T-900X5U> User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Oct 28, 2020 at 06:14:21PM +0900, Jongpil Jung wrote: > LiteON(SSSTC) CL1 device running FW 220TQ,22001 has bugs with simple > suspend. > > When NVMe device receive D3hot from host, NVMe firmware will do > garbage collection. While NVMe device do Garbage collection, > firmware has chance to going incorrect address. I'm still lost on what this means. The device doesn't receive 'D3hot' from the host, it receives a shutdown request. And we don't just do that when hibernating, but also when doing an actual shutdown, a suspend to disk, unbinding the driver, etc. So if the device has a problem with shutdowns we really are in trouble.