From: Jensen <shencanquan@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] why ocfs2 quota need call ocfs2_qinfo_lock function before qtree_read_dquot or qtree_write_dquot ?
Date: Fri, 6 Sep 2013 09:50:22 +0800 [thread overview]
Message-ID: <522934DE.6070503@huawei.com> (raw)
Hi all,
I want to know why ocfs2 quota need call ocfs2_qinfo_lock function before qtree_read_dquot or
qtree_write_dquot in ocfs2_acquire_dquot function.
I think that it need not, because before ocfs2_qinfo_lock, it has ocfs2_lock_global_qf, it will
lock the global quota inode.
Thanks,
Jesen.
2013-9-6
reply other threads:[~2013-09-06 1:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=522934DE.6070503@huawei.com \
--to=shencanquan@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.