From: Kees Cook <kees@kernel.org>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: Qing Zhao <qing.zhao@oracle.com>, Uros Bizjak <ubizjak@gmail.com>,
Joseph Myers <josmyers@redhat.com>,
Richard Biener <rguenther@suse.de>,
Andrew Pinski <pinskia@gmail.com>,
Jakub Jelinek <jakub@redhat.com>,
Martin Uecker <uecker@tugraz.at>,
Peter Zijlstra <peterz@infradead.org>,
Ard Biesheuvel <ardb@kernel.org>, Jan Hubicka <hubicka@ucw.cz>,
Richard Earnshaw <richard.earnshaw@arm.com>,
Richard Sandiford <richard.sandiford@arm.com>,
Marcus Shawcroft <marcus.shawcroft@arm.com>,
Kyrylo Tkachov <kyrylo.tkachov@arm.com>,
Kito Cheng <kito.cheng@gmail.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Andrew Waterman <andrew@sifive.com>,
Jim Wilson <jim.wilson.gcc@gmail.com>,
Dan Li <ashimida.1990@gmail.com>,
Sami Tolvanen <samitolvanen@google.com>,
Ramon de C Valle <rcvalle@google.com>,
Joao Moreira <joao@overdrivepizza.com>,
Nathan Chancellor <nathan@kernel.org>,
Bill Wendling <morbo@google.com>,
"Osterlund, Sebastian" <sebastian.osterlund@intel.com>,
"Constable, Scott D" <scott.d.constable@intel.com>,
gcc-patches@gcc.gnu.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH v7 7/7] riscv: Add RISC-V Kernel Control Flow Integrity implementation
Date: Wed, 19 Nov 2025 16:40:27 -0800 [thread overview]
Message-ID: <202511191549.E163044@keescook> (raw)
In-Reply-To: <c8b5038c-222f-4215-84c4-3f0698ccf10e@gmail.com>
On Wed, Nov 19, 2025 at 08:35:35AM -0700, Jeff Law wrote:
> Note there's still review work to do on the RISC-V bits. But it's worth
> noting your patch triggers ICEs in the RISC-V testsuite. See:
>
> https://github.com/ewlu/gcc-precommit-ci/issues/4115#issuecomment-3543758441
Ah thanks for the pointer -- I didn't know there were any CIs running on
patch submission!
I fixed a bunch of the lint issues and found a few more too. :)
I'll get the test failures tracked down...
--
Kees Cook
prev parent reply other threads:[~2025-11-20 0:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 20:12 [PATCH v7 0/7] Introduce Kernel Control Flow Integrity ABI [PR107048] Kees Cook
2025-11-17 20:12 ` [PATCH v7 1/7] typeinfo: Introduce KCFI typeinfo mangling API Kees Cook
2025-11-17 20:12 ` [PATCH v7 2/7] kcfi: Add core Kernel Control Flow Integrity infrastructure Kees Cook
2025-11-17 20:12 ` [PATCH v7 3/7] kcfi: Add regression test suite Kees Cook
2025-11-17 20:12 ` [PATCH v7 4/7] x86: Add x86_64 Kernel Control Flow Integrity implementation Kees Cook
2025-11-17 20:12 ` [PATCH v7 5/7] aarch64: Add AArch64 " Kees Cook
2025-11-17 20:12 ` [PATCH v7 6/7] arm: Add ARM 32-bit " Kees Cook
2025-11-17 20:12 ` [PATCH v7 7/7] riscv: Add RISC-V " Kees Cook
2025-11-19 15:35 ` Jeff Law
2025-11-20 0:40 ` Kees Cook [this message]
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=202511191549.E163044@keescook \
--to=kees@kernel.org \
--cc=andrew@sifive.com \
--cc=ardb@kernel.org \
--cc=ashimida.1990@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=jakub@redhat.com \
--cc=jeffreyalaw@gmail.com \
--cc=jim.wilson.gcc@gmail.com \
--cc=joao@overdrivepizza.com \
--cc=josmyers@redhat.com \
--cc=kito.cheng@gmail.com \
--cc=kyrylo.tkachov@arm.com \
--cc=linux-hardening@vger.kernel.org \
--cc=marcus.shawcroft@arm.com \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=palmer@dabbelt.com \
--cc=peterz@infradead.org \
--cc=pinskia@gmail.com \
--cc=qing.zhao@oracle.com \
--cc=rcvalle@google.com \
--cc=rguenther@suse.de \
--cc=richard.earnshaw@arm.com \
--cc=richard.sandiford@arm.com \
--cc=samitolvanen@google.com \
--cc=scott.d.constable@intel.com \
--cc=sebastian.osterlund@intel.com \
--cc=ubizjak@gmail.com \
--cc=uecker@tugraz.at \
/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.