From: Thomas Gleixner <tglx@kernel.org>
To: "Han / 한상우Sangwoo" <sangwoo.han@nearthlab.com>,
"Bjorn Helgaas" <helgaas@kernel.org>
Cc: jim2101024@gmail.com, florian.fainelli@broadcom.com,
lpieralisi@kernel.org, kwilczynski@kernel.org, mani@kernel.org,
bhelgaas@google.com, bcm-kernel-feedback-list@broadcom.com,
robh@kernel.org, linux-pci@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Inochi Amaoto <inochiama@gmail.com>
Subject: Re: [PATCH] PCI: brcmstb: Reserve only the MSI vectors that are handed out
Date: Fri, 30 Oct 2026 20:20:50 +0100 [thread overview]
Message-ID: <87h5i3xael.ffs@fw13> (raw)
In-Reply-To: <CAFg7d9a2p2jtGyThS1M=2ZFDX0y5rpSK3H34ZuTz09R5r_ff0A@mail.gmail.com>
On Fri, Oct 30 2026 at 21:59, Han wrote:
> On Thu, Oct 01 2026 at 21:29, Thomas Gleixner wrote:
> The buggy address is located 0 bytes to the right of
> allocated 48-byte region [ffff8000053a6880, ffff8000053a68b0)
>
> The report is caused by the patch. __msi_domain_alloc_irqs() passes
> nvec_aligned (4) to __irq_domain_alloc_irqs() together with
> desc->affinity, which has only nvec_used (3) entries. alloc_descs()
> then reads all 4 entries. The fourth entry is read past the end of
> the array. If the data there has no CPU set, the allocation fails
> with -ENOSPC. Without PCI_IRQ_AFFINITY, desc->affinity is NULL, so
> this read does not happen.
Ah. I missed that detail. I'll look at it on Monday.
prev parent reply other threads:[~2026-10-30 19:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-30 7:22 Sangwoo Han
2026-08-03 16:11 ` Manivannan Sadhasivam
2026-08-03 22:22 ` Bjorn Helgaas
2026-08-04 11:31 ` Han / 한상우Sangwoo
2026-08-04 12:50 ` Bjorn Helgaas
2026-08-10 23:30 ` Bjorn Helgaas
2026-09-07 16:34 ` Bjorn Helgaas
2026-09-07 21:40 ` Thomas Gleixner
2026-09-16 23:10 ` Bjorn Helgaas
2026-09-21 9:05 ` Han / 한상우Sangwoo
2026-10-01 19:29 ` Thomas Gleixner
2026-10-12 21:47 ` Bjorn Helgaas
2026-10-13 8:47 ` Han / 한상우Sangwoo
2026-10-13 16:06 ` Bjorn Helgaas
2026-10-30 12:59 ` Han / 한상우Sangwoo
2026-10-30 19:20 ` 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=87h5i3xael.ffs@fw13 \
--to=tglx@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=florian.fainelli@broadcom.com \
--cc=helgaas@kernel.org \
--cc=inochiama@gmail.com \
--cc=jim2101024@gmail.com \
--cc=kwilczynski@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=lpieralisi@kernel.org \
--cc=mani@kernel.org \
--cc=robh@kernel.org \
--cc=sangwoo.han@nearthlab.com \
/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
all inboxes | Powered by JetHome®