[Safe Rust] Kick off activities to safety qualify Rust code [2025-10-27]

[darkwisebear]

Participants

@PLeVasseur
@odra
@pawelrutkaq
@darkwisebear
@aschemmel-tech
@rafaeling
@bilelmoussaoui

Agenda

• Create a list of tools we think need to run to ensure code quality
• Decide on the use of guidelines for all self written Rust code
• Create (or link) issues and distribute work

Minutes

Setting the stage

• Safety qualification needed by the end of '26 for all Rust code inside S-Core
• Goal: Have a list of tools, guidelines, process improvements and activities that we plan for this qualification
• We need to leverage the already-existing structures (SCRC tooling, guidelines, liaison) for that

Collection of entities for safe Rust

Discussion on safe vs unsafe

• Unsafe code seems to require the same level of C++ (see https://rustc-dev-guide.rust-lang.org/sanitizers.html for a list of sanitizers)

Follow-up activities

• Define subsets and requirements vor various parts of the "Safety-certified Rust framework"

  • async runtime
  • libcore / libstd
  • Determine qualified targets (aarch64, x86_64?)

• async runtime

  • Code available
  • HL requirements available (https://eclipse-score.github.io/score/pr-1914/features/orchestration/docs/requirements/index.html#executor)
  • Component requirments missing (Todo: Ticket)

• Rules

  • API rules + high-level patterns: collect kind of needed rules and create tickets (Todo: Create ticket to collect rule list)
  • Lang guidelines. Decide which one to use (preferably SCRC rules) and write decision record
  • Create / reuse review template (Todo: Ticket, reuse https://eclipse-score.github.io/process_description//main/process_areas/implementation/guidance/implementation_checklist.html)
  • Decide how to treat unsafe code reviews (suggestion: Create unsafe code review team)

• Tooling

  • For coverage, clippy, cargo fmt, miri already in place (@dcalavrezo-qorix)
  • Have a look at cargo-deny and decide on its usability / necessity (Todo: Ticket)
  • Decide and introduce unit testing framework (Ticket)
    • mocking (mockall?)
    • extended asserting
  • Extend SCTF to support Rust (Todo: Talk to testing team @PiotrKorkus)
  • Make a list of available sanitizers, decide when to use (pre-merge, post-merge, only on unsafe code? --> Ticket)
  • Do TCL assessment for all selected tools and initiate qualification (if necessary --> Ticket)

• Traceability

  • Decide how to add tracing info to Rust tests (Ticket, FEO maybe has such a ticket (ask @pahmann))
  • Add external cargo.io crates to SBOM (Ticket)

• Process

  • Release note content (Already existing: https://eclipse-score.github.io/process_description/main/process_areas/release_management/guidance/release_guideline.html, Tickets for missing things from Rust side)
  • Generate rustdoc and put somewhere (Ticket)
  • Decide where to put the tailored guidelines (Tickets)
  • Commit to process training for all Rust developers (Ticket)

--> Suggest to form a small team tackling this, suggest to Tech Lead circle (@darkwisebear will suggest to @antonkri)

[pawelrutkaq]

The scope of dicussion is transfered to project Rust certification (view) and progress will be visible there

[FScholPer]

@pawelrutkaq do you have ideas where to discuss the topic in a regular manner(rust meeting wednesday...)?