linux-kernel - Re: [PATCH 1/1] PCI: Cleanup link activation wait logic

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 for Android: free password hash cracker in your pocket

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

Message-ID: <alpine.DEB.2.21.2402261244030.60326@angie.orcam.me.uk>
Date: Mon, 26 Feb 2024 12:53:35 +0000 (GMT)
From: "Maciej W. Rozycki" <macro@...am.me.uk>
To: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
cc: Bjorn Helgaas <bhelgaas@...gle.com>, linux-pci@...r.kernel.org, 
    LKML <linux-kernel@...r.kernel.org>, 
    Mika Westerberg <mika.westerberg@...ux.intel.com>
Subject: Re: [PATCH 1/1] PCI: Cleanup link activation wait logic

On Sat, 10 Feb 2024, Maciej W. Rozycki wrote:

> > >  You change the logic here in that the second conditional isn't run if the 
> > > first has not.  This is wrong, unclamping is not supposed to rely on LBMS. 
> > > It is supposed to be always run and any failure has to be reported too, as 
> > > a retraining error.  I'll send an update according to what I have outlined 
> > > before then, with some testing done first.
> > 
> > Oh I see now, I'm sorry, I didn't read all the way to the last paragraph 
> > of the commit message because the earlier one in the commit message hinted 
> > the restriction is removed afterwards so I thought it was only linked to 
> > the first part of the quirk.
> 
>  No worries.  I have submitted the changes now: 
> <https://lore.kernel.org/r/alpine.DEB.2.21.2402092125070.2376@angie.orcam.me.uk/>.
> 
>  Unfortunately due to a sudden hardware failure I wasn't able to do any
> non-trivial verification, as explained in the cover letter.  I'll try to 
> get back to it as soon as reasonably possible, hopefully next month.

 I have the failure sorted now, simply reseating one of the connections 
made all the option modules work again as previously.  I'm not impressed 
by this lack of reliability, but maybe it was just bad lack, as things 
used to work just fine for over 2 years before I replaced the mainboard.

 I'll see if I can do some verification this week.

  Maciej