[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250129072345.3106495-1-wnliu@google.com>
Date: Wed, 29 Jan 2025 07:23:45 +0000
From: Weinan Liu <wnliu@...gle.com>
To: indu.bhagat@...cle.com
Cc: irogers@...gle.com, joe.lawrence@...hat.com, jpoimboe@...nel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
linux-toolchains@...r.kernel.org, live-patching@...r.kernel.org,
mark.rutland@....com, peterz@...radead.org, roman.gushchin@...ux.dev,
rostedt@...dmis.org, will@...nel.org, wnliu@...gle.com
Subject: Re: [PATCH 0/8] unwind, arm64: add sframe unwinder for kernel
Not only does objdump show that func_start_addr all 0s, but the
func_start_addr in the kernel module's sframe table is also incorrect. I'll
prepare a repro so we can investigate this.
>
> I can share a fix for 32589 so atleast we can verify that the starting
> point is sane.
>
Great! Thanks.
This will be helpful for comparing the values from the sframe table with
the values we obtain at runtime
Powered by blists - more mailing lists