linux-kernel - [PATCH v2 0/3] PCI: Always lift 2.5GT/s restriction in PCIe failed link retraining

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-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.21.2512072345220.49654@angie.orcam.me.uk>
Date: Mon, 8 Dec 2025 19:24:23 +0000 (GMT)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: Bjorn Helgaas <bhelgaas@...gle.com>, 
    Matthew W Carlis <mattc@...estorage.com>, 
    ALOK TIWARI <alok.a.tiwari@...cle.com>
cc: ashishk@...estorage.com, msaggi@...estorage.com, sconnor@...estorage.com, 
    Lukas Wunner <lukas@...ner.de>, 
    Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>, 
    Jiwei <jiwei.sun.bj@...com>, guojinhui.liam@...edance.com, 
    ahuang12@...ovo.com, sunjw10@...ovo.com, linux-pci@...r.kernel.org, 
    linux-kernel@...r.kernel.org
Subject: [PATCH v2 0/3] PCI: Always lift 2.5GT/s restriction in PCIe failed
 link retraining

Hi,

 I've figured out that backporting will be less intrusive if an update to 
use `->supported_speeds' is posted as a separate follow-up change.  So it 
is now 2/3 in this series, after 1/3 comprising the original patch, only 
trivially updated.  Then 3/3 moves the maximum link speed determination 
earlier on for an early exit in the PCIE_SPEED_2_5GT case; maybe unlikely, 
but essentially free now, now that we retrieve the speed anyway, and makes 
code a little simpler yet.

 Please let me know if you'd prefer me to fold 2/3 into 1/3 after all.

 Previous iterations:

- v1 at: <https://lore.kernel.org/r/alpine.DEB.2.21.2511290245460.36486@angie.orcam.me.uk/>.

  Maciej