linux-kernel - RE: [PATCH 1/2] ACPI: resource: do IRQ override on LENOVO IdeaPad

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: <MN0PR12MB6101BF3E9F579B8AA23954BCE25D9@MN0PR12MB6101.namprd12.prod.outlook.com>
Date:   Wed, 5 Oct 2022 16:34:37 +0000
From:   "Limonciello, Mario" <Mario.Limonciello@....com>
To:     Chuanhong Guo <gch981213@...il.com>
CC:     "Jiri Slaby (SUSE)" <jirislaby@...nel.org>,
        "rafael.j.wysocki@...el.com" <rafael.j.wysocki@...el.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        Len Brown <lenb@...nel.org>,
        "linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
        Tighe Donnelly <tighe.donnelly@...tonmail.com>,
        Fridrich Strba <fstrba@...e.com>
Subject: RE: [PATCH 1/2] ACPI: resource: do IRQ override on LENOVO IdeaPad

[Public]



> -----Original Message-----
> From: Chuanhong Guo <gch981213@...il.com>
> Sent: Tuesday, October 4, 2022 23:02
> To: Limonciello, Mario <Mario.Limonciello@....com>
> Cc: Jiri Slaby (SUSE) <jirislaby@...nel.org>; rafael.j.wysocki@...el.com; linux-
> kernel@...r.kernel.org; Rafael J. Wysocki <rafael@...nel.org>; Len Brown
> <lenb@...nel.org>; linux-acpi@...r.kernel.org; Tighe Donnelly
> <tighe.donnelly@...tonmail.com>; Fridrich Strba <fstrba@...e.com>
> Subject: Re: [PATCH 1/2] ACPI: resource: do IRQ override on LENOVO
> IdeaPad
> 
> Hi!
> 
> On Wed, Oct 5, 2022 at 5:02 AM Limonciello, Mario
> <Mario.Limonciello@....com> wrote:
> > [...]
> > >
> > > White-list this specific model in the override_table.
> > >
> > > For this to work, the ZEN test needs to be put below the table walk.
> >
> > Unfortunately this is the second case that popped up very recently.
> > Another one is listed here:
> >
> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugz
> illa.kernel.org%2Fshow_bug.cgi%3Fid%3D216552&amp;data=05%7C01%7CM
> ario.Limonciello%40amd.com%7C27a32c2395ed4d2a85e208daa68666bb%7C3
> dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C638005393451041667%7C
> Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJB
> TiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=iLj95fy44%
> 2BT2KCahzTD8HP2bl2dD6gXVOcVnHylPWJc%3D&amp;reserved=0
> 
> Now I'm really curious how Windows is able to handle all these vendor crap...
> 
> > I don't think we have a good solution to cover the intersection of these
> bugs.  The
> > existing heuristic to look at legacy syntax and the IOAPIC doesn't work
> properly
> > on all the Lenovo and ASUS Ryzen 6000 systems, but it does on these other
> two.
> 
> These legacy IRQ declarations are obsolete, but they aren't really wrong.
> Meanwhile the two devices popped up until now both got IRQ declarations
> which
> don't match the actual device configuration.

You're right; both of these are technically BIOS DSDT bugs if you had assumed that this
workaround wasn't in place.

> 
> > We're going to be adding more to this table either way.  I /suspect/ the
> better solution
> > is to revert 37c81d9f1d1b and add to the table all those that are broken.
> 
> I think we should have a list of only the wrong IRQ declaration and
> apply the fix
> just for them, instead of applying the fix to all devices and skip it
> for selected
> devices the fix breaks.

OK.  In that case Jiri I think your patch series makes sense.

> 
> --
> Regards,
> Chuanhong Guo