From: Marc Zyngier <maz@kernel.org>
To: wens@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Mark Rutland <mark.rutland@arm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Mark Kettenis <mark.kettenis@xs4all.nl>,
Chen-Yu Tsai <wenst@chromium.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] irqchip/gic-v3: Work around insecure GIC integrations
Date: Fri, 13 Dec 2024 15:44:23 +0000 [thread overview]
Message-ID: <86ed2bsi3s.wl-maz@kernel.org> (raw)
In-Reply-To: <CAGb2v67vgoZr_1T579SrwG9UvNs0eRfT37Qk_g2k7Z-mRfEXNg@mail.gmail.com>
On Fri, 13 Dec 2024 15:10:11 +0000,
Chen-Yu Tsai <wens@kernel.org> wrote:
>
> On Fri, Dec 13, 2024 at 10:34 PM Marc Zyngier <maz@kernel.org> wrote:
> >
> > It appears that the relatively popular RK3399 SoC has been put together
> > using a large amount of illicit substances, as experiments reveal
> > that its integration of GIC500 exposes the *secure* programming
> > interface to non-secure.
> >
> > This has some pretty bad effects on the way priorities are handled,
> > and results in a dead machine if booting with pseudo-NMI enabled
> > (irqchip.gicv3_pseudo_nmi=1) if the kernel contains 18fdb6348c480
> > ("arm64: irqchip/gic-v3: Select priorities at boot time"), which
> > relies on the priorities being programmed using the NS view.
> >
> > Let's restore some sanity by going one step further and disable
> > security altogether in this case. This is not any worse, and
> > puts us in a mode where priorities actually make some sense.
> >
> > Huge thanks to Mark Kettenis who initially identified this issue
> > on OpenBSD, and to Chen-Yu Tsai who reported the problem in
> > Linux.
> >
> > Fixes: 18fdb6348c480 ("arm64: irqchip/gic-v3: Select priorities at boot time")
> > Reported-by: Mark Kettenis <mark.kettenis@xs4all.nl>
> > Reported-by: Chen-Yu Tsai <wenst@chromium.org>
>
> Should be
>
> Reported-by: Chen-Yu Tsai <wens@csie.org>
>
> (I know it's confusing, I even mix up inboxes at work.)
Ah, fair enough. Given that the report was on IRC, I had just used the
first address git log gave me.
> > Signed-off-by: Marc Zyngier <maz@kernel.org>
> > Cc: stable@vger.kernel.org
>
> Tested-by: Chen-Yu Tsai <wens@csie.org>
>
> My RK3399 boots normally with pseudo NMI enabled with this patch now.
> Also tried NMI backtraces through sysrq, though I'm not sure that
> always goes through the pseudo NMI path?
Should do, according to arch/arm64/kernel/smp::ipi_setup().
Thanks for having tested it.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2024-12-13 15:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 14:10 [PATCH] irqchip/gic-v3: Work around insecure GIC integrations Marc Zyngier
2024-12-13 15:10 ` Chen-Yu Tsai
2024-12-13 15:44 ` Marc Zyngier [this message]
2024-12-13 17:20 ` [tip: irq/urgent] " tip-bot2 for Marc Zyngier
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=86ed2bsi3s.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.kettenis@xs4all.nl \
--cc=mark.rutland@arm.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=wens@kernel.org \
--cc=wenst@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.