[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <202205041200.147A737@keescook>
Date: Wed, 4 May 2022 12:01:11 -0700
From: Kees Cook <keescook@...omium.org>
To: Catalin Marinas <catalin.marinas@....com>
Cc: Mark Rutland <mark.rutland@....com>,
linux-arm-kernel@...ts.infradead.org, akpm@...ux-foundation.org,
alex.popov@...ux.com, linux-kernel@...r.kernel.org,
luto@...nel.org, will@...nel.org
Subject: Re: [PATCH v2 01/13] arm64: stackleak: fix current_top_of_stack()
On Wed, May 04, 2022 at 05:41:32PM +0100, Catalin Marinas wrote:
> On Wed, Apr 27, 2022 at 06:31:16PM +0100, Mark Rutland wrote:
> > [...]
> > Fixes: 0b3e336601b82c6a ("arm64: Add support for STACKLEAK gcc plugin")
> > Signed-off-by: Mark Rutland <mark.rutland@....com>
> > Cc: Alexander Popov <alex.popov@...ux.com>
> > Cc: Andrew Morton <akpm@...ux-foundation.org>
> > Cc: Andy Lutomirski <luto@...nel.org>
> > Cc: Catalin Marinas <catalin.marinas@....com>
> > Cc: Kees Cook <keescook@...omium.org>
> > Cc: Will Deacon <will@...nel.org>
>
> I thought this was queued already but I couldn't find it in -next. So:
>
> Acked-by: Catalin Marinas <catalin.marinas@....com>
Should this patch go via the arm64 tree for -rc6, or should I just carry
it as part of the overall stackleak series?
--
Kees Cook
Powered by blists - more mailing lists