Linux ocfs2 filesystem development
 help / color / mirror / Atom feed
From: Joseph Qi <joseph.qi@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] A deadlock when system do not has sufficient memory
Date: Mon, 25 Aug 2014 13:41:45 +0800	[thread overview]
Message-ID: <53FACC99.8070701@huawei.com> (raw)
In-Reply-To: <CAEeiSHWiPZHKC5gwLTuuZAm3xUeGT48BLNs97qdUgZSMM+AFZQ@mail.gmail.com>

On 2014/8/25 13:00, Sunil Mushran wrote:
> Functions in dlmdomain.c are only triggered during mount. So they cannot trigger the deadlock as described above in this thread. I would leave them as is.
> 
It is possible if mounts multiple volumes on each node.

> On Aug 24, 2014 7:06 PM, "Xue jiufei" <xuejiufei at huawei.com <mailto:xuejiufei@huawei.com>> wrote:
> 
>     Hi Sunil,
>     On 2014/8/23 1:08, Sunil Mushran wrote:
>     > Allocs made via GFP_NOFS, by definition, should not trigger any reclaim from the fs.
>     > So this situation should never arise. That's why all allocs in the dlm have NOFS.
>     >
>     Thanks for your reply. I haven't noticed that before. So I think
>     dlm_query_region_handler() should also use GFP_NOFS instead of GFP_KERNEL,
>     right?
> 
>     Thanks.
>     Xuejiufei
>     >
>     > _______________________________________________
>     > Ocfs2-devel mailing list
>     > Ocfs2-devel at oss.oracle.com <mailto:Ocfs2-devel@oss.oracle.com>
>     > https://oss.oracle.com/mailman/listinfo/ocfs2-devel
>     >
> 
> 
> 
> 
> _______________________________________________
> Ocfs2-devel mailing list
> Ocfs2-devel at oss.oracle.com
> https://oss.oracle.com/mailman/listinfo/ocfs2-devel
> 

  reply	other threads:[~2014-08-25  5:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20  3:57 [Ocfs2-devel] A deadlock when system do not has sufficient memory Xue jiufei
2014-08-22  8:30 ` Xue jiufei
2014-08-22 17:08   ` Sunil Mushran
2014-08-25  2:05     ` Xue jiufei
2014-08-25  5:00       ` Sunil Mushran
2014-08-25  5:41         ` Joseph Qi [this message]
2014-08-25  5:45           ` Sunil Mushran
2014-08-25  6:05             ` Joseph Qi
2014-08-25 17:13               ` Sunil Mushran
2014-08-27  1:57                 ` Xue jiufei
2014-08-28  1:16                   ` Sunil Mushran
2014-08-25  1:50   ` Junxiao Bi
2014-08-28  8:16     ` Xue jiufei
2014-08-29  3:26       ` Junxiao Bi
2014-08-29  7:22         ` Xue jiufei
2014-08-29  7:30           ` Junxiao Bi

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=53FACC99.8070701@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox