From: Joel Becker <Joel.Becker@oracle.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH 1/2] ocfs2/lockdep: Move ip_xattr_sem out of ocfs2_xattr_get_nolock.
Date: Fri, 10 Sep 2010 09:21:41 -0700 [thread overview]
Message-ID: <20100910162141.GB17223@mail.oracle.com> (raw)
In-Reply-To: <1283837406-15685-1-git-send-email-tao.ma@oracle.com>
On Tue, Sep 07, 2010 at 01:30:05PM +0800, Tao Ma wrote:
> As the name shows, we shouldn't have any lock in
> ocfs2_xattr_get_nolock. so lift ip_xattr_sem to the caller.
> This should be safe for us since the only 2 callers are:
> 1. ocfs2_xattr_get which will lock the resources.
> 2. ocfs2_mknod which don't need this locking.
This patch is now in the fixes branch of ocfs2.git.
Joel
--
"You cannot bring about prosperity by discouraging thrift. You cannot
strengthen the weak by weakening the strong. You cannot help the wage
earner by pulling down the wage payer. You cannot further the
brotherhood of man by encouraging class hatred. You cannot help the
poor by destroying the rich. You cannot build character and courage by
taking away a man's initiative and independence. You cannot help men
permanently by doing for them what they could and should do for
themselves."
- Abraham Lincoln
Joel Becker
Consulting Software Developer
Oracle
E-mail: joel.becker at oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2010-09-10 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 5:29 [Ocfs2-devel] [PATCH 0/2] Fix 2 lockdep warning in ocfs2 Tao Ma
2010-09-07 5:30 ` [Ocfs2-devel] [PATCH 1/2] ocfs2/lockdep: Move ip_xattr_sem out of ocfs2_xattr_get_nolock Tao Ma
2010-09-10 16:21 ` Joel Becker [this message]
2010-09-07 5:30 ` [Ocfs2-devel] [PATCH 2/2] ocfs2: Fix lockdep warning in reflink Tao Ma
2010-09-10 16:21 ` Joel Becker
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=20100910162141.GB17223@mail.oracle.com \
--to=joel.becker@oracle.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.