> > We set the per-block dirty status in ->write_begin. The check above happens in the > writeback path when we are about to write the dirty data to the disk. > What the check is doing is that, it checks if the block state is not dirty > then skip it which means the block was not written to in the ->write_begin(). > Also the block with dirty status always means that the block is uptodate > anyways. > > Hope it helps! > Definitely. I also checked your 1st RFC version to get more context. Thanks for the explanation.
