Searched refs:i_sem (Results 1 – 7 of 7) sorted by relevance
999 down_write(&F2FS_I(new_inode)->i_sem); in f2fs_rename()1003 up_write(&F2FS_I(new_inode)->i_sem); in f2fs_rename()1024 down_write(&F2FS_I(old_inode)->i_sem); in f2fs_rename()1030 up_write(&F2FS_I(old_inode)->i_sem); in f2fs_rename()1186 down_write(&F2FS_I(old_inode)->i_sem); in f2fs_cross_rename()1192 up_write(&F2FS_I(old_inode)->i_sem); in f2fs_cross_rename()1196 down_write(&F2FS_I(old_dir)->i_sem); in f2fs_cross_rename()1198 up_write(&F2FS_I(old_dir)->i_sem); in f2fs_cross_rename()1205 down_write(&F2FS_I(new_inode)->i_sem); in f2fs_cross_rename()1211 up_write(&F2FS_I(new_inode)->i_sem); in f2fs_cross_rename()[all …]
711 down_write(&F2FS_I(inode)->i_sem); in f2fs_add_regular_entry()738 up_write(&F2FS_I(inode)->i_sem); in f2fs_add_regular_entry()803 down_write(&F2FS_I(inode)->i_sem); in f2fs_do_tmpfile()814 up_write(&F2FS_I(inode)->i_sem); in f2fs_do_tmpfile()822 down_write(&F2FS_I(inode)->i_sem); in f2fs_drop_nlink()833 up_write(&F2FS_I(inode)->i_sem); in f2fs_drop_nlink()
620 down_write(&F2FS_I(inode)->i_sem); in f2fs_add_inline_entry()649 up_write(&F2FS_I(inode)->i_sem); in f2fs_add_inline_entry()
234 down_write(&fi->i_sem); in try_to_fix_pino()240 up_write(&fi->i_sem); in try_to_fix_pino()304 down_read(&F2FS_I(inode)->i_sem); in f2fs_do_sync_file()306 up_read(&F2FS_I(inode)->i_sem); in f2fs_do_sync_file()
1041 init_rwsem(&fi->i_sem); in f2fs_alloc_inode()
773 struct rw_semaphore i_sem; /* protect fi info */ member
43 This is the JFFS2-internal equivalent of the inode mutex i->i_sem.48 The reason that the i_sem itself isn't used for this purpose is to49 avoid deadlocks with garbage collection -- the VFS will lock the i_sem53 VFS. If the garbage collection code were to attempt to lock the i_sem55 lead to deadlock, unless we played games with unlocking the i_sem