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.

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

librbd: start perf counters after id is initialized #6494

Merged
merged 1 commit into from Nov 9, 2015

Conversation

trociny
Copy link
Contributor

@trociny trociny commented Nov 7, 2015

So the perf counters section name has non-empty id.

Fixes: #13720
Signed-off-by: Mykola Golub mgolub@mirantis.com

So the perf counters section name has non-empty id.

Fixes: ceph#13720
Signed-off-by: Mykola Golub <mgolub@mirantis.com>
@dillaman
Copy link

dillaman commented Nov 9, 2015

lgtm

dillaman pushed a commit that referenced this pull request Nov 9, 2015
librbd: start perf counters after id is initialized

Reviewed-by: Jason Dillaman <dillaman@redhat.com>
@dillaman dillaman merged commit 1279053 into ceph:master Nov 9, 2015
@trociny
Copy link
Contributor Author

trociny commented Nov 10, 2015

Unfortunately, it looks this change causes crush when opening e.g. nonexistent image, because ictx->init() returns earlier than perf counters are started, and on unsuccessful init() we still do close_image(), which calls flush():

#0  PerfCounters::inc (this=0x0, idx=26010, amt=1) at common/perf_counters.cc:142
#1  0x00007ffff5437912 in librbd::flush (ictx=0x555557887630) at librbd/internal.cc:3814
#2  0x00007ffff5437fa5 in librbd::close_image (ictx=ictx@entry=0x555557887630) at librbd/internal.cc:3119
#3  0x00007ffff543ffb7 in librbd::open_image (ictx=0x555557887630) at librbd/internal.cc:3094
#4  0x00007ffff53c72b0 in librbd::RBD::open_read_only (this=0x7fffffffcd6b, io_ctx=..., image=..., name=0x555557879350 "xxx", 
    snap_name=0x0) at librbd/librbd.cc:265

It looks like we have some problems with loic-bot because I don't see it was running for this pr?

@dillaman
Copy link

@trociny This should have been fixed on master -- see ticket 13740 / PR #6523

@trociny
Copy link
Contributor Author

trociny commented Nov 10, 2015

@dillaman thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants