Rust CI wanted features & bugfixes

[ojeda]

Features that we would like to see

Required (we almost certainly want them)

Nice to have (not critical, we could workaround if needed, etc.)

Low priority (we will likely not use them in the end)

Done (stabilized, fixed, not needed anymore, etc.)

• The kernel in the Rust CI.

  • Ideally in the pre-merge CI.
  • Draft policy from RustNL: https://hackmd.io/@rustnl-2024-unconf/HkutiwyQR.
  • PR: Add Rust for Linux auto CI job rust-lang/rust#125209 (2024-06-10).
  • PR (Rust for Linux ping group - initial marker team to list members): Add a Rust for Linux marker team rust-lang/team#1457.
  • PR (Rust for Linux ping group - actual ping group): Create a triagebot ping group for Rust for Linux rust-lang/rust#125375.
  • PR (Rust for Linux ping group - docs on dev guide): Add Rust for Linux notification group entry rust-lang/rustc-dev-guide#1984.
  • PR (Rust for Linux ping group - fill marker team): Fill the Rust for Linux ping group rust-lang/team#1465.
  • PR (Rust for Linux ping group - fill marker team 2): Add Vincenzo to Rust for Linux ping group rust-lang/team#1466.
  • PR (Renamed CI job): CI: rename Rust for Linux CI job rust-lang/rust#127023.
  • PR (Documentation about policy): Add Rust for Linux integration tests documentation rust-lang/rustc-dev-guide#2004.
  • Zulip: https://rust-lang.zulipchat.com/#narrow/stream/242791-t-infra/topic/Testing.20Rust.20for.20Linux.20in.20our.20CI.

• Move RFL job forward to v6.11-rc1.

  • PR: CI: move RFL job forward to v6.11-rc1 rust-lang/rust#128322.

• Build the generated doctests and documentation.

  • PR: CI: rfl: build the generated doctests and documentation rust-lang/rust#128367.

• Add a few more tools and steps (Clippy, rustfmt, -Zunpretty=expanded).

  • PR: CI: rfl: add more tools and steps rust-lang/rust#128928.

---

Bugs that we would like to see fixed

Required (we almost certainly want them)

Nice to have (probably not critical, we could workaround if needed, etc.)

Low priority (we will likely not use them in the end)

Done (stabilized, fixed, or not needed anymore, etc.)

[keys-i]

is this done?

[ojeda]

These are meta-issues to hold live lists, i.e. they can grow over time. We could close on 0 and reopen if something gets added, but I am not sure how that would be useful.

[Conan-Kudo]

Do we test Clang + LTO alongside the other modes (Clang without LTO, GCC, etc.)?

[ojeda]

Only a single, basic built-test is done, and only for the Rust side of the kernel, at least so far. It is mainly meant to catch unintentional changes around unstable features that would break the kernel's build.