linux-kernel - Re: [PATCH v2 1/2] irqchip/gic-v3: Add Rockchip 3588001 errata workaround

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <865y9tlg7q.wl-maz@kernel.org>
Date:   Tue, 18 Apr 2023 09:58:17 +0100
From:   Marc Zyngier <maz@...nel.org>
To:     Sebastian Reichel <sebastian.reichel@...labora.com>
Cc:     Heiko Stuebner <heiko@...ech.de>, Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Peng Fan <peng.fan@....com>,
        Robin Murphy <robin.murphy@....com>,
        Peter Geis <pgwipeout@...il.com>,
        XiaoDong Huang <derrick.huang@...k-chips.com>,
        Kever Yang <kever.yang@...k-chips.com>,
        linux-rockchip@...ts.infradead.org, devicetree@...r.kernel.org,
        linux-kernel@...r.kernel.org, kernel@...labora.com
Subject: Re: [PATCH v2 1/2] irqchip/gic-v3: Add Rockchip 3588001 errata workaround

On Mon, 17 Apr 2023 22:40:33 +0100,
Sebastian Reichel <sebastian.reichel@...labora.com> wrote:
> 
> Hi,
> 
> On Mon, Apr 17, 2023 at 05:20:08PM +0100, Marc Zyngier wrote:
> >> [...]
> > Please see below for an untested diff against your patch, addressing
> > most of the issues mentioned here.
> 
> Thanks, looks good. I integrated the changes into v3.
> 
> > Also, I don't see anything here addressing the *other* bug this
> > platform suffers from, which is the 32bit limit to the allocations.
> > Without a fix for it, this patch is pointless as the GIC may end-up
> > with memory it cannot reach.
> >
> > What;s the plan for that?
> 
> It got fixed in RK3588.

So what's the plan for the affected SoCs? It might be a good idea to
address it too, unless there are none of them in the wild?

	M.

-- 
Without deviation from the norm, progress is not possible.