Searched refs:I_FREEING (Results 1 - 18 of 18) sorted by relevance
/linux-master/fs/ |
H A D | drop_caches.c | 31 if ((inode->i_state & (I_FREEING|I_WILL_FREE|I_NEW)) ||
|
H A D | inode.c | 458 if (inode->i_state & (I_DIRTY_ALL | I_SYNC | I_FREEING | I_WILL_FREE)) 625 BUG_ON(!(inode->i_state & I_FREEING)); 629 inode->i_state = I_FREEING | I_CLEAR; 638 * An inode must already be marked I_FREEING so that we avoid the inode being 643 * the cache. This should occur atomically with setting the I_FREEING state 650 BUG_ON(!(inode->i_state & I_FREEING)); 661 * the inode has I_FREEING set, flusher thread won't start new work on 679 BUG_ON(inode->i_state != (I_FREEING | I_CLEAR)); 726 if (inode->i_state & (I_NEW | I_FREEING | I_WILL_FREE)) { 731 inode->i_state |= I_FREEING; [all...] |
H A D | fs-writeback.c | 124 WARN_ON_ONCE(inode->i_state & I_FREEING); 309 WARN_ON_ONCE(inode->i_state & I_FREEING); 410 * Once I_FREEING or I_WILL_FREE are visible under i_lock, the eviction 413 if (unlikely(inode->i_state & (I_FREEING | I_WILL_FREE))) 565 inode->i_state & (I_WB_SWITCH | I_FREEING | I_WILL_FREE) || 1181 WARN_ON_ONCE(inode->i_state & I_FREEING); 1353 if (inode->i_state & I_FREEING) { 1566 if (inode->i_state & I_FREEING) 1731 * to the inode, or the inode must have I_WILL_FREE or I_FREEING set. 1741 WARN_ON(!(inode->i_state & (I_WILL_FREE|I_FREEING))); [all...] |
H A D | dcache.c | 1009 // used without having I_FREEING set, which means no aliases left 1010 if (likely(!(inode->i_state & I_FREEING) && !hlist_empty(l))) {
|
/linux-master/fs/ext4/ |
H A D | orphan.c | 110 WARN_ON_ONCE(!(inode->i_state & (I_NEW | I_FREEING)) && 239 WARN_ON_ONCE(!(inode->i_state & (I_NEW | I_FREEING)) &&
|
H A D | inode.c | 199 * the inode. Flush worker is ignoring it because of I_FREEING flag but 4089 if (!(inode->i_state & (I_NEW|I_FREEING)))
|
/linux-master/fs/notify/ |
H A D | fsnotify.c | 45 * We cannot __iget() an inode in state I_FREEING, 50 if (inode->i_state & (I_FREEING|I_WILL_FREE|I_NEW)) {
|
/linux-master/include/trace/events/ |
H A D | writeback.h | 19 {I_FREEING, "I_FREEING"}, \
|
/linux-master/fs/crypto/ |
H A D | keyring.c | 902 if (inode->i_state & (I_FREEING | I_WILL_FREE | I_NEW)) {
|
/linux-master/security/landlock/ |
H A D | fs.c | 1078 * Checks I_FREEING and I_WILL_FREE to protect against a race 1084 if (inode->i_state & (I_FREEING | I_WILL_FREE | I_NEW)) {
|
/linux-master/block/ |
H A D | bdev.c | 1142 if (inode->i_state & (I_FREEING|I_WILL_FREE|I_NEW) ||
|
/linux-master/include/linux/ |
H A D | fs.h | 2301 * until that flag is cleared. I_WILL_FREE, I_FREEING and I_CLEAR are set at 2326 * Inodes in I_WILL_FREE, I_FREEING or I_CLEAR state can 2331 * is zero. I_FREEING must be set when I_WILL_FREE is 2333 * I_FREEING Set when inode is about to be freed but still has dirty 2337 * clean and can be destroyed. Inode keeps I_FREEING. 2339 * Inodes that are I_WILL_FREE, I_FREEING or I_CLEAR are 2372 * Q: What is the difference between I_WILL_FREE and I_FREEING? 2380 #define I_FREEING (1 << 5) macro 2423 I_FREEING | I_WILL_FREE)) == I_DIRTY_TIME;
|
/linux-master/fs/xfs/ |
H A D | xfs_bmap_util.c | 511 if (!(VFS_I(ip)->i_state & I_FREEING))
|
/linux-master/fs/gfs2/ |
H A D | ops_fstype.c | 1758 if ((inode->i_state & (I_FREEING|I_WILL_FREE|I_NEW)) &&
|
/linux-master/fs/quota/ |
H A D | dquot.c | 1033 if ((inode->i_state & (I_FREEING|I_WILL_FREE|I_NEW)) ||
|
/linux-master/fs/bcachefs/ |
H A D | fs.c | 1596 !(inode->v.i_state & I_FREEING) &&
|
/linux-master/fs/btrfs/ |
H A D | inode.c | 5148 ASSERT(inode->i_state & I_FREEING); 5526 (I_WILL_FREE | I_FREEING))); 8010 int inode_evicting = inode->vfs_inode.i_state & I_FREEING;
|
/linux-master/fs/nfs/ |
H A D | pnfs.c | 323 if (i_state & (I_FREEING | I_CLEAR))
|
Completed in 250 milliseconds