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: <87a596zzou.ffs@tglx>
Date: Thu, 27 Mar 2025 08:43:13 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: Sasha Levin <sashal@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
 linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: [GIT pull] irq/urgent for v6.15-rc1

Sasha!

On Wed, Mar 26 2025 at 21:07, Sasha Levin wrote:
> On Wed, Mar 26, 2025 at 08:08:16PM +0100, Thomas Gleixner wrote:
>>Thomas Gleixner (1):
>>      PCI/MSI: Handle the NOMASK flag correctly for all PCI/MSI backends
>
> I haven't bisected this, but I suspect that this commit is causing
> boot-time panics that are observed on LKFT. Note the line numbers are
> off by a bit.

I'm not sure which commit you are referring to, but the one which causes
this type of failure is:

  c3164d2e0d18 ("PCI/MSI: Convert pci_msi_ignore_mask to per MSI domain flag")

which is fixed by

  3ece3e8e5976 ("PCI/MSI: Handle the NOMASK flag correctly for all PCI/MSI backends")

i.e. this pull request.

> Full logs of the run are available at:
> https://qa-reports.linaro.org/lkft/sashal-linus-next/build/v6.13-rc7-16083-gc13edfd29c29/testrun/27775255/suite/log-parser-test/test/bug-bug-kernel-null-pointer-dereference-address/details/

TBH, and I know this is not your fault, this report page is a
masterpiece of bad engineering. It contains tons of useless information,
but fails to provide the most important basic data:

  1) There is no date of the failure

     Am I supposed to reverse engineer this out of this horrible user
     interface?

     I haven't even found a way to figure it out within a reasonable
     time. I just gave up.

  2) There is no useful reference to the actually used source tree and
     commit

     v6.13-rc7-16083-gc13edfd29c29 is _NOT_ a helpful reference as it
     suggests that this is a 6.13-rc7 based tree, but the log file says:
     Linux version 6.14.0

     sasha-linus-next at least gives a hint where to rumage, and 100
     clicks later I'm able to see what this is actually testing.

Seriously?

Thanks,

        tglx


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ