84  * Returns if the folio has dirty or writeback buffers. If all the buffers
86  * any of the buffers are locked, it is assumed they are locked for IO.
198 	 * Folio lock protects the buffers. Callers that cannot block  in __find_get_block_slow()
231 	/* we might be here because some of the buffers on this page are  in __find_get_block_slow()
234 	 * elsewhere, don't buffer_error if we had some unmapped buffers  in __find_get_block_slow()
427  * If a page's buffers are under async readin (end_buffer_async_read
429  * control could lock one of the buffers after it has completed
430  * but while some of the other buffers have not completed.  This
435  * The page comes unlocked when it has no locked buffer_async buffers
439  * the buffers.
476  * management of a list of dependent buffers at ->i_mapping->i_private_list.
478  * Locking is a little subtle: try_to_free_buffers() will remove buffers
481  * at the time, not against the S_ISREG file which depends on those buffers.
483  * which backs the buffers.  Which is different from the address_space 
484  * against which the buffers are listed.  So for a particular address_space,
489  * Which introduces a requirement: all buffers on an address_space's
492  * address_spaces which do not place buffers at ->i_private_list via these
503  * mark_buffer_dirty_fsync() to clearly define why those buffers are being
510  * that buffers are taken *off* the old inode's list when they are freed
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
567  * sync_mapping_buffers - write out & wait upon a mapping's "associated" buffers
568  * @mapping: the mapping which wants those buffers written
570  * Starts I/O against the buffers at mapping->i_private_list, and waits upon
574  * @mapping is a file or directory which needs those buffers to be written for
599  * filesystems which track all non-inode metadata in the buffers list
624 	/* check and advance again to catch errors after syncing out buffers */  in generic_buffers_fsync_noflush()
642  * filesystems which track all non-inode metadata in the buffers list
709  * If the folio has buffers, the uptodate buffers are set dirty, to
710  * preserve dirty-state coherency between the folio and the buffers.
711  * Buffers added to a dirty folio are created dirty.
713  * The buffers are dirtied before the folio is dirtied.  There's a small
716  * dirty before the buffers, writeback could clear the folio dirty flag,
717  * see a bunch of clean buffers and we'd end up with dirty buffers/clean
721  * using the folio's buffer list.  This also prevents clean buffers
764  * Write out and wait upon a list of buffers.
767  * initially dirty buffers get waited on, but that any subsequently
768  * dirtied buffers don't.  After all, we don't want fsync to last
771  * Do this in two main stages: first we copy dirty buffers to a
779  * the osync code to catch these locked, dirty buffers without requeuing
780  * any newly dirty buffers for write.
861  * Invalidate any and all dirty buffers on a given inode.  We are
863  * done a sync().  Just drop the buffers from the inode list.
866  * assumes that all the buffers are against the blockdev.
884  * Remove any clean buffers from the inode's buffer list.  This is called
885  * when we're trying to free the inode itself.  Those buffers can pin it.
887  * Returns true if all buffers were removed.
913  * Create the appropriate buffers when given a folio for data area and
915  * follow the buffers created.  Return NULL if unable to create more
916  * buffers.
1002  * Initialise the state of a blockdev folio's buffers.
1064 		 * writeback, or buffers may be cleaned.  This should not  in grow_dev_folio()
1065 		 * happen very often; maybe we have old buffers attached to  in grow_dev_folio()
1080 	 * Link the folio to the buffers and initialise them.  Take the  in grow_dev_folio()
1095  * Create buffers for the specified block device block's folio.  If
1096  * that folio was dirty, the buffers are set dirty also.  Returns false
1115 	/* Create a folio with the proper size buffers */  in grow_buffers()
1153  * The relationship between dirty buffers and dirty pages:
1155  * Whenever a page has any dirty buffers, the page's dirty bit is set, and
1158  * At all times, the dirtiness of the buffers represents the dirtiness of
1159  * subsections of the page.  If the page has buffers, the page dirty bit is
1162  * When a page is set dirty in its entirety, all its buffers are marked dirty
1163  * (if the page has buffers).
1166  * buffers are not.
1168  * Also.  When blockdev buffers are explicitly read with bread(), they
1170  * uptodate - even if all of its buffers are uptodate.  A subsequent
1172  * buffers, will set the folio uptodate and will perform no I/O.
1289  * The bhs[] array is sorted - newest buffer is at bhs[0].  Buffers have their
1631  * block_invalidate_folio() does not have to release all buffers, but it must
1675 	 * We release buffers only if the entire folio is being invalidated.  in block_invalidate_folio()
1687  * We attach and possibly dirty the buffers atomically wrt
1725  * clean_bdev_aliases: clean a range of buffers in block device
1726  * @bdev: Block device to clean buffers in
1740  * writeout I/O going on against recently-freed buffers.  We don't wait on that
1766 			 * to pin buffers here since we can afford to sleep and  in clean_bdev_aliases()
1827  * While block_write_full_folio is writing back the dirty buffers under
1828  * the page lock, whoever dirtied the buffers may decide to clean them
1858 	 * here, and the (potentially unmapped) buffers may become dirty at  in __block_write_full_folio()
1862 	 * Buffers outside i_size may be dirtied by block_dirty_folio;  in __block_write_full_folio()
1873 	 * Get all the dirty buffers mapped to disk addresses and  in __block_write_full_folio()
1879 			 * mapped buffers outside i_size will occur, because  in __block_write_full_folio()
1930 	 * The folio and its buffers are protected by the writeback flag,  in __block_write_full_folio()
1951 		 * The folio was marked dirty, but the buffers were  in __block_write_full_folio()
1972 	/* Recovery: lock and submit the mapped buffers */  in __block_write_full_folio()
2006  * If a folio has any new buffers, zero them out here, and mark them uptodate
2234 	 * If this is a partial write which happened to make all buffers  in block_commit_write()
2282 		 * The buffers that were written will now be uptodate, so  in block_write_end()
2347  * block_is_partially_uptodate checks whether buffers within a folio are
2350  * Returns true if all buffers which correspond to the specified part
2462 	 * All buffers are uptodate or get_block() returned an error  in block_read_full_folio()
2925  * try_to_free_buffers - Release buffers attached to this folio.
2928  * If any buffers are in use (dirty, under writeback, elevated refcount),
2929  * no buffers will be freed.
2931  * If the folio is dirty but all the buffers are clean then we need to
2933  * may be against a block device, and a later reattachment of buffers
2934  * to a dirty folio will set *all* buffers dirty.  Which would corrupt
2937  * The same applies to regular filesystem folios: if all the buffers are
2946  * Return: true if all buffers attached to this folio were freed.
2967 	 * If the filesystem writes its buffers by hand (eg ext3)  in try_to_free_buffers()
2968 	 * then we can have clean buffers against a dirty folio.  We  in try_to_free_buffers()
2973 	 * the folio's buffers clean.  We discover that here and clean  in try_to_free_buffers()
3116  * __bh_read_batch - Submit read for a batch of unlocked buffers