Home
last modified time | relevance | path

Searched refs:mnt_count (Results 1 – 5 of 5) sorted by relevance

/linux-6.12.1/fs/
Dmount.h24 int mnt_count; member
47 int mnt_count; member
Dnamespace.c281 this_cpu_add(mnt->mnt_pcp->mnt_count, n); in mnt_add_count()
284 mnt->mnt_count += n; in mnt_add_count()
299 count += per_cpu_ptr(mnt->mnt_pcp, cpu)->mnt_count; in mnt_get_count()
304 return mnt->mnt_count; in mnt_get_count()
330 this_cpu_add(mnt->mnt_pcp->mnt_count, 1); in alloc_vfsmnt()
332 mnt->mnt_count = 1; in alloc_vfsmnt()
/linux-6.12.1/fs/nilfs2/
Dsuper.c808 int mnt_count; in nilfs_setup_super() local
819 mnt_count = le16_to_cpu(sbp[0]->s_mnt_count); in nilfs_setup_super()
824 } else if (max_mnt_count >= 0 && mnt_count >= max_mnt_count) { in nilfs_setup_super()
831 sbp[0]->s_mnt_count = cpu_to_le16(mnt_count + 1); in nilfs_setup_super()
/linux-6.12.1/Documentation/filesystems/
Dpath-lookup.rst321 mnt->mnt_count
324 ``mnt_count`` is a per-CPU reference counter on "``mount``" structures.
327 it needs to check with every CPU. Taking a ``mnt_count`` reference
330 ``mnt_count`` doesn't ensure that the mount remains in the namespace and,
334 filesystem. So a reference through ``->mnt_count`` provides a stable
347 the ``mnt_count``. Finally the value in ``mount_lock`` is checked against
349 was a change, the ``mnt_count`` is decremented and the whole process is
395 step. A reference through ``d_lockref`` and ``mnt_count`` is always
867 For ``mnt->mnt_count`` it is safe to take a reference as long as
/linux-6.12.1/fs/ext4/
Dxattr.c2767 static unsigned int mnt_count; in ext4_expand_extra_isize_ea() local
2861 if (error && (mnt_count != le16_to_cpu(sbi->s_es->s_mnt_count))) { in ext4_expand_extra_isize_ea()
2864 mnt_count = le16_to_cpu(sbi->s_es->s_mnt_count); in ext4_expand_extra_isize_ea()