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.

Sign up for GitHub

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

Jump to bottom

RUSTSEC-2020-0070: Some lock_api lock guard objects can cause data races #8

Open
github-actions bot opened this issue Jul 4, 2024 · 0 comments
Open

RUSTSEC-2020-0070: Some lock_api lock guard objects can cause data races #8

github-actions bot opened this issue Jul 4, 2024 · 0 comments

Comments

@github-actions
Copy link

github-actions bot commented Jul 4, 2024

Some lock_api lock guard objects can cause data races

Details
Status unsound
Package lock_api
Version 0.3.4
URL Amanieu/parking_lot#262
Date 2020-11-08

Affected versions of lock_api had unsound implementations of the Send or
Sync traits for some guard objects, namely:

  • MappedMutexGuard
  • MappedRwLockReadGuard
  • MappedRwLockWriteGuard
  • RwLockReadGuard
  • RwLockWriteGuard

These guards could allow data races through types that are not safe to Send
across thread boundaries in safe Rust code.

This issue was fixed by changing the trait bounds on the Mapped guard types
and removing the Sync trait for the RwLock guards.

See advisory page for additional details.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
0 participants