[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YrWjH4H7KxLAqfph@sirena.org.uk>
Date: Fri, 24 Jun 2022 12:42:23 +0100
From: Mark Brown <broonie@...nel.org>
To: Will Deacon <will@...nel.org>
Cc: madvenka@...ux.microsoft.com, mark.rutland@....com,
jpoimboe@...hat.com, ardb@...nel.org, nobuta.keiya@...itsu.com,
sjitindarsingh@...il.com, catalin.marinas@....com,
jamorris@...ux.microsoft.com, linux-arm-kernel@...ts.infradead.org,
live-patching@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v15 0/6] arm64: Reorganize the unwinder and implement
stack trace reliability checks
On Thu, Jun 23, 2022 at 06:32:24PM +0100, Will Deacon wrote:
> On Fri, Jun 17, 2022 at 04:07:11PM -0500, madvenka@...ux.microsoft.com wrote:
> > as HAVE_RELIABLE_STACKTRACE depends on STACK_VALIDATION which is not present
> > yet. This patch will be added in the future once Objtool is enhanced to
> > provide stack validation in some form.
> Given that it's not at all obvious that we're going to end up using objtool
> for arm64, does this patch series gain us anything in isolation?
Having the reliability information seems like it should be useful in
general even without doing live patching - we can use it to annotate
stack traces to warn people about anything that might be suspect in
there. For live patching it's probably something we'll want regardless
of the use of objtool, it's one more robustness check which always
helps.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists