Lines Matching full:filesystem

9  *                                   - filesystem drivers list
217 * prune the icache, followed by the filesystem specific caches in super_cache_scan()
247 * rwsem does not protect filesystem operations backing in super_cache_count()
253 * filesystem might be in a state of partial construction and hence it in super_cache_count()
310 * @type: filesystem type superblock should belong to
552 * filesystem is not shut down while we are working on it. It returns
554 * filesystem already got into shutdown, and returns true with the s_umount
614 * Upon calling this function, the filesystem may no longer alter or
704 * @fc: Filesystem context.
717 * (1) the namespace the filesystem context @fc and the extant
720 * (2) the filesystem context @fc has requested that reusing an extant
745 * not set, as the filesystem is likely unprepared to handle it. in sget_fc()
799 warnfc(fc, "reusing existing filesystem not allowed"); in sget_fc()
801 warnfc(fc, "reusing existing filesystem in another namespace not allowed"); in sget_fc()
813 * @type: filesystem type superblock should belong to
1014 * reconfigure_super - asks filesystem to change superblock parameters
1073 * Protect filesystem's reconfigure code from writes from in reconfigure_super()
1098 * mappings. So If we try to mount readonly then copy the filesystem in reconfigure_super()
1162 * emergency_thaw_all -- forcibly thaw every frozen filesystem
1387 * @fc: Filesystem context.
1513 * fs_bdev_freeze - freeze owning filesystem of block device
1516 * Freeze the filesystem that owns this block device if it is still
1519 * A filesystem that owns multiple block devices may be frozen from each
1521 * unfrozen. Each block device can only freeze the filesystem once as we
1551 * fs_bdev_thaw - thaw owning filesystem of block device
1554 * Thaw the filesystem that owns this block device.
1556 * A filesystem that owns multiple block devices may be frozen from each
1558 * unfrozen. Each block device can only freeze the filesystem once as we
1563 * returns zero it doesn't mean that the filesystem is unfrozen
1576 * filesystem. Concurrently another process might try to mount that in fs_bdev_thaw()
1658 * @fc: The filesystem context holding the parameters
1710 * @fc: The filesystem context holding the parameters
1739 * The filesystem is invoked to get or create a superblock which can then later
1740 * be used for mounting. The filesystem places a pointer to the root to be
1759 pr_err("Filesystem %s get_tree() didn't set fc->root, returned %i\n", in vfs_get_tree()
2015 * freeze_super - lock the filesystem and force it into a consistent state
2020 * Syncs the super to make sure the filesystem is consistent and calls the fs's
2030 * freeze the filesystem. Although there cannot be multiple kernel freezes or
2032 * userspace can both hold a filesystem frozen. The filesystem remains frozen
2035 * A filesystem may hold multiple devices and thus a filesystems may be
2038 * FREEZE_MAY_NEST. The filesystem remains frozen until all block
2051 * but internal fs threads can still modify the filesystem (although they
2053 * for all running page faults we sync the filesystem which will clean all
2061 * internal writers are finished we call ->freeze_fs() to finish filesystem
2131 /* Now wait for internal filesystem counter */ in freeze_super()
2139 "VFS:Filesystem freeze failed\n"); in freeze_super()
2162 * Undoes the effect of a freeze_super_locked call. If the filesystem is
2165 * filesystem.
2197 pr_err("VFS: Filesystem thaw failed\n"); in thaw_super_locked()
2218 * thaw_super -- unlock filesystem
2223 * Unlocks the filesystem and marks it writeable again after freeze_super()
2224 * if there are no remaining freezes on the filesystem.
2231 * A filesystem may hold multiple devices and thus a filesystems may
2233 * The filesystem remains frozen until all block devices are unfrozen.