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

jewel: librbd: potential concurrent event processing during journal replay #9040

Merged
merged 3 commits into from May 10, 2016

Conversation

dillaman
Copy link

@dillaman dillaman commented May 10, 2016

Jason Dillaman added 3 commits May 10, 2016 11:58
When replaying a journal flush event, do not start processing the next
journal entry until after the flush is in progress to ensure the barrier
is correctly guarding against future writes.

Signed-off-by: Jason Dillaman <dillaman@redhat.com>
(cherry picked from commit 5d205ef)
One such example is popping the last entry from an object.  The next
object will be automatically prefetched.  When that object is received,
we do not want to alert the user that entries are available since
try_pop_front already indicated more records were available.

Fixes: http://tracker.ceph.com/issues/15755
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
(cherry picked from commit 3b8d21a)
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
(cherry picked from commit 44827a3)
@dillaman dillaman added this to the jewel milestone May 10, 2016
@dillaman dillaman merged commit 7686c62 into ceph:jewel May 10, 2016
@dillaman dillaman deleted the wip-15818 branch May 10, 2016 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant