Inode Synchronization

writeback_inodes writes back installed mappings by walking through the system inodes (for the sake of simplicity, this is called inode writeback, but in fact not the inode but the dirty data associated with it are written back). The function shoulders the main burden of synchronization because most system data are provided in the form of address space mappings that make use of inodes. Figure 17-6 illustrates the code flow diagram for writeback_inodes. The function is slightly more complicated in reality because some more details and corner cases need to be handled properly. We consider a simplified variant that nevertheless contains everything that is essential when inodes are written back.

Figure 17-6: Code flow diagram for writeback_inodes.

The function uses the data structures discussed in Chapter 8 to establish a link among superblocks, inodes, and associated data.

Continue reading here: Walking the Superblocks

Was this article helpful?

0 0