Searched refs:mnt_count (Results 1 – 6 of 6) sorted by relevance
28 int mnt_count; member51 int mnt_count; member
170 this_cpu_add(mnt->mnt_pcp->mnt_count, n); in mnt_add_count()173 mnt->mnt_count += n; in mnt_add_count()188 count += per_cpu_ptr(mnt->mnt_pcp, cpu)->mnt_count; in mnt_get_count()193 return mnt->mnt_count; in mnt_get_count()219 this_cpu_add(mnt->mnt_pcp->mnt_count, 1); in alloc_vfsmnt()221 mnt->mnt_count = 1; in alloc_vfsmnt()
79 __le16 mnt_count; member
832 int mnt_count; in nilfs_setup_super() local843 mnt_count = le16_to_cpu(sbp[0]->s_mnt_count); in nilfs_setup_super()848 } else if (max_mnt_count >= 0 && mnt_count >= max_mnt_count) { in nilfs_setup_super()855 sbp[0]->s_mnt_count = cpu_to_le16(mnt_count + 1); in nilfs_setup_super()
321 mnt->mnt_count324 ``mnt_count`` is a per-CPU reference counter on "``mount``" structures.327 it needs to check with every CPU. Taking a ``mnt_count`` reference330 ``mnt_count`` doesn't ensure that the mount remains in the namespace and,334 filesystem. So a reference through ``->mnt_count`` provides a stable347 the ``mnt_count``. Finally the value in ``mount_lock`` is checked against349 was a change, the ``mnt_count`` is decremented and the whole process is395 step. A reference through ``d_lockref`` and ``mnt_count`` is always867 For ``mnt->mnt_count`` it is safe to take a reference as long as
2764 static unsigned int mnt_count; in ext4_expand_extra_isize_ea() local2858 if (error && (mnt_count != le16_to_cpu(sbi->s_es->s_mnt_count))) { in ext4_expand_extra_isize_ea()2861 mnt_count = le16_to_cpu(sbi->s_es->s_mnt_count); in ext4_expand_extra_isize_ea()