Home
last modified time | relevance | path

Searched refs:LOG_INODE_EXISTS (Results 1 - 2 of 2) sorted by relevance

/kernel/linux/linux-5.10/fs/btrfs/
H A Dtree-log.c27 * LOG_INODE_EXISTS means to log just enough to recreate the inode
32 LOG_INODE_EXISTS, enumerator
4048 inode_only == LOG_INODE_EXISTS, in copy_items()
5025 * lock as long as we log with the LOG_INODE_EXISTS mode. We in log_conflicting_inodes()
5300 inode_only >= LOG_INODE_EXISTS)) in btrfs_log_inode()
5331 inode_only = LOG_INODE_EXISTS; in btrfs_log_inode()
5358 if (inode_only == LOG_INODE_EXISTS) in btrfs_log_inode()
5362 if (inode_only == LOG_INODE_EXISTS) { in btrfs_log_inode()
5382 if (inode_only == LOG_INODE_EXISTS) { in btrfs_log_inode()
5400 inode_only == LOG_INODE_EXISTS) { in btrfs_log_inode()
[all...]
/kernel/linux/linux-6.6/fs/btrfs/
H A Dtree-log.c39 * LOG_INODE_EXISTS means to log just enough to recreate the inode
44 LOG_INODE_EXISTS, enumerator
4481 inode_only == LOG_INODE_EXISTS, in copy_items()
5354 * 1) For regular files we log with a mode of LOG_INODE_EXISTS. It's possible
5416 int log_mode = LOG_INODE_EXISTS; in log_new_dir_dentries()
5585 * LOG_INODE_EXISTS mode) and slow down other fsyncs or transaction in add_conflicting_inode()
5667 * inode in LOG_INODE_EXISTS mode and rename operations update the log, in add_conflicting_inode()
5743 * might have been logged in LOG_INODE_EXISTS mode or in log_conflicting_inodes()
5758 * the inode in LOG_INODE_EXISTS mode and rename operations in log_conflicting_inodes()
5773 * lock as long as we log with the LOG_INODE_EXISTS mod in log_conflicting_inodes()
[all...]

Completed in 14 milliseconds