linux-kernel - Re: Bug report: probe of AMDI0040:00 failed with error -16

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: <CAJZ5v0hgWGWneAgqCxZ2L85nrM_7J7H1g042sA5tzz234BNUGw@mail.gmail.com>
Date: Fri, 22 Mar 2024 15:49:29 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: "Rafael J. Wysocki" <rjw@...ysocki.net>, Francisco Ayala Le Brun <francisco@...eowindow.eu>, 
	Adrian Hunter <adrian.hunter@...el.com>, linux-mmc@...r.kernel.org, 
	linux-kernel@...r.kernel.org, ulf.hansson@...aro.org, 
	Linux ACPI <linux-acpi@...r.kernel.org>, Thomas Gleixner <tglx@...utronix.de>, 
	Mario Limonciello <mario.limonciello@....com>, "Rafael J. Wysocki" <rafael@...nel.org>
Subject: Re: Bug report: probe of AMDI0040:00 failed with error -16

On Fri, Mar 22, 2024 at 3:28 PM Linus Walleij <linus.walleij@...aroorg> wrote:
>
> On Thu, Mar 21, 2024 at 5:33 PM Rafael J. Wysocki <rjw@...ysocki.net> wrote:
>
> > We actually can get away without defining a new IRQ flag, as in
> > the patch below.
> >
> > It is not super-clean, but should do the work.
> >
> > Linus, what do you think?
>
> Uhhh I rather not, the other approach will cover the invariably recurring
> instances of this, it will not be the last time we see something like this.

I'm not actually sure how likely this is.

The ACPI SCI is generally heavy-wieght, so it is not shared very often
(and I believe that there is a particular reason for sharing it with a
GPIO chip) and this very well may be an exception.

> We need tglx input on this, I could merge the patch below with some
> big TODO to fix it properly if the discussion about the proper solution
> takes too much time.
>
> But I rather not hack around with IRQs without tglx (or marcz, but he
> got overloaded) input.

Fair enough.

I guess I'll post the first patch with a proper changelog next week
and we'll see.

Thanks!