Lines Matching defs:dirty

84  * Returns if the folio has dirty or writeback buffers. If all the buffers
89 bool *dirty, bool *writeback)
92 *dirty = false;
110 *dirty = true;
537 * as you dirty the buffers, and then use osync_inode_buffers to wait for
538 * completion. Any other dirty buffers which are not yet queued for
662 * `bblock + 1' is probably a dirty indirect block. Hunt it down and, if it's
663 * dirty, schedule it for IO. So that indirects merge nicely with their data.
698 * Add a page to the dirty page list.
703 * If the page has buffers, the uptodate buffers are set dirty, to preserve
704 * dirty-state coherency between the page and the buffers. It the page does
706 * dirty.
710 * buffer dirtiness. That's fine. If this code were to set the page dirty
711 * before the buffers, a concurrent writepage caller could clear the page dirty
712 * bit, see a bunch of clean buffers and we'd end up with dirty buffers/clean
713 * page on the dirty page list.
717 * added to the page after it was set dirty.
739 * synchronized with per-memcg dirty page counters.
761 * initially dirty buffers get waited on, but that any subsequently
765 * Do this in two main stages: first we copy dirty buffers to a
770 * up refiling the buffer on the original inode's dirty list again, so
773 * the osync code to catch these locked, dirty buffers without requeuing
774 * any newly dirty buffers for write.
793 * a lockless check and we rely on seeing the dirty bit */
832 * a lockless check and we rely on seeing the dirty bit */
856 * Invalidate any and all dirty buffers on a given inode. We are
1094 * that page was dirty, the buffers are set dirty also.
1152 * The relationship between dirty buffers and dirty pages:
1154 * Whenever a page has any dirty buffers, the page's dirty bit is set, and
1155 * the page is tagged dirty in the page cache.
1158 * subsections of the page. If the page has buffers, the page dirty bit is
1159 * merely a hint about the true dirty state.
1161 * When a page is set dirty in its entirety, all its buffers are marked dirty
1164 * When a buffer is marked dirty, its page is dirtied, but the page's other
1176 * @bh: the buffer_head to mark dirty
1178 * mark_buffer_dirty() will set the dirty bit against the buffer, then set
1179 * its backing page dirty, then tag the page as dirty in the page cache
1180 * and then attach the address_space's inode to its superblock's dirty
1193 * Very *carefully* optimize the it-is-already-dirty case.
1195 * Don't let the final "is it dirty" escape to before we
1253 * potentially dirty data.
1584 * ensure that no dirty buffer is left outside @offset and that no I/O
1639 * We attach and possibly dirty the buffers atomically wrt
1688 * moment when something will explicitly mark the buffer dirty (hopefully that
1794 * While block_write_full_page is writing back the dirty buffers under
1826 * here, and the (potentially unmapped) buffers may become dirty at
1827 * any time. If a buffer becomes dirty here after we've inspected it
1828 * then we just miss that fact, and the folio stays dirty.
1842 * Get all the dirty buffers mapped to disk addresses and
1918 * The folio was marked dirty, but the buffers were
1947 * The buffer may have been set dirty during
1948 * attachment to a dirty folio.
1973 * and dirty so they'll be written out (in order to prevent uninitialised
2302 * Don't mark the inode dirty under page lock. First, it unnecessarily
2893 * If the folio is dirty but all the buffers are clean then we need to
2896 * to a dirty folio will set *all* buffers dirty. Which would corrupt
2959 * then we can have clean buffers against a dirty folio. We
2969 * dirty bit from being lost.