[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id:
<172191363937.6240.7475127253705380898.git-patchwork-notify@kernel.org>
Date: Thu, 25 Jul 2024 13:20:39 +0000
From: patchwork-bot+linux-riscv@...nel.org
To: Jisheng Zhang <jszhang@...nel.org>
Cc: linux-riscv@...ts.infradead.org, paul.walmsley@...ive.com,
palmer@...belt.com, aou@...s.berkeley.edu, ardb@...nel.org,
charlie@...osinc.com, linux-kernel@...r.kernel.org, linux-efi@...r.kernel.org
Subject: Re: [PATCH v2] riscv: enable HAVE_ARCH_STACKLEAK
Hello:
This patch was applied to riscv/linux.git (for-next)
by Palmer Dabbelt <palmer@...osinc.com>:
On Mon, 24 Jun 2024 07:53:16 +0800 you wrote:
> Add support for the stackleak feature. Whenever the kernel returns to user
> space the kernel stack is filled with a poison value.
>
> At the same time, disables the plugin in EFI stub code because EFI stub
> is out of scope for the protection.
>
> Tested on qemu and milkv duo:
> / # echo STACKLEAK_ERASING > /sys/kernel/debug/provoke-crash/DIRECT
> [ 38.675575] lkdtm: Performing direct entry STACKLEAK_ERASING
> [ 38.678448] lkdtm: stackleak stack usage:
> [ 38.678448] high offset: 288 bytes
> [ 38.678448] current: 496 bytes
> [ 38.678448] lowest: 1328 bytes
> [ 38.678448] tracked: 1328 bytes
> [ 38.678448] untracked: 448 bytes
> [ 38.678448] poisoned: 14312 bytes
> [ 38.678448] low offset: 8 bytes
> [ 38.689887] lkdtm: OK: the rest of the thread stack is properly erased
>
> [...]
Here is the summary with links:
- [v2] riscv: enable HAVE_ARCH_STACKLEAK
https://git.kernel.org/riscv/c/0059748ce289
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
Powered by blists - more mailing lists