Searched refs:write_inode (Results 1 – 25 of 38) sorted by relevance
12
/linux-6.6.21/fs/9p/ |
D | vfs_super.c | 326 .write_inode = v9fs_write_inode, 337 .write_inode = v9fs_write_inode_dotl,
|
/linux-6.6.21/fs/ubifs/ |
D | file.c | 1033 err = inode->i_sb->s_op->write_inode(inode, NULL); in ubifs_writepage() 1061 err = inode->i_sb->s_op->write_inode(inode, NULL); in ubifs_writepage() 1263 err = inode->i_sb->s_op->write_inode(inode, NULL); in do_setattr() 1340 err = inode->i_sb->s_op->write_inode(inode, NULL); in ubifs_fsync()
|
D | dir.c | 1509 old_inode->i_sb->s_op->write_inode(old_inode, NULL); in do_rename()
|
/linux-6.6.21/fs/nfs/ |
D | nfs4super.c | 27 .write_inode = nfs4_write_inode,
|
D | super.c | 81 .write_inode = nfs_write_inode,
|
/linux-6.6.21/fs/sysv/ |
D | inode.c | 329 .write_inode = sysv_write_inode,
|
/linux-6.6.21/fs/ |
D | fs-writeback.c | 1467 static int write_inode(struct inode *inode, struct writeback_control *wbc) in write_inode() function 1471 if (inode->i_sb->s_op->write_inode && !is_bad_inode(inode)) { in write_inode() 1473 ret = inode->i_sb->s_op->write_inode(inode, wbc); in write_inode() 1690 int err = write_inode(inode, wbc); in __writeback_single_inode()
|
/linux-6.6.21/fs/hfs/ |
D | super.c | 177 .write_inode = hfs_write_inode,
|
/linux-6.6.21/fs/adfs/ |
D | super.c | 273 .write_inode = adfs_write_inode,
|
/linux-6.6.21/fs/bfs/ |
D | inode.c | 284 .write_inode = bfs_write_inode,
|
/linux-6.6.21/fs/orangefs/ |
D | super.c | 319 .write_inode = orangefs_write_inode,
|
/linux-6.6.21/fs/affs/ |
D | super.c | 154 .write_inode = affs_write_inode,
|
/linux-6.6.21/fs/afs/ |
D | super.c | 58 .write_inode = afs_write_inode,
|
/linux-6.6.21/fs/omfs/ |
D | inode.c | 321 .write_inode = omfs_write_inode,
|
/linux-6.6.21/Documentation/filesystems/ |
D | hpfs.rst | 229 0.91 Fixed bug that caused shooting to memory when write_inode was called on 239 Fixed a race-condition when write_inode is called while deleting file
|
D | porting.rst | 354 NOTE: checking i_nlink in the beginning of ->write_inode() and bailing out 356 may happen while the inode is in the middle of ->write_inode(); e.g. if you blindly 357 free the on-disk inode, you may end up doing that while ->write_inode() is writing
|
D | locking.rst | 167 int (*write_inode) (struct inode *, struct writeback_control *wbc); 191 write_inode:
|
/linux-6.6.21/fs/hfsplus/ |
D | super.c | 365 .write_inode = hfsplus_write_inode,
|
/linux-6.6.21/fs/exfat/ |
D | super.c | 191 .write_inode = exfat_write_inode,
|
/linux-6.6.21/fs/minix/ |
D | inode.c | 109 .write_inode = minix_write_inode,
|
/linux-6.6.21/fs/jfs/ |
D | super.c | 882 .write_inode = jfs_write_inode,
|
/linux-6.6.21/fs/gfs2/ |
D | super.c | 1613 .write_inode = gfs2_write_inode,
|
/linux-6.6.21/fs/ceph/ |
D | super.c | 1030 .write_inode = ceph_write_inode,
|
/linux-6.6.21/fs/ext2/ |
D | super.c | 343 .write_inode = ext2_write_inode,
|
/linux-6.6.21/Documentation/filesystems/caching/ |
D | netfs-api.rst | 363 ``write_inode`` superblock operation. It cleans up after writing by unusing
|
12