On 09/04/2026 13:19, Kees Cook wrote: > On Thu, 09 Apr 2026 12:12:29 -0300, Guilherme G. Piccoli wrote: >> The pstore ftrace frontend works by purely collecting the >> instruction address, saving it on the persistent area through >> the backend and when the log is read, on next boot for example, >> the address is then resolved by using the regular printk symbol >> lookup (%pS for example). >> >> Problem: if we are running a relocatable kernel with KASLR enabled, >> this is a recipe for failure in the symbol resolution on next boots, >> since the addresses are offset'ed by the KASLR address. So, naturally >> the way to go is factor the KASLR address out of instruction address >> collection, and adding the fresh offset when resolving the symbol >> on future boots. >> >> [...] > > Applied to for-next/pstore, thanks! > > [1/1] pstore/ftrace: Factor KASLR offset in the core kernel instruction > addresses > https://git.kernel.org/kees/c/187e3865f298 > > Take care, >
Closing the loop: due to a problem reported by the kernel robot in the V1, patch was removed from the for-next/pstore tree; V3 here: https://lore.kernel.org/r/[email protected]/ Thanks, Guilherme
