linux-kernel - Re: [PATCH 1/2] PCI: Clear LBMS on resume to avoid Target Speed quirk

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]

Message-ID: <alpine.DEB.2.21.2402121745300.2376@angie.orcam.me.uk>
Date: Mon, 12 Feb 2024 17:56:26 +0000 (GMT)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
cc: Bjorn Helgaas <helgaas@...nel.org>, linux-pci@...r.kernel.org, 
    LKML <linux-kernel@...r.kernel.org>, 
    Mika Westerberg <mika.westerberg@...ux.intel.com>
Subject: Re: [PATCH 1/2] PCI: Clear LBMS on resume to avoid Target Speed
 quirk

On Thu, 1 Feb 2024, Maciej W. Rozycki wrote:

> > > There's always an option to store it into pci_dev for later use when the 
> > > quirk is found to be working for the first time if other solutions don't 
> > > work.
> 
>  Indeed there is.

 On second thoughts there is not.

 The thing is if we handle a situation where the downstream device can be 
replaced while in suspend (which I infer from the discussion that we do), 
then it could be that one device will require the quirk while the other 
one will not.

 So any previous results have to be considered irrelevant and the whole 
dance with the quirk has to be repeated every time at resume or hot-plug.

  Maciej