linux-kernel - Why there is no mutex_lock in vfs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <487B16FB.2040805@oracle.com>
Date:	Mon, 14 Jul 2008 17:06:03 +0800
From:	Tao Ma <tao.ma@...cle.com>
To:	linux-fsdevel@...r.kernel.org
CC:	linux-kernel@...r.kernel.org
Subject: Why there is no mutex_lock in vfs_getxattr.

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-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/