Keeping Safe Rust Safe with Galeed

Rivera, Elijah; Mergendahl, Samuel; Shrobe, Howard; Okhravi, Hamed; Burow, Nathan

doi:10.1145/3485832.3485903

Cited by 18 publications

(1 citation statement)

References 49 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Existing work on unsafe Rust mainly focuses on formal verification [17,18], bug detection [5,19] or isolation [20,21]. Our work is novel from the perspective of unsafe code replacement.…”

Section: Related Workmentioning

confidence: 99%

SafeNet: Towards mitigating replaceable unsafe Rust code via a recommendation‐based approach

Dong,

Zhang,

Cui

et al. 2024

Software Testing Verif & Rel

View full text Add to dashboard Cite

Rust is a system‐level programming language with advantages in memory safety. It ensures that any Rust programs without unsafe code should not incur undefined behaviours. However, unsafe code still plays an essential role in Rust to achieve low‐level control. Therefore, a major design pattern of Rust programs is interior unsafe, which wraps unsafe code as safe APIs and handles all undefined behaviours internally. Rust standard library already provides a rich set of safe APIs to facilitate Rust code development. Nevertheless, due to unfamiliarity with these APIs, developers may misuse unnecessary unsafe code and suffer memory‐safety risks. In this paper, we investigate an approach to mitigate replaceable unsafe code. We first analyse unsafe APIs of the Rust standard library and summarize their common usage patterns. Each pattern corresponds to one or several code samples in our knowledge base. Then, we develop an approach to automatically recognize the usage pattern and recommend corresponding code samples. Our approach leverages dataflow analysis to exclude impossible patterns and employs a BERT‐based machine learning model to find the most similar pattern among the rest. We have conducted evaluation experiments with 472 unsafe code snippets collected from GitHub projects and successfully recognized the pattern of 394 snippets. We hope our approach can assist developers in detecting unnecessary unsafe code and suggesting safe alternatives.

show abstract

“…Existing work on unsafe Rust mainly focuses on formal verification [17,18], bug detection [5,19] or isolation [20,21]. Our work is novel from the perspective of unsafe code replacement.…”

Section: Related Workmentioning

confidence: 99%

SafeNet: Towards mitigating replaceable unsafe Rust code via a recommendation‐based approach

Dong,

Zhang,

Cui

et al. 2024

Software Testing Verif & Rel

View full text Add to dashboard Cite

show abstract

On the Termination of Borrow Checking in Featherweight Rust

Payet

Pearce

Spoto

2022

Lecture Notes in Computer Science

View full text Add to dashboard Cite

A distinguished feature of the Rust programming language is its ability to deallocate dynamically-allocated data structures as soon as they go out of scope, without relying on a garbage collector. At the same time, Rust lets programmers create references, called borrows, to data structures. A static borrow checker enforces that borrows can only be used in a controlled way, so that automatic deallocation does not introduce dangling references. Featherweight Rust provides a formalisation for a subset of Rust where borrow checking is encoded using flow typing [25]. However, we have identified a source of non-termination within the calculus which arises when typing environments contain cycles between variables. In fact, it turns out that well-typed programs cannot lead to such environments -but this was not immediately obvious from the presentation. This paper defines a simplification of Featherweight Rust, more amenable to formal proofs. Then it develops a sufficient condition that forbids cycles and, hence, guarantees termination. Furthermore, it proves that this condition is, in fact, maintained by Featherweight Rust for welltyped programs.

show abstract

Detecting Cross-language Memory Management Issues in Rust

Wang

Sun³

et al. 2022

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Keeping Safe Rust Safe with Galeed

Cited by 18 publications

References 49 publications

SafeNet: Towards mitigating replaceable unsafe Rust code via a recommendation‐based approach

SafeNet: Towards mitigating replaceable unsafe Rust code via a recommendation‐based approach

On the Termination of Borrow Checking in Featherweight Rust

Detecting Cross-language Memory Management Issues in Rust

Contact Info

Product

Resources

About