From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> To: Nathan Chancellor <nathan@kernel.org> Cc: Conor Dooley <conor@kernel.org>, 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 20:42:48 +0200 [thread overview] Message-ID: <CANiq72kSfC2j07mAaV591i4kDwejWRYcFTvASgQmNnHVe5ZwCw@mail.gmail.com> (raw) In-Reply-To: <20240404153258.GA852748@dev-arch.thelio-3990X> On Thu, Apr 4, 2024 at 5:33 PM Nathan Chancellor <nathan@kernel.org> wrote: > > Acked-by: Nathan Chancellor <nathan@kernel.org> Thanks! > 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. We track the unstable feature(s) at https://github.com/Rust-for-Linux/linux/issues/2 (I just moved this one there since it is close to ready, but it was in #355 previously, and cleaned things up a bit). On the Rust side, I think the main one is https://github.com/rust-lang/rust/issues/89653. It includes KCFI, but it is missing Matthew's PRs for KCFI etc. I added a link to get those issues/PRs (or hopefully most of them): https://github.com/rust-lang/rust/pulls?q=is%3Apr+cfi+label%3APG-exploit-mitigations+-label%3Arollup We could create an explicit/concrete issue for removing the `depends on !` when Matthew sends the patches, though. > 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. That is definitely a good idea. An alternative could be linking an issue instead (perhaps concrete ones for that, i.e. your other idea above) so that we can update the status etc. easily. Cheers, Miguel
WARNING: multiple messages have this Message-ID (diff)
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> To: Nathan Chancellor <nathan@kernel.org> Cc: Conor Dooley <conor@kernel.org>, 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 20:42:48 +0200 [thread overview] Message-ID: <CANiq72kSfC2j07mAaV591i4kDwejWRYcFTvASgQmNnHVe5ZwCw@mail.gmail.com> (raw) In-Reply-To: <20240404153258.GA852748@dev-arch.thelio-3990X> On Thu, Apr 4, 2024 at 5:33 PM Nathan Chancellor <nathan@kernel.org> wrote: > > Acked-by: Nathan Chancellor <nathan@kernel.org> Thanks! > 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. We track the unstable feature(s) at https://github.com/Rust-for-Linux/linux/issues/2 (I just moved this one there since it is close to ready, but it was in #355 previously, and cleaned things up a bit). On the Rust side, I think the main one is https://github.com/rust-lang/rust/issues/89653. It includes KCFI, but it is missing Matthew's PRs for KCFI etc. I added a link to get those issues/PRs (or hopefully most of them): https://github.com/rust-lang/rust/pulls?q=is%3Apr+cfi+label%3APG-exploit-mitigations+-label%3Arollup We could create an explicit/concrete issue for removing the `depends on !` when Matthew sends the patches, though. > 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. That is definitely a good idea. An alternative could be linking an issue instead (perhaps concrete ones for that, i.e. your other idea above) so that we can update the status etc. easily. Cheers, Miguel _______________________________________________ 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 18:43 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 2024-04-04 15:32 ` Nathan Chancellor 2024-04-04 18:42 ` Miguel Ojeda [this message] 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=CANiq72kSfC2j07mAaV591i4kDwejWRYcFTvASgQmNnHVe5ZwCw@mail.gmail.com \ --to=miguel.ojeda.sandonis@gmail.com \ --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=nathan@kernel.org \ --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.