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
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
