Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RDMA Soundness Scope #76

Open
Nugine opened this issue Jun 11, 2022 · 0 comments
Open

RDMA Soundness Scope #76

Nugine opened this issue Jun 11, 2022 · 0 comments

Comments

@Nugine
Copy link
Contributor

Nugine commented Jun 11, 2022

It is impossible to prevent an incorrect remote process from triggering UB in the local process.
Like mmap and /proc/self/mem, such a situation is out of the control of Rust language.

There are two solutions:

  • Document the behavior and remove it from soundness concerns.
    Like Document Rust's stance on /proc/self/mem rust-lang/rust#97837
  • Put an unsafe function on the way from network connections to active RDMA connections.
    The function means "trust the remote process" while it is impossible to check whether the remote process is correct actually.

Timeout from single side is still unsound because UB may happen when system time goes back.

Related:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant