linux-kernel - Re: realtek,rtl-intc IRQ mapping broken on 5.16-rc1

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: <9c169aad-3c7b-2ffb-90a2-1ca791a3f411@phrozen.org>
Date:   Sun, 21 Nov 2021 22:11:15 +0100
From:   John Crispin <john@...ozen.org>
To:     Sander Vanheule <sander@...nheule.net>,
        Marc Zyngier <maz@...nel.org>,
        Rob Herring <robh+dt@...nel.org>,
        Birger Koblitz <mail@...ger-koblitz.de>
Cc:     Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
        Bjorn Helgaas <bhelgaas@...gle.com>,
        Bert Vermeulen <bert@...t.com>,
        Thomas Gleixner <tglx@...utronix.de>,
        linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
        Frank Rowand <frowand.list@...il.com>
Subject: Re: realtek,rtl-intc IRQ mapping broken on 5.16-rc1

On 21.11.21 21:33, Sander Vanheule wrote:
> Alternatively, a second compatible could perhaps be introduced and the current
> one would be deprecated, using (2) to prevent breaking 5.16+ kernels. I don't
> think that's really worth the effort though.
> 
> Best,

Hey,

I think that what Marc proposed as (1) is the clean solution. We want to 
describe the HW as it exists. Yes we have zero docs, and the RLT 2.6 sdk 
kernel is a pain to extract info from, yet we should move fwd with a 
clean implementation.

breaking pseudo owrt dts ABI is imho acceptable. owrt users are well 
able to reflash their units from uboot, they are at the end flying 
without wings on bleeding edge. asking for some backward compat for a 
de-facto broken dts mapping of the HW is imho a no-go.

	John