i_flags locking

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



  Hi,

  I came across the following question: What is the proper locking for
using i_flags? I've noticed i_flags are read freely without any lock.
The modifications I've seen e.g. in ext3 were done under i_mutex. Is this
right?
  BTW it means that when checking i_flags we can see intermediate states
in ext3_set_inode_flags() when all flags are cleared and the proper flags
are not yet set, right?
  I'm currently playing with something like inotify for subtree and I'd
need to modify i_flags but using i_mutex unpleasantly interferes with
directory locking...

								Honza
-- 
Jan Kara <jack@xxxxxxx>
SuSE CR Labs
-
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

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux