[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <165099545363.893398.5975919098164892758.b4-ty@chromium.org>
Date: Tue, 26 Apr 2022 10:51:00 -0700
From: Kees Cook <keescook@...omium.org>
To: linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
mark.rutland@....com
Cc: Kees Cook <keescook@...omium.org>, catalin.marinas@....com,
luto@...nel.org, Andrew Morton <akpm@...ux-foundation.org>,
will@...nel.org, alex.popov@...ux.com
Subject: Re: [PATCH 0/8] stackleak: fixes and rework
On Mon, 25 Apr 2022 12:55:55 +0100, Mark Rutland wrote:
> This series reworks the stackleak code. The first patch fixes some
> latent issues on arm64, and the subsequent patches improve the code to
> improve clarity and permit better code generation.
>
> I started working on this as a tangent from rework to arm64's stacktrace
> code. Looking at users of the `on_*_stack()` helpers I noticed that the
> assembly generated for stackleak was particularly awful as it performed
> a lot of redundant work and also called instrumentable code, which isn't
> sound.
>
> [...]
Applied to for-next/hardening, thanks!
[1/8] arm64: stackleak: fix current_top_of_stack()
https://git.kernel.org/kees/c/b9f8167d08e9
[2/8] stackleak: move skip_erasing() check earlier
https://git.kernel.org/kees/c/b7d6315d1d7c
[3/8] stackleak: rework stack low bound handling
https://git.kernel.org/kees/c/1f4f72d1d99e
[4/8] stackleak: clarify variable names
https://git.kernel.org/kees/c/52a2aa794e0a
[5/8] stackleak: rework stack high bound handling
https://git.kernel.org/kees/c/83301ac044c9
[6/8] stackleak: remove redundant check
https://git.kernel.org/kees/c/0cd7ee6880c7
[7/8] stackleak: add on/off stack variants
https://git.kernel.org/kees/c/9bb0b174fd2b
[8/8] arm64: entry: use stackleak_erase_on_task_stack()
https://git.kernel.org/kees/c/6a5927e73497
--
Kees Cook
Powered by blists - more mailing lists