From: Nathan Chancellor <nathan@kernel.org> To: Conor Dooley <conor@kernel.org> Cc: linux-riscv@lists.infradead.org, Conor Dooley <conor.dooley@microchip.com>, stable@vger.kernel.org, Miguel Ojeda <ojeda@kernel.org>, Alex Gaynor <alex.gaynor@gmail.com>, Wedson Almeida Filho <wedsonaf@gmail.com>, linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org, Sami Tolvanen <samitolvanen@google.com>, Kees Cook <keescook@chromium.org>, llvm@lists.linux.dev Subject: Re: [PATCH v3] rust: make mutually exclusive with CFI_CLANG Date: Thu, 4 Apr 2024 08:32:58 -0700 [thread overview] Message-ID: <20240404153258.GA852748@dev-arch.thelio-3990X> (raw) In-Reply-To: <20240404-providing-emporium-e652e359c711@spud> On Thu, Apr 04, 2024 at 03:17:02PM +0100, Conor Dooley wrote: > From: Conor Dooley <conor.dooley@microchip.com> > > On RISC-V and arm64, and presumably x86, if CFI_CLANG is enabled, > loading a rust module will trigger a kernel panic. Support for > sanitisers, including kcfi (CFI_CLANG), is in the works, but for now > they're nightly-only options in rustc. Make RUST depend on !CFI_CLANG > to prevent configuring a kernel without symmetrical support for kfi. > > Fixes: 2f7ab1267dc9 ("Kbuild: add Rust support") > cc: stable@vger.kernel.org > Signed-off-by: Conor Dooley <conor.dooley@microchip.com> Acked-by: Nathan Chancellor <nathan@kernel.org> It seems like this won't be forgotten about but if there is not already an issue open for this somewhere, it would be good to have one, since we obviously want this for both C and Rust code. As a general meta comment not directed at anyone in particualr, I think these 'depends on !' should all have some sort of comment or description as to why they are disabled. I can infer from most of them but it would still be good to be explicit, especially since someone might want to work on fixing the ones that are due to missing support and such. > --- > Sending this one on its own, there's no explicit dep on this for the > riscv enabling patch, v3 to continue the numbering from there. Nothing > has changed since v2. > > CC: Miguel Ojeda <ojeda@kernel.org> > CC: Alex Gaynor <alex.gaynor@gmail.com> > CC: Wedson Almeida Filho <wedsonaf@gmail.com> > CC: linux-kernel@vger.kernel.org (open list) > CC: rust-for-linux@vger.kernel.org > CC: Sami Tolvanen <samitolvanen@google.com> > CC: Kees Cook <keescook@chromium.org> > CC: Nathan Chancellor <nathan@kernel.org> > CC: llvm@lists.linux.dev > --- > init/Kconfig | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/init/Kconfig b/init/Kconfig > index aa02aec6aa7d..ad9a2da27dc9 100644 > --- a/init/Kconfig > +++ b/init/Kconfig > @@ -1899,6 +1899,7 @@ config RUST > bool "Rust support" > depends on HAVE_RUST > depends on RUST_IS_AVAILABLE > + depends on !CFI_CLANG > depends on !MODVERSIONS > depends on !GCC_PLUGINS > depends on !RANDSTRUCT > -- > 2.43.0 > >
WARNING: multiple messages have this Message-ID (diff)
From: Nathan Chancellor <nathan@kernel.org> To: Conor Dooley <conor@kernel.org> Cc: linux-riscv@lists.infradead.org, Conor Dooley <conor.dooley@microchip.com>, stable@vger.kernel.org, Miguel Ojeda <ojeda@kernel.org>, Alex Gaynor <alex.gaynor@gmail.com>, Wedson Almeida Filho <wedsonaf@gmail.com>, linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org, Sami Tolvanen <samitolvanen@google.com>, Kees Cook <keescook@chromium.org>, llvm@lists.linux.dev Subject: Re: [PATCH v3] rust: make mutually exclusive with CFI_CLANG Date: Thu, 4 Apr 2024 08:32:58 -0700 [thread overview] Message-ID: <20240404153258.GA852748@dev-arch.thelio-3990X> (raw) In-Reply-To: <20240404-providing-emporium-e652e359c711@spud> On Thu, Apr 04, 2024 at 03:17:02PM +0100, Conor Dooley wrote: > From: Conor Dooley <conor.dooley@microchip.com> > > On RISC-V and arm64, and presumably x86, if CFI_CLANG is enabled, > loading a rust module will trigger a kernel panic. Support for > sanitisers, including kcfi (CFI_CLANG), is in the works, but for now > they're nightly-only options in rustc. Make RUST depend on !CFI_CLANG > to prevent configuring a kernel without symmetrical support for kfi. > > Fixes: 2f7ab1267dc9 ("Kbuild: add Rust support") > cc: stable@vger.kernel.org > Signed-off-by: Conor Dooley <conor.dooley@microchip.com> Acked-by: Nathan Chancellor <nathan@kernel.org> It seems like this won't be forgotten about but if there is not already an issue open for this somewhere, it would be good to have one, since we obviously want this for both C and Rust code. As a general meta comment not directed at anyone in particualr, I think these 'depends on !' should all have some sort of comment or description as to why they are disabled. I can infer from most of them but it would still be good to be explicit, especially since someone might want to work on fixing the ones that are due to missing support and such. > --- > Sending this one on its own, there's no explicit dep on this for the > riscv enabling patch, v3 to continue the numbering from there. Nothing > has changed since v2. > > CC: Miguel Ojeda <ojeda@kernel.org> > CC: Alex Gaynor <alex.gaynor@gmail.com> > CC: Wedson Almeida Filho <wedsonaf@gmail.com> > CC: linux-kernel@vger.kernel.org (open list) > CC: rust-for-linux@vger.kernel.org > CC: Sami Tolvanen <samitolvanen@google.com> > CC: Kees Cook <keescook@chromium.org> > CC: Nathan Chancellor <nathan@kernel.org> > CC: llvm@lists.linux.dev > --- > init/Kconfig | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/init/Kconfig b/init/Kconfig > index aa02aec6aa7d..ad9a2da27dc9 100644 > --- a/init/Kconfig > +++ b/init/Kconfig > @@ -1899,6 +1899,7 @@ config RUST > bool "Rust support" > depends on HAVE_RUST > depends on RUST_IS_AVAILABLE > + depends on !CFI_CLANG > depends on !MODVERSIONS > depends on !GCC_PLUGINS > depends on !RANDSTRUCT > -- > 2.43.0 > > _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2024-04-04 15:33 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-04-04 14:17 [PATCH v3] rust: make mutually exclusive with CFI_CLANG Conor Dooley 2024-04-04 14:17 ` Conor Dooley 2024-04-04 14:33 ` Miguel Ojeda 2024-04-04 14:33 ` Miguel Ojeda 2024-04-04 15:25 ` Matthew Maurer 2024-04-04 15:25 ` Matthew Maurer 2024-04-04 15:55 ` Conor Dooley 2024-04-04 15:55 ` Conor Dooley 2024-04-04 17:47 ` Miguel Ojeda 2024-04-04 17:47 ` Miguel Ojeda 2024-04-04 15:32 ` Nathan Chancellor [this message] 2024-04-04 15:32 ` Nathan Chancellor 2024-04-04 18:42 ` Miguel Ojeda 2024-04-04 18:42 ` Miguel Ojeda 2024-04-04 22:41 ` Ramon de C Valle 2024-04-04 22:41 ` Ramon de C Valle [not found] ` <CAOcBZOTuqzwQncS8rMUMoOj3zE+FnLxPY6O=4EEaOP2xuFG9Vg@mail.gmail.com> 2024-04-05 10:30 ` Miguel Ojeda 2024-04-05 10:30 ` Miguel Ojeda 2024-04-07 20:02 ` Miguel Ojeda 2024-04-07 20:02 ` Miguel Ojeda
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=20240404153258.GA852748@dev-arch.thelio-3990X \ --to=nathan@kernel.org \ --cc=alex.gaynor@gmail.com \ --cc=conor.dooley@microchip.com \ --cc=conor@kernel.org \ --cc=keescook@chromium.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=llvm@lists.linux.dev \ --cc=ojeda@kernel.org \ --cc=rust-for-linux@vger.kernel.org \ --cc=samitolvanen@google.com \ --cc=stable@vger.kernel.org \ --cc=wedsonaf@gmail.com \ /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: linkBe 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.