From: Will Deacon <will@kernel.org>
To: Johnathan Smithinovic <johnathan.smithinovic@gmx.at>,
mingo@redhat.com, David Woodhouse <dwmw2@infradead.org>,
tglx@linutronix.de, bp@alien8.de
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org,
iommu <iommu@lists.linux-foundation.org>
Subject: Re: [PATCH] iommu/amd: Stop irq_remapping_select() matching when remapping is disabled
Date: Tue, 5 Jan 2021 22:07:02 +0000 [thread overview]
Message-ID: <160987465284.30865.16684216909917986687.b4-ty@kernel.org> (raw)
In-Reply-To: <04bbe8bca87f81a3cfa93ec4299e53f47e00e5b3.camel@infradead.org>
On Tue, 05 Jan 2021 01:36:13 +0000, David Woodhouse wrote:
> The AMD IOMMU initialisation registers the IRQ remapping domain for
> each IOMMU before doing the final sanity check that every I/OAPIC is
> covered.
>
> This means that the AMD irq_remapping_select() function gets invoked
> even when IRQ remapping has been disabled, eventually leading to a NULL
> pointer dereference in alloc_irq_table().
>
> [...]
Applied to arm64 (for-next/iommu/fixes), thanks!
[1/1] iommu/amd: Stop irq_remapping_select() matching when remapping is disabled
https://git.kernel.org/arm64/c/b34f10c2dc59
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2021-01-05 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 23:05 PROBLEM: commit f36a74b9345a leads to not booting system with AMD 2990WX Johnathan Smithinovic
2021-01-05 0:19 ` [EXTERNAL] " David Woodhouse
2021-01-05 2:24 ` Johnathan Smithinovic
2021-01-05 1:36 ` [PATCH] iommu/amd: Stop irq_remapping_select() matching when remapping is disabled David Woodhouse
2021-01-05 22:07 ` Will Deacon [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=160987465284.30865.16684216909917986687.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=dwmw2@infradead.org \
--cc=iommu@lists.linux-foundation.org \
--cc=johnathan.smithinovic@gmx.at \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®