linux-kernel - Re: [PATCH] irqchip/riscv-aplic: Register the driver prior to device creation

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: <b2eb7f70-8ee9-43f6-b086-f0c17b1f9e39@picoheart.com>
Date: Fri, 16 Jan 2026 14:16:21 +0800
From: "Yicong Yang" <yang.yicong@...oheart.com>
To: "Thomas Gleixner" <tglx@...nel.org>, 
	"Anup Patel" <apatel@...tanamicro.com>
Cc: <yang.yicong@...oheart.com>, <anup@...infault.org>, <pjw@...nel.org>, 
	<palmer@...belt.com>, <aou@...s.berkeley.edu>, <alex@...ti.fr>, 
	<linux-riscv@...ts.infradead.org>, <linux-kernel@...r.kernel.org>, 
	<geshijian@...oheart.com>, <weidong.wd@...oheart.com>, 
	"Greg Kroah-Hartman" <gregkh@...uxfoundation.org>, 
	"Rafael J. Wysocki" <rafael@...nel.org>, 
	"Danilo Krummrich" <dakr@...nel.org>
Subject: Re: [PATCH] irqchip/riscv-aplic: Register the driver prior to device creation

On 1/15/26 9:28 PM, Thomas Gleixner wrote:
> On Thu, Jan 15 2026 at 16:31, Yicong Yang wrote:
>> so based on above, if we use async_wq (with async_schedule* APIs) in
>> acpi_scan_clear_dep_queue() for creating these devices, the issue
>> could be solved since we're sure to have these devices before entering
>> userspace, since the barrier of async_synchronize_full(). This should be
>> a solution with a conceptual support and I did a quick test on our
>> platform it solves the issue.
> 
> Sounds about right to me. The drivers core and ACPI folks might have
> opinions though :)
> 

sure I'll wait a bit to see if there's further comment before sending out
next version.

>> As for the order of console_on_rootfs()/async_synchronize_full(),
>> though our issue is not directly caused by it, it will cause the
>> same issue (by the console open time the async probing maybe not
>> finised) theoretically and needs to be fixed, is it?
> 
> Yes, that should move past the synchronization point.
> 

will include this fix as a separate patch since they're two separate issue.

thanks a lot for the useful discussion to help find a better solution :)

Thanks.