rust-lang / rust-lang/rust

Tracking issue for reviewing and moving sanitizers into a compiler crate (i.e., `rustc_sanitizers`)

Open
#123,619 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-sanitizers C-tracking-issue PG-exploit-mitigations
Dominant language
Rust
Stars
119k
Forks
16.2k
PR merge metrics
PR metrics pending

Description

This is a tracking issue for reviewing previously-added support for sanitizers to the Rust compiler, and moving and organizing as much as possible of the sanitizers source code into a compiler crate (i.e., rustc_sanitizers). This is part of our work to organize and stabilize support for the sanitizers. (See our roadmap at https://hackmd.io/@rcvalle/S1Ou9K6H6.)

Steps
  • Create the rustc_sanitizers compiler crate.
  • Move the source code for the CFI and KCFI sanitizers to the rustc_sanitizers crate.
  • Move common sanitizers source code, review and move other sanitizers to the rustc_sanitizers crate.
  • TBD.
Unresolved Questions

None.

Implementation history
  • #123620

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the rustc_sanitizers crate and the completed CFI/KCFI move, including implementation history in #123620. Identify the remaining common or other sanitizer sources that need review and relocation; done means the agreed sources are organized in the crate and the tracking checklist is updated.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.