-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
fix atomic_clear_long_excl wrong return #10526
Conversation
When clear a bit, we should check whether that bit is 1. BTW atomic_clear_long_excl is not used. Signed-off-by: Liu Qing <[email protected]>
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.
You're right that this doesn't seem to be used anywhere. BT_ATOMIC_CLEAR_EXCL
uses it but that is never used.
Codecov Report
@@ Coverage Diff @@
## master #10526 +/- ##
==========================================
- Coverage 79.65% 79.50% -0.15%
==========================================
Files 391 391
Lines 123887 123887
==========================================
- Hits 98684 98500 -184
- Misses 25203 25387 +184
Continue to review full report at Codecov.
|
Co-authored-by: Ryan Moeller <[email protected]>
When clearing a bit, we should check whether that bit is 0. Note atomic_clear_long_excl is not used. Reviewed-by: Brian Behlendorf <[email protected]> Reviewed-by: Ryan Moeller <[email protected]> Signed-off-by: Liu Qing <[email protected]> Closes openzfs#10526
When clearing a bit, we should check whether that bit is 0. Note atomic_clear_long_excl is not used. Reviewed-by: Brian Behlendorf <[email protected]> Reviewed-by: Ryan Moeller <[email protected]> Signed-off-by: Liu Qing <[email protected]> Closes openzfs#10526
When clear a bit, we should check whether that bit is 1.
BTW atomic_clear_long_excl is not used.
Signed-off-by: Liu Qing [email protected]
Motivation and Context
Description
How Has This Been Tested?
Types of changes
Checklist:
Signed-off-by
.