All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Qi <joseph.qi@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: retry once dlm_dispatch_assert_master failed with ENOMEM
Date: Fri, 4 Apr 2014 10:06:42 +0800	[thread overview]
Message-ID: <533E13B2.5060108@huawei.com> (raw)
In-Reply-To: <533E0A39.9020001@oracle.com>

Thanks for your advice.
I thought about returning DLM_LOCK_RES_OWNER_UNKNOWN, but it would
result in confusion at message sender.
I'll take your idea of retrying 3 times and then resend this patch.

On 2014/4/4 9:26, Wengang wrote:
> O2net is using a single threaded work queue to process network requests.
> Blocking in a handler would block whole network processing.
> As you see, the memory allocation is with GFP_NOFS, if the first try
> failed, the following retries may still fail. Thus it could block a
> while which is not good.
> 
> How about to limit the retries, say, 3 or 5 times. If it still failed to
> get memory, return an error to peer and peer decides to retry or give up.
> 
> thanks,
> wengang
> 
> ? 2014?04?03? 20:45, Joseph Qi ??:
>> Once dlm_dispatch_assert_master failed in dlm_master_requery_handler,
>> the only reason is ENOMEM. So just retry it instead of BUG().
>>
>> Signed-off-by: Joseph Qi <joseph.qi@huawei.com>
>> ---
>>   fs/ocfs2/dlm/dlmrecovery.c | 11 ++++++++---
>>   1 file changed, 8 insertions(+), 3 deletions(-)
>>
>> diff --git a/fs/ocfs2/dlm/dlmrecovery.c b/fs/ocfs2/dlm/dlmrecovery.c
>> index 7035af0..f772d64 100644
>> --- a/fs/ocfs2/dlm/dlmrecovery.c
>> +++ b/fs/ocfs2/dlm/dlmrecovery.c
>> @@ -1685,6 +1685,7 @@ int dlm_master_requery_handler(struct o2net_msg
>> *msg, u32 len, void *data,
>>         hash = dlm_lockid_hash(req->name, req->namelen);
>>   +retry:
>>       spin_lock(&dlm->spinlock);
>>       res = __dlm_lookup_lockres(dlm, req->name, req->namelen, hash);
>>       if (res) {
>> @@ -1693,10 +1694,14 @@ int dlm_master_requery_handler(struct
>> o2net_msg *msg, u32 len, void *data,
>>           if (master == dlm->node_num) {
>>               int ret = dlm_dispatch_assert_master(dlm, res,
>>                                    0, 0, flags);
>> +            /* ENOMEM returns, just retry */
>>               if (ret < 0) {
>> -                mlog_errno(-ENOMEM);
>> -                /* retry!? */
>> -                BUG();
>> +                spin_unlock(&res->spinlock);
>> +                dlm_lockres_put(res);
>> +                spin_unlock(&dlm->spinlock);
>> +                mlog_errno(ret);
>> +                msleep(50);
>> +                goto retry;
>>               }
>>           } else /* put.. incase we are not the master */
>>               dlm_lockres_put(res);
> 
> 
> 

      reply	other threads:[~2014-04-04  2:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-03 12:45 [Ocfs2-devel] [PATCH] ocfs2: retry once dlm_dispatch_assert_master failed with ENOMEM Joseph Qi
2014-04-04  1:26 ` Wengang
2014-04-04  2:06   ` Joseph Qi [this message]

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=533E13B2.5060108@huawei.com \
    --to=joseph.qi@huawei.com \
    --cc=ocfs2-devel@oss.oracle.com \
    /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.