[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20211022163604.GD174703@worktop.programming.kicks-ass.net>
Date: Fri, 22 Oct 2021 18:36:04 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Kees Cook <keescook@...omium.org>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org,
juri.lelli@...hat.com, vincent.guittot@...aro.org,
dietmar.eggemann@....com, rostedt@...dmis.org, bsegall@...gle.com,
mgorman@...e.de, bristot@...hat.com, akpm@...ux-foundation.org,
mark.rutland@....com, zhengqi.arch@...edance.com,
linux@...linux.org.uk, catalin.marinas@....com, will@...nel.org,
mpe@...erman.id.au, paul.walmsley@...ive.com, palmer@...belt.com,
hca@...ux.ibm.com, gor@...ux.ibm.com, borntraeger@...ibm.com,
linux-arch@...r.kernel.org, ardb@...nel.org
Subject: Re: [PATCH 4/7] arch: Make ARCH_STACKWALK independent of STACKTRACE
On Fri, Oct 22, 2021 at 09:18:05AM -0700, Kees Cook wrote:
> On Fri, Oct 22, 2021 at 05:09:37PM +0200, Peter Zijlstra wrote:
> > Make arch_stack_walk() available for ARCH_STACKWALK architectures
> > without it being entangled in STACKTRACE.
>
> Which CONFIG/arch combos did you build test with this? It looks good,
> but I always expect things like this to end up landing in corner cases.
> :)
I had this one through 0day last night. That's no guarantees, but at
least it's had a handfull of builds done on it.
Powered by blists - more mailing lists