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

Lock escalation error relaxation #22

Open
ProofOfKeags opened this issue Dec 30, 2021 · 0 comments
Open

Lock escalation error relaxation #22

ProofOfKeags opened this issue Dec 30, 2021 · 0 comments
Assignees
@Blu-J
Labels
Enhancement New feature or request P3 - Eventual Things of low consequence to ignore

Comments

@ProofOfKeags
Copy link
Contributor

Currently we ban all lock escalations:

  • E -> R
  • R -> W
  • E -> W
  • A/B -> A (regardless of lock type)

Some of these are actually safe to let through. We can benefit from relaxing the requirements to only the ones that can lead to deadlocks. This should not be done though until deadlock detection is merged. #14
@ProofOfKeags ProofOfKeags self-assigned this Dec 30, 2021
@elvece elvece added Enhancement New feature or request P3 - Eventual Things of low consequence to ignore and removed enhancement labels Jan 24, 2022
@ProofOfKeags ProofOfKeags assigned Blu-J and unassigned ProofOfKeags Jun 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Blu-J Blu-J

Labels
Enhancement New feature or request P3 - Eventual Things of low consequence to ignore
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Blu-J @ProofOfKeags @elvece