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
test/fio: fix global CephContext life cycle #12245
Conversation
the difference between your change to the fio engine is correct though |
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.
f6ea4d5
to
c139e9b
Compare
oops, dropped another commit.. |
Signed-off-by: Igor Fedotov <ifedotov@mirantis.com>
c139e9b
to
212294a
Compare
fixed. |
@tchaikov would you approve? |
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.
lgtm =)
It looks like that's a bad idea to omit add_ref when returning intrusive_ptr from global_init. Assigning temporary resulting pointer to another var doesn't increment ref counter. From the boost manual - this is equivalent to swap call instead. Hence we might have either lack of CephContext release or its' premature release. The latter case I observed in fio plugin.
Consider the following code snippet:
Corresponding output: