-
Notifications
You must be signed in to change notification settings - Fork 88
Fix: symbolic locksets use may-equality when invalidating on unlock #1987
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
Draft
Copilot
wants to merge
4
commits into
master
Choose a base branch
from
copilot/fix-symbolic-locksets-invalidations
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+23
−6
Draft
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
2a00bca
Initial plan
Copilot 50a66e0
Fix: Use may-equality (MayPointTo) when removing locks during unlock …
Copilot 81076a5
Remove TODO from 30-symb_lockset_mayunlock.c: race is now detected wi…
Copilot b430e2c
Use semantic_equal directly for AddrOf(Var) lockset elements in Symbo…
Copilot File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder what the purpose of
stripCastsDeepForPtrArithwas because it's now removed fromremove.It's still in
addthough. I don't immediately know if this mismatch/removal can cause any problems.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
stripCastsDeepForPtrArithinaddwas used to normalize expressions fromeq_setbefore syntactic comparison with lockset elements. Inremove, we now useMayPointTowhich evaluates expressions through the abstract domain and handles casts semantically, so the explicit cast-stripping is no longer needed. Added a comment in b430e2c explaining this.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@copilot: Why is is still used in
addthen?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
EqualSetquery (implemented invarEq.ml) wraps every returned expression inCastE (Internal, et, ...)(seevarEq.ml:548). SostripCastsDeepForPtrArithinaddis needed to peel those cast wrappers before theAddrOf _syntactic filter can recognize the lock addresses to store.In
remove, we useMayPointToinstead, which evaluates through the abstract value domain — casts are handled semantically there, so no explicit stripping is needed.