[PATCH V3 1/1] nvme: Add quirk for LiteON CL1 devices running FW 220TQ,22001

Gloria Tsai Gloria.Tsai at ssstc.com
Wed Oct 28 23:21:27 EDT 2020


Correct, it's device SRAM.


Regards,
Gloria Tsai
_____________________________________

Sales PM Division
Solid State Storage Technology Corporation
TEL: +886-3-612-3888 ext. 2201
E-Mail: gloria.tsai at ssstc.com
_____________________________________

-----Original Message-----
From: Keith Busch <kbusch at kernel.org> 
Sent: Thursday, October 29, 2020 11:15 AM
To: Gloria Tsai <Gloria.Tsai at ssstc.com>
Cc: Jongpil Jung <jongpuls at gmail.com>; Sagi Grimberg <sagi at grimberg.me>; linux-kernel at vger.kernel.org; linux-nvme at lists.infradead.org; Jens Axboe <axboe at fb.com>; dj54.sohn at samsung.com; jongpil19.jung at samsung.com; jongheony.kim at samsung.com; Christoph Hellwig <hch at lst.de>
Subject: Re: [PATCH V3 1/1] nvme: Add quirk for LiteON CL1 devices running FW 220TQ,22001



This message was sent from outside of the company. Please do not click links or open attachments unless you recognize the source of this email and know the content is safe.


On Thu, Oct 29, 2020 at 11:33:06AM +0900, Keith Busch wrote:
> On Thu, Oct 29, 2020 at 02:20:27AM +0000, Gloria Tsai wrote:
> > Corrected the description of this bug that SSD will not do GC after receiving shutdown cmd.
> > Do GC before shutdown -> delete IO Q -> shutdown from host -> 
> > breakup GC -> D3hot -> enter PS4 -> have a chance swap block -> use 
> > wrong pointer on device SRAM -> over program
>
> What do you mean by "wrong pointer"? At the place in the sequence 
> you're referring to, the PCI BME is disabled: you can't access *any* 
> host RAM, so there's no "correct" pointer either.

Re-reading your message, I do see you said "device" rather than "host", so my response may not be relevant.



More information about the Linux-nvme mailing list