3  * fs/fs-writeback.c
9  * pages against inodes.  ie: data writeback.  Writeout of the
14  *		Additions for address_space-based writeback
26 #include <linux/writeback.h>
50 	unsigned int for_sync:1;	/* sync(2) WB_SYNC_ALL writeback */
52 	enum wb_reason reason;		/* why was writeback initiated? */
81 #include <trace/events/writeback.h>
229  * The current cgroup writeback is built on the assumption that multiple
420 	 * folios actually under writeback.  in inode_do_switch_wbs()
692 	 * In addition to the inodes that have completed writeback, also switch  in cleanup_offline_cgwb()
696 	 * bandwidth restrictions, as writeback of inode metadata is not  in cleanup_offline_cgwb()
730  * Record @inode's writeback context into @wbc and unlock the i_lock.  On
731  * writeback completion, wbc_detach_inode() should be called.  This is used
732  * to track the cgroup writeback context.
769  * @wbc: writeback_control of the just finished writeback
771  * To be called after a writeback attempt of an inode finishes and undoes
776  * the usefulness of such sharing, cgroup writeback tracks ownership
781  * behaviors (single foreign page can lead to gigabytes of writeback to be
784  * To resolve this issue, cgroup writeback detects the majority dirtier of
788  * a certain amount of time and/or writeback attempts.
790  * On each writeback attempt, @wbc tries to detect the majority writer
891  * wbc_account_cgroup_owner - account writeback to update inode cgroup ownership
892  * @wbc: writeback_control of the writeback in progress
896  * @bytes from @page are about to written out during the writeback
911 	 * regular writeback instead of writing things out itself.  in wbc_account_cgroup_owner()
974  * @skip_if_busy: skip wb's which already have writeback in progress
1053  * cgroup_writeback_by_id - initiate cgroup writeback from bdi and memcg IDs
1056  * @reason: reason why some writeback work initiated
1110 	/* issue the writeback work */  in cgroup_writeback_by_id()
1248 	 * All callers of this function want to start writeback of all  in wb_start_writeback()
1264  * wb_start_background_writeback - start background writeback
1268  *   This makes sure WB_SYNC_NONE background writeback happens. When
1277 	 * writeback as soon as there is no other work to do.  in wb_start_background_writeback()
1284  * Remove the inode from the writeback list it is on.
1303  * mark an inode as under writeback on the sb
1321  * clear an inode as under writeback on the sb
1406 	 * from permanently stopping the whole bdi writeback.  in inode_dirtied_after()
1453 	 * Inode is already marked as I_SYNC_QUEUED so writeback list handling is  in move_expired_inodes()
1511  * Wait for writeback on an inode to complete. Called with i_lock held.
1562  * Find proper writeback list for the inode depending on its current state and
1563  * possibly also change of its state while we were doing writeback.  Here we
1564  * handle things such as livelock prevention or fairness of writeback among
1566  * processes all inodes in writeback lists and requeueing inodes behind flusher
1587 		 * Writeback is not making progress due to locked buffers.  in requeue_inode()
1610 			 * Writeback blocked by something other than  in requeue_inode()
1613 			 * retrying writeback of the dirty page/inode  in requeue_inode()
1620 		 * Filesystems can dirty the inode during writeback operations,  in requeue_inode()
1630 		/* The inode is clean. Remove from writeback lists. */  in requeue_inode()
1639  * This doesn't remove the inode from the writeback list it is on, except
1641  * expiration.  The caller is otherwise responsible for writeback list handling.
1663 	 * I/O completion. We don't do it for sync(2) writeback because it has a  in __writeback_single_inode()
1734  * the regular batched writeback done by the flusher threads in
1755 		 * Writeback is already running on the inode.  For WB_SYNC_NONE,  in writeback_single_inode()
1757 		 * must wait for the existing writeback to complete, then do  in writeback_single_inode()
1758 		 * writeback again if there's anything left.  in writeback_single_inode()
1769 	 * still under writeback, e.g. due to prior WB_SYNC_NONE writeback.  If  in writeback_single_inode()
1792 		 * removed from its writeback list (if any). Otherwise the  in writeback_single_inode()
1793 		 * flusher threads are responsible for the writeback lists.  in writeback_single_inode()
1826 	 * The intended call sequence for WB_SYNC_ALL writeback is:  in writeback_chunk_size()
1916 			 * If this inode is locked for writeback and we are not  in writeback_sb_inodes()
1917 			 * doing writeback-for-data-integrity, move it to  in writeback_sb_inodes()
1918 			 * b_more_io so that writeback can proceed with the  in writeback_sb_inodes()
1933 		 * are doing WB_SYNC_NONE writeback. So this catches only the  in writeback_sb_inodes()
2063  * Explicit flushing or periodic writeback of "old" data.
2066  * dirtying-time in the inode's address_space.  So this periodic writeback code
2070  * Try to run once per dirty_writeback_interval.  But if a writeback event
2090 		 * Stop writeback when nr_pages has been consumed  in wb_writeback()
2096 		 * Background writeout and kupdate-style writeback may  in wb_writeback()
2142 		 * Dirty inodes are moved to b_io for writeback in batches.  in wb_writeback()
2162 		 * become available for writeback. Otherwise  in wb_writeback()
2218 	 * When set to zero, disable periodic writeback  in wb_check_old_data_flush()
2271  * Retrieve work items and do the writeback they describe
2291 	 * Check for periodic writeback, kupdated() style  in wb_do_writeback()
2301  * Handle writeback of dirty data for the device backed by this bdi. Also
2342  * Start writeback of all dirty pages on this bdi.
2365  * Wakeup the flusher threads to start writeback of all currently dirty pages
2372 	 * If we are expecting writeback progress we must submit plugged IO.  in wakeup_flusher_threads()
2538 		 * If the inode is queued for writeback by flush worker, just  in __mark_inode_dirty()
2622 	 * Splice the writeback list onto a temporary list to avoid waiting on  in wait_sb_inodes()
2623 	 * inodes that have started writeback after this point.  in wait_sb_inodes()
2627 	 * the local list because inodes can be dropped from either by writeback  in wait_sb_inodes()
2635 	 * Data integrity sync. Must wait for all pages under writeback, because  in wait_sb_inodes()
2649 		 * writeback tag. Writeback completion is responsible to remove  in wait_sb_inodes()
2650 		 * the inode from either list once the writeback tag is cleared.  in wait_sb_inodes()
2677 		 * applications can catch the writeback error using fsync(2).  in wait_sb_inodes()
2717  * writeback_inodes_sb_nr -	writeback dirty inodes from given super_block
2720  * @reason: reason why some writeback work initiated
2722  * Start writeback on some inodes on this super_block. No guarantees are made
2735  * writeback_inodes_sb	-	writeback dirty inodes from given super_block
2737  * @reason: reason why some writeback work was initiated
2739  * Start writeback on some inodes on this super_block. No guarantees are made
2750  * try_to_writeback_inodes_sb - try to start writeback if none underway
2752  * @reason: reason why some writeback work was initiated
2754  * Invoke __writeback_inodes_sb_nr if no writeback is currently underway.
2789 	 * inodes under writeback and I_DIRTY_TIME inodes ignored by  in sync_inodes_sb()