From: Gregory Farnum <greg@inktank.com>
To: David Disseldorp <ddiss@suse.de>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: [PATCH] mds: remove waiting lock before merging with neighbours
Date: Fri, 23 Aug 2013 13:58:56 -0700 [thread overview]
Message-ID: <CAPYLRzgeWsdxyqWNRykH1Ac+TChQwFh4PKmP7D81jc89YOZJ9w@mail.gmail.com> (raw)
In-Reply-To: <1375110344-26133-1-git-send-email-ddiss@suse.de>
Hi David,
I'm really sorry it took us so long to get back to you on this. :(
However, I've reviewed the patch and, apart from going over the code
making me want to strangle myself for structuring it that way,
everything looks good. I changed the last paragraph in the commit
message very slightly to clarify the cause of the bug:
On Mon, Jul 29, 2013 at 8:05 AM, David Disseldorp <ddiss@suse.de> wrote:
> When handling a lock request, the MDS calls adjust_locks() to merge
> the new lock with available neighbours. If the new lock is merged,
> then the waiting_locks entry is not located in the subsequent
> remove_waiting() call.
> This fix ensures that the waiting_locks entry is removed prior to
> modification during merge.
When handling a lock request, the MDS calls adjust_locks() to merge
the new lock with available neighbours. If the new lock is merged,
then the waiting_locks entry is not located in the subsequent
remove_waiting() call because adjust_locks changed the new lock to
include the old locks.
This fix ensures that the waiting_locks entry is removed prior to
modification during merge.
And it's now merged into master and backported to dumpling. Thank you very much!
If you feel like cleaning up the locking code a little more (or
anything else, for that matter) I can promise you faster reviews in
the future... ;)
-Greg
Software Engineer #42 @ http://inktank.com | http://ceph.com
next prev parent reply other threads:[~2013-08-23 20:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-29 15:05 [PATCH] mds: remove waiting lock before merging with neighbours David Disseldorp
2013-08-01 12:11 ` David Disseldorp
2013-08-01 18:07 ` Sage Weil
2013-08-23 20:58 ` Gregory Farnum [this message]
2013-08-24 12:02 ` David Disseldorp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPYLRzgeWsdxyqWNRykH1Ac+TChQwFh4PKmP7D81jc89YOZJ9w@mail.gmail.com \
--to=greg@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ddiss@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.