linux-kernel - Re: [PATCH] irqchip/riscv-aplic: adapt to syscore API passing context data

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20260102093744.66053-1-ming.jvle@gmail.com>
Date: Fri,  2 Jan 2026 17:37:41 +0800
From: Keke Ming <ming.jvle@...il.com>
To: sanjayembeddedse@...il.com
Cc: alex@...ti.fr,
	anup@...infault.org,
	aou@...s.berkeley.edu,
	linux-kernel@...r.kernel.org,
	linux-riscv@...ts.infradead.org,
	palmer@...belt.com,
	pjw@...nel.org,
	tglx@...utronix.de,
	virendrasinhchauhan1206@...il.com,
	Keke Ming <ming.jvle@...il.com>
Subject: Re: [PATCH] irqchip/riscv-aplic: adapt to syscore API passing context data

On Wed, Dec 24, 2025 at 16:41:46 +0530, Sanjay Chitroda wrote:
> The RISC-V APLIC driver started preserving state across suspend/resume,
> but its syscore usage still assumed the old API. Building against
> linux-next after a97fbc3ee3e2 fails because the callbacks don’t receive
> the necessary driver context.

Tested this on riscv64 (cross-compiled on x86_64) using linux-next 
(next-20251219). Without this patch, the build fails with:

drivers/irqchip/irq-riscv-aplic-main.c:111:20: error: initialization of 
‘int (*)(void *)’ from incompatible pointer type ‘int (*)(void)’

This patch correctly fixes the compilation error by updating the APLIC 
driver to the new syscore API.

Tested-by: Keke Ming <ming.jvle@...il.com>