linux-kernel - Re: [PATCH v3] nvme: Add quirk for LiteON CL1 devices running FW 22301111

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 19 Aug 2019 13:02:08 -0600
From:   Jens Axboe <axboe@...nel.dk>
To:     Sagi Grimberg <sagi@...mberg.me>,
        Mario Limonciello <mario.limonciello@...l.com>,
        Keith Busch <kbusch@...nel.org>
Cc:     Christoph Hellwig <hch@....de>, linux-nvme@...ts.infradead.org,
        LKML <linux-kernel@...r.kernel.org>,
        Ryan Hong <Ryan.Hong@...l.com>, Crag Wang <Crag.Wang@...l.com>,
        sjg@...gle.com, Charles Hyde <charles.hyde@...lteam.com>,
        Jared Dominguez <jared.dominguez@...l.com>
Subject: Re: [PATCH v3] nvme: Add quirk for LiteON CL1 devices running FW
 22301111

On 8/19/19 12:57 PM, Sagi Grimberg wrote:
> 
> 
> On 8/16/19 1:16 PM, Mario Limonciello wrote:
>> One of the components in LiteON CL1 device has limitations that
>> can be encountered based upon boundary race conditions using the
>> nvme bus specific suspend to idle flow.
>>
>> When this situation occurs the drive doesn't resume properly from
>> suspend-to-idle.
>>
>> LiteON has confirmed this problem and fixed in the next firmware
>> version.  As this firmware is already in the field, avoid running
>> nvme specific suspend to idle flow.
>>
>> Fixes: d916b1be94b6 ("nvme-pci: use host managed power state for suspend")
>> Link: http://lists.infradead.org/pipermail/linux-nvme/2019-July/thread.html
>> Signed-off-by: Mario Limonciello <mario.limonciello@...l.com>
>> Signed-off-by: Charles Hyde <charles.hyde@...lteam.com>
>> ---
> 
> Jens, can you please rebase for-linus so we have the needed dependency:
> 4eaefe8c621c6195c91044396ed8060c179f7aae

I just did as part of adding a new patch, being pushed out shortly.

-- 
Jens Axboe