* Why there is no mutex_lock in vfs_getxattr.
@ 2008-07-14 9:06 Tao Ma
0 siblings, 0 replies; only message in thread
From: Tao Ma @ 2008-07-14 9:06 UTC (permalink / raw)
To: linux-fsdevel; +Cc: linux-kernel
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
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2008-07-14 9:06 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-07-14 9:06 Why there is no mutex_lock in vfs_getxattr Tao Ma
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).