From: Thomas Gleixner <tglx@linutronix.de>
To: Sasha Levin <sashal@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [GIT pull] irq/urgent for v6.15-rc1
Date: Thu, 27 Mar 2025 08:43:13 +0100 [thread overview]
Message-ID: <87a596zzou.ffs@tglx> (raw)
In-Reply-To: <Z-Sk41xJ-JIkoZt8@lappy>
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
prev parent reply other threads:[~2025-03-27 7:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 19:08 [GIT pull] irq/urgent for v6.15-rc1 Thomas Gleixner
2025-03-27 0:57 ` pr-tracker-bot
2025-03-27 1:07 ` Sasha Levin
2025-03-27 7:43 ` Thomas Gleixner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a596zzou.ffs@tglx \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox