-
Notifications
You must be signed in to change notification settings - Fork 1.1k
When the lock timer creation fails, delete lock_obj #4604
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
base: devel
Are you sure you want to change the base?
Conversation
|
@atinmu @sanjurakonde |
c236f8b to
5d2e8f6
Compare
| gf_msg(this->name, GF_LOG_ERROR, 0, GD_MSG_DICT_SET_FAILED, | ||
| "Unable to set timer in mgmt_v3 lock"); | ||
| keylen = strlen(key_dup); | ||
| dict_deln(priv->mgmt_v3_lock, key_dup, keylen); |
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.
Shouldn't you also free 'lock_obj' ?
nit: the whole keylen and such and using dict_deln() - you could just use dict_del()
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.
@mykaul I have made modifications based on the suggestions. Please review it again.
Thanks!
Signed-off-by: 10255046 <wu.shiwei@zte.com.cn>
|
I will take a look when I get some time. Bit busy with one migration at work. Will take a while. |
When the lock timer creation fails, we may delete lock_obj. To prevent permanent occupation by lock owners
Fixes: #4603