From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
PCI <linux-pci@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org,
Linux Regressions <regressions@lists.linux.dev>,
Bjorn Helgaas <bhelgaas@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
shivamurthy.shastri@linutronix.de,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: next-20250324: x86_64: BUG: kernel NULL pointer dereference __pci_enable_msi_range
Date: Tue, 25 Mar 2025 15:53:40 +0100 [thread overview]
Message-ID: <Z-LDdPeTsnBi8gAU@macbook.local> (raw)
In-Reply-To: <b6df035d-74b5-4113-84c3-1a0a18a61e78@stanley.mountain>
On Tue, Mar 25, 2025 at 04:56:33PM +0300, Dan Carpenter wrote:
> If I had to guess, I'd say that it was related to Fixes: d9f2164238d8
> ("PCI/MSI: Convert pci_msi_ignore_mask to per MSI domain flag"). I
> suspect d->host_data can be NULL. I could be wrong, but let's add Roger
> to the CC list just in case.
Indeed, sorry. There's a patch from Thomas to switch to using
pci_msi_domain_supports() for fetching the flag, as there's no
guarantee all call contexts will have an associated msi_domain_info:
https://lore.kernel.org/xen-devel/87v7rxzct0.ffs@tglx/
Regards, Roger.
next prev parent reply other threads:[~2025-03-25 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 11:41 next-20250324: x86_64: BUG: kernel NULL pointer dereference __pci_enable_msi_range Naresh Kamboju
2025-03-25 13:56 ` Dan Carpenter
2025-03-25 14:53 ` Roger Pau Monné [this message]
2025-03-27 8:40 ` Naresh Kamboju
2025-03-27 11:00 ` Roger Pau Monné
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=Z-LDdPeTsnBi8gAU@macbook.local \
--to=roger.pau@citrix.com \
--cc=anders.roxell@linaro.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=dan.carpenter@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=regressions@lists.linux.dev \
--cc=shivamurthy.shastri@linutronix.de \
--cc=tglx@linutronix.de \
/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