From: patchwork-bot+linux-riscv@kernel.org
To: Kees Cook <kees@kernel.org>
Cc: linux-riscv@lists.infradead.org, arnd@arndb.de, mingo@kernel.org,
gustavoars@kernel.org, hch@lst.de, andreyknvl@gmail.com,
ryabinin.a.a@gmail.com, ardb@kernel.org, masahiroy@kernel.org,
nathan@kernel.org, nicolas.schier@linux.dev,
nick.desaulniers+lkml@gmail.com, morbo@google.com,
justinstitt@google.com, linux-kernel@vger.kernel.org,
x86@kernel.org, kasan-dev@googlegroups.com,
linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kvmarm@lists.linux.dev, linux-s390@vger.kernel.org,
linux-efi@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-kbuild@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kselftest@vger.kernel.org, sparclinux@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH v3 00/13] stackleak: Support Clang stack depth tracking
Date: Sun, 10 Aug 2025 21:12:22 +0000 [thread overview]
Message-ID: <175486034248.1221929.3658503475425874388.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250717231756.make.423-kees@kernel.org>
Hello:
This series was applied to riscv/linux.git (fixes)
by Kees Cook <kees@kernel.org>:
On Thu, 17 Jul 2025 16:25:05 -0700 you wrote:
> v3:
> - split up and drop __init vs inline patches that went via arch trees
> - apply feedback about preferring __init to __always_inline
> - incorporate Ritesh Harjani's patch for __init cleanups in powerpc
> - wider build testing on older compilers
> v2: https://lore.kernel.org/lkml/20250523043251.it.550-kees@kernel.org/
> v1: https://lore.kernel.org/lkml/20250507180852.work.231-kees@kernel.org/
>
> [...]
Here is the summary with links:
- [v3,01/13] stackleak: Rename STACKLEAK to KSTACK_ERASE
(no matching commit)
- [v3,02/13] stackleak: Rename stackleak_track_stack to __sanitizer_cov_stack_depth
(no matching commit)
- [v3,03/13] stackleak: Split KSTACK_ERASE_CFLAGS from GCC_PLUGINS_CFLAGS
(no matching commit)
- [v3,04/13] x86: Handle KCOV __init vs inline mismatches
(no matching commit)
- [v3,05/13] arm: Handle KCOV __init vs inline mismatches
(no matching commit)
- [v3,06/13] arm64: Handle KCOV __init vs inline mismatches
https://git.kernel.org/riscv/c/65c430906eff
- [v3,07/13] s390: Handle KCOV __init vs inline mismatches
https://git.kernel.org/riscv/c/c64d6be1a6f8
- [v3,08/13] powerpc/mm/book3s64: Move kfence and debug_pagealloc related calls to __init section
https://git.kernel.org/riscv/c/645d1b666498
- [v3,09/13] mips: Handle KCOV __init vs inline mismatch
https://git.kernel.org/riscv/c/d01daf9d95c9
- [v3,10/13] init.h: Disable sanitizer coverage for __init and __head
https://git.kernel.org/riscv/c/381a38ea53d2
- [v3,11/13] kstack_erase: Support Clang stack depth tracking
(no matching commit)
- [v3,12/13] configs/hardening: Enable CONFIG_KSTACK_ERASE
https://git.kernel.org/riscv/c/4c56d9f7e75e
- [v3,13/13] configs/hardening: Enable CONFIG_INIT_ON_FREE_DEFAULT_ON
https://git.kernel.org/riscv/c/437641a72d0a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+linux-riscv@kernel.org
To: Kees Cook <kees@kernel.org>
Cc: linux-riscv@lists.infradead.org, arnd@arndb.de, mingo@kernel.org,
gustavoars@kernel.org, hch@lst.de, andreyknvl@gmail.com,
ryabinin.a.a@gmail.com, ardb@kernel.org, masahiroy@kernel.org,
nathan@kernel.org, nicolas.schier@linux.dev,
nick.desaulniers+lkml@gmail.com, morbo@google.com,
justinstitt@google.com, linux-kernel@vger.kernel.org,
x86@kernel.org, kasan-dev@googlegroups.com,
linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
kvmarm@lists.linux.dev, linux-s390@vger.kernel.org,
linux-efi@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-kbuild@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-kselftest@vger.kernel.org, sparclinux@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH v3 00/13] stackleak: Support Clang stack depth tracking
Date: Sun, 10 Aug 2025 21:12:22 +0000 [thread overview]
Message-ID: <175486034248.1221929.3658503475425874388.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250717231756.make.423-kees@kernel.org>
Hello:
This series was applied to riscv/linux.git (fixes)
by Kees Cook <kees@kernel.org>:
On Thu, 17 Jul 2025 16:25:05 -0700 you wrote:
> v3:
> - split up and drop __init vs inline patches that went via arch trees
> - apply feedback about preferring __init to __always_inline
> - incorporate Ritesh Harjani's patch for __init cleanups in powerpc
> - wider build testing on older compilers
> v2: https://lore.kernel.org/lkml/20250523043251.it.550-kees@kernel.org/
> v1: https://lore.kernel.org/lkml/20250507180852.work.231-kees@kernel.org/
>
> [...]
Here is the summary with links:
- [v3,01/13] stackleak: Rename STACKLEAK to KSTACK_ERASE
(no matching commit)
- [v3,02/13] stackleak: Rename stackleak_track_stack to __sanitizer_cov_stack_depth
(no matching commit)
- [v3,03/13] stackleak: Split KSTACK_ERASE_CFLAGS from GCC_PLUGINS_CFLAGS
(no matching commit)
- [v3,04/13] x86: Handle KCOV __init vs inline mismatches
(no matching commit)
- [v3,05/13] arm: Handle KCOV __init vs inline mismatches
(no matching commit)
- [v3,06/13] arm64: Handle KCOV __init vs inline mismatches
https://git.kernel.org/riscv/c/65c430906eff
- [v3,07/13] s390: Handle KCOV __init vs inline mismatches
https://git.kernel.org/riscv/c/c64d6be1a6f8
- [v3,08/13] powerpc/mm/book3s64: Move kfence and debug_pagealloc related calls to __init section
https://git.kernel.org/riscv/c/645d1b666498
- [v3,09/13] mips: Handle KCOV __init vs inline mismatch
https://git.kernel.org/riscv/c/d01daf9d95c9
- [v3,10/13] init.h: Disable sanitizer coverage for __init and __head
https://git.kernel.org/riscv/c/381a38ea53d2
- [v3,11/13] kstack_erase: Support Clang stack depth tracking
(no matching commit)
- [v3,12/13] configs/hardening: Enable CONFIG_KSTACK_ERASE
https://git.kernel.org/riscv/c/4c56d9f7e75e
- [v3,13/13] configs/hardening: Enable CONFIG_INIT_ON_FREE_DEFAULT_ON
https://git.kernel.org/riscv/c/437641a72d0a
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2025-08-10 21:12 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-17 23:25 [PATCH v3 00/13] stackleak: Support Clang stack depth tracking Kees Cook
2025-07-17 23:25 ` Kees Cook
2025-07-17 23:25 ` [PATCH v3 01/13] stackleak: Rename STACKLEAK to KSTACK_ERASE Kees Cook
2025-07-17 23:25 ` Kees Cook
2025-07-21 20:02 ` Nicolas Schier
2025-07-21 20:02 ` Nicolas Schier
2025-07-21 20:16 ` Kees Cook
2025-07-21 20:16 ` Kees Cook
2025-07-17 23:25 ` [PATCH v3 02/13] stackleak: Rename stackleak_track_stack to __sanitizer_cov_stack_depth Kees Cook
2025-07-17 23:25 ` Kees Cook
2025-07-17 23:25 ` [PATCH v3 03/13] stackleak: Split KSTACK_ERASE_CFLAGS from GCC_PLUGINS_CFLAGS Kees Cook
2025-07-17 23:25 ` Kees Cook
2025-07-17 23:25 ` [PATCH v3 04/13] x86: Handle KCOV __init vs inline mismatches Kees Cook
2025-07-17 23:25 ` Kees Cook
2025-07-18 8:36 ` Mike Rapoport
2025-07-18 8:36 ` Mike Rapoport
2025-07-18 22:51 ` Kees Cook
2025-07-18 22:51 ` Kees Cook
2025-07-20 6:10 ` Ard Biesheuvel
2025-07-20 6:10 ` Ard Biesheuvel
2025-07-21 12:47 ` Will Deacon
2025-07-21 12:47 ` Will Deacon
2025-07-21 20:14 ` Kees Cook
2025-07-21 20:14 ` Kees Cook
2025-07-21 20:49 ` Kees Cook
2025-07-21 20:49 ` Kees Cook
2025-07-22 6:55 ` Ard Biesheuvel
2025-07-22 6:55 ` Ard Biesheuvel
2025-07-22 13:29 ` Will Deacon
2025-07-22 13:29 ` Will Deacon
2025-07-22 8:26 ` Mike Rapoport
2025-07-22 8:26 ` Mike Rapoport
2025-07-17 23:25 ` [PATCH v3 05/13] arm: " Kees Cook
2025-07-17 23:25 ` Kees Cook
2025-07-18 12:58 ` Nishanth Menon
2025-07-18 12:58 ` Nishanth Menon
2025-07-18 13:04 ` Lee Jones
2025-07-18 13:04 ` Lee Jones
2025-07-17 23:25 ` [PATCH v3 06/13] arm64: " Kees Cook
2025-07-17 23:25 ` Kees Cook
2025-07-18 11:22 ` Will Deacon
2025-07-18 11:22 ` Will Deacon
2025-07-17 23:25 ` [PATCH v3 07/13] s390: " Kees Cook
2025-07-17 23:25 ` Kees Cook
2025-07-17 23:25 ` [PATCH v3 08/13] powerpc/mm/book3s64: Move kfence and debug_pagealloc related calls to __init section Kees Cook
2025-07-17 23:25 ` Kees Cook
2025-07-17 23:25 ` [PATCH v3 09/13] mips: Handle KCOV __init vs inline mismatch Kees Cook
2025-07-17 23:25 ` Kees Cook
2025-07-18 9:18 ` Huacai Chen
2025-07-18 9:18 ` Huacai Chen
2025-07-17 23:25 ` [PATCH v3 10/13] init.h: Disable sanitizer coverage for __init and __head Kees Cook
2025-07-17 23:25 ` Kees Cook
2025-07-18 22:51 ` kernel test robot
2025-07-19 4:22 ` kernel test robot
2025-07-17 23:25 ` [PATCH v3 11/13] kstack_erase: Support Clang stack depth tracking Kees Cook
2025-07-17 23:25 ` Kees Cook
2025-07-17 23:25 ` [PATCH v3 12/13] configs/hardening: Enable CONFIG_KSTACK_ERASE Kees Cook
2025-07-17 23:25 ` Kees Cook
2025-07-17 23:25 ` [PATCH v3 13/13] configs/hardening: Enable CONFIG_INIT_ON_FREE_DEFAULT_ON Kees Cook
2025-07-17 23:25 ` Kees Cook
2025-08-10 21:12 ` patchwork-bot+linux-riscv [this message]
2025-08-10 21:12 ` [PATCH v3 00/13] stackleak: Support Clang stack depth tracking patchwork-bot+linux-riscv
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=175486034248.1221929.3658503475425874388.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=andreyknvl@gmail.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=gustavoars@kernel.org \
--cc=hch@lst.de \
--cc=justinstitt@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kees@kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-s390@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=masahiroy@kernel.org \
--cc=mingo@kernel.org \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=nick.desaulniers+lkml@gmail.com \
--cc=nicolas.schier@linux.dev \
--cc=ryabinin.a.a@gmail.com \
--cc=sparclinux@vger.kernel.org \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.