Searched refs:i_mutex (Results 1 – 6 of 6) sorted by relevance
122 ->link() callers hold ->i_mutex on the object we are linking to. Some of your150 ->setattr() is called without BKL now. Caller _always_ holds ->i_mutex, so151 watch for ->i_mutex-grabbing code that might be used by your ->setattr().152 Callers of notify_change() need ->i_mutex now.478 You must also keep in mind that ->fsync() is not called with i_mutex held479 anymore, so if you require i_mutex locking you must make sure to take it and669 ->i_mutex is replaced with ->i_rwsem now. inode_lock() et.al. work as
89 such that any local locking will be done with the i_mutex as required
324 very least because i_mutex needs to be grabbed, and objects allocated.
646 inode's i_mutex.
213 struct mutex i_mutex; member
7084 mutex_unlock(&path.dentry->d_inode->i_mutex);