From: Tao Ma <tao.ma@oracle.com>
To: linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Why there is no mutex_lock in vfs_getxattr.
Date: Mon, 14 Jul 2008 17:06:03 +0800 [thread overview]
Message-ID: <487B16FB.2040805@oracle.com> (raw)
Hi all,
When we use vfs_setxattr we call mutex_lock(&inode->i_mutex) to lock
the inode. Then why there is no mutex_lock in vfs_getxattr? Is there any
reason for it? And how can I prevent getting the stale xattr if set/get
happen in the same time? Just let the actual file system implement it
by itself?
Regards,
Tao
reply other threads:[~2008-07-14 9:06 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=487B16FB.2040805@oracle.com \
--to=tao.ma@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).