table of contents
- stretch 4.9.168-1
__MARK_INODE_DIRTY(9) | The Linux VFS | __MARK_INODE_DIRTY(9) |
NAME¶
__mark_inode_dirty - internal functionSYNOPSIS¶
void __mark_inode_dirty(struct inode * inode, int flags);
ARGUMENTS¶
inodeflags
DESCRIPTION¶
Put the inode on the super block's dirty list.CAREFUL! We mark it dirty unconditionally, but move it onto the dirty list only if it is hashed or if it refers to a blockdev. If it was not hashed, it will never be added to the dirty list even if it is later hashed, as it will have been marked dirty already.
In short, make sure you hash any inodes _before_ you start marking them dirty.
Note that for blockdevs, inode->dirtied_when represents the dirtying time of the block-special inode (/dev/hda1) itself. And the ->dirtied_when field of the kernel-internal blockdev inode represents the dirtying time of the blockdev's pages. This is why for I_DIRTY_PAGES we always use page->mapping->host, so the page-dirtying time is recorded in the internal blockdev inode.
COPYRIGHT¶
April 2019 | Kernel Hackers Manual 4.9. |