| blob | b73e0215baa7ceeb0dbfd3a77c79d5d498231e60 |
1 /*
2 * linux/fs/jbd2/commit.c
3 *
4 * Written by Stephen C. Tweedie <sct@redhat.com>, 1998
5 *
6 * Copyright 1998 Red Hat corp --- All Rights Reserved
7 *
8 * This file is part of the Linux kernel and is made available under
9 * the terms of the GNU General Public License, version 2, or at your
10 * option, any later version, incorporated herein by reference.
11 *
12 * Journal commit routines for the generic filesystem journaling code;
13 * part of the ext2fs journaling system.
14 */
16 #include <linux/time.h>
17 #include <linux/fs.h>
18 #include <linux/jbd2.h>
19 #include <linux/errno.h>
20 #include <linux/slab.h>
21 #include <linux/mm.h>
22 #include <linux/pagemap.h>
23 #include <linux/jiffies.h>
24 #include <linux/crc32.h>
25 #include <linux/writeback.h>
26 #include <linux/backing-dev.h>
27 #include <linux/bio.h>
28 #include <linux/blkdev.h>
29 #include <linux/bitops.h>
30 #include <trace/events/jbd2.h>
32 /*
33 * IO end handler for temporary buffer_heads handling writes to the journal.
34 */
36 {
42 else
48 }
50 }
52 /*
53 * When an ext4 file is truncated, it is possible that some pages are not
54 * successfully freed, because they are attached to a committing transaction.
55 * After the transaction commits, these pages are left on the LRU, with no
56 * ->mapping, and with attached buffers. These pages are trivially reclaimable
57 * by the VM, but their apparent absence upsets the VM accounting, and it makes
58 * the numbers in /proc/meminfo look odd.
59 *
60 * So here, we have a buffer which has just come off the forget list. Look to
61 * see if we can strip all buffers from the backing page.
62 *
63 * Called under lock_journal(), and possibly under journal_datalist_lock. The
64 * caller provided us with a ref against the buffer, and we drop that here.
65 */
67 {
80 /* OK, it's a truncated page */
91 nope:
93 }
96 {
98 __u32 csum;
109 }
111 /*
112 * Done it all: now submit the commit record. We should have
113 * cleaned up our previous buffers by now, so if we are in abort
114 * mode we can now just skip the rest of the journal write
115 * entirely.
116 *
117 * Returns 1 if the journal needs to be aborted or 0 on success
118 */
122 __u32 crc32_sum)
123 {
146 JBD2_FEATURE_COMPAT_CHECKSUM)) {
150 }
161 JBD2_FEATURE_INCOMPAT_ASYNC_COMMIT))
163 else
168 }
170 /*
171 * This function along with journal_submit_commit_record
172 * allows to write the commit record asynchronously.
173 */
176 {
187 }
189 /*
190 * write the filemap data using writepage() address_space_operations.
191 * We don't do block allocation here even for delalloc. We don't
192 * use writepages() because with dealyed allocation we may be doing
193 * block allocation in writepages().
194 */
196 {
203 };
207 }
209 /*
210 * Submit all the data buffers of inode associated with the transaction to
211 * disk.
212 *
213 * We are in a committing transaction. Therefore no new inode can be added to
214 * our inode list. We use JI_COMMIT_RUNNING flag to protect inode we currently
215 * operate on from being released while we write out pages.
216 */
219 {
229 /*
230 * submit the inode data buffers. We use writepage
231 * instead of writepages. Because writepages can do
232 * block allocation with delalloc. We need to write
233 * only allocated blocks here.
234 */
244 }
247 }
249 /*
250 * Wait for data submitted for writeout, refile inodes to proper
251 * transaction if needed.
252 *
253 */
256 {
260 /* For locking, see the comment in journal_submit_data_buffers() */
267 /*
268 * Because AS_EIO is cleared by
269 * filemap_fdatawait_range(), set it again so
270 * that user process can get -EIO from fsync().
271 */
277 }
282 }
284 /* Now refile inode to proper lists */
295 }
296 }
300 }
303 {
306 __u32 checksum;
314 }
318 {
322 }
326 {
328 __u32 csum;
338 }
342 {
346 __u32 csum32;
347 __be32 seq;
361 else
363 }
364 /*
365 * jbd2_journal_commit_transaction
366 *
367 * The primary function for committing a transaction to the log. This
368 * function is called by the journal thread to begin a complete commit.
369 */
371 {
381 ktime_t start_time;
382 u64 commit_time;
394 /* Tail of the journal */
396 tid_t first_tid;
405 /*
406 * First job: lock down the current transaction and wait for
407 * all outstanding updates to complete.
408 */
410 /* Do we need to erase the effects of a prior jbd2_journal_flush? */
414 /*
415 * We hold j_checkpoint_mutex so tail cannot change under us.
416 * We don't need any special data guarantees for writing sb
417 * since journal is empty and it is ok for write to be
418 * flushed only with transaction commit.
419 */
423 WRITE_SYNC);
427 }
458 TASK_UNINTERRUPTIBLE);
465 }
467 }
473 /*
474 * First thing we are allowed to do is to discard any remaining
475 * BJ_Reserved buffers. Note, it is _not_ permissible to assume
476 * that there are no such buffers: if a large filesystem
477 * operation like a truncate needs to split itself over multiple
478 * transactions, then it may try to do a jbd2_journal_restart() while
479 * there are still BJ_Reserved buffers outstanding. These must
480 * be released cleanly from the current transaction.
481 *
482 * In this case, the filesystem must still reserve write access
483 * again before modifying the buffer in the new transaction, but
484 * we do not require it to remember exactly which old buffers it
485 * has reserved. This is consistent with the existing behaviour
486 * that multiple jbd2_journal_get_write_access() calls to the same
487 * buffer are perfectly permissible.
488 */
492 /*
493 * A jbd2_journal_get_undo_access()+jbd2_journal_release_buffer() may
494 * leave undo-committed data.
495 */
503 }
505 }
507 /*
508 * Now try to drop any written-back buffers from the journal's
509 * checkpoint lists. We do this *before* commit because it potentially
510 * frees some memory
511 */
518 /*
519 * Clear revoked flag to reflect there is no revoked buffers
520 * in the next transaction which is going to be started.
521 */
524 /*
525 * Switch to a new revoke table.
526 */
529 /*
530 * Reserved credits cannot be claimed anymore, free them
531 */
550 /*
551 * Now start flushing things to disk, in the order they appear
552 * on the transaction lists. Data blocks go first.
553 */
564 /*
565 * Way to go: we have now written out all of the data for a
566 * transaction! Now comes the tricky part: we need to write out
567 * metadata. Loop over the transaction's entire buffer list:
568 */
589 /* Find the next buffer to be journaled... */
593 /* If we're in abort mode, we just un-journal the buffer and
594 release it. */
604 /* If that was the last one, we need to clean up
605 * any descriptor buffers which may have been
606 * already allocated, even if we are now
607 * aborting. */
611 }
613 /* Make sure we have a descriptor block in which to
614 record the metadata buffer. */
625 }
643 /* Record it so that we can wait for IO
644 completion later */
647 }
649 /* Where is the buffer to be written? */
652 /* If the block mapping failed, just abandon the buffer
653 and repeat this loop: we'll fall into the
654 refile-on-abort condition above. */
658 }
660 /*
661 * start_this_handle() uses t_outstanding_credits to determine
662 * the free space in the log, but this counter is changed
663 * by jbd2_journal_next_log_block() also.
664 */
667 /* Bump b_count to prevent truncate from stumbling over
668 the shadowed buffer! @@@ This can go if we ever get
669 rid of the shadow pairing of buffers. */
672 /*
673 * Make a temporary IO buffer with which to write it out
674 * (this will requeue the metadata buffer to BJ_Shadow).
675 */
683 }
686 /* Record the new block's tag in the current descriptor
687 buffer */
702 bufs++;
709 }
711 /* If there's no more to do, or if the descriptor is full,
712 let the IO rip! */
720 /* Write an end-of-descriptor marker before
721 submitting the IOs. "tag" still points to
722 the last tag we set up. */
727 start_journal_io:
730 /*
731 * Compute checksum.
732 */
734 JBD2_FEATURE_COMPAT_CHECKSUM)) {
735 crc32_sum =
737 }
744 }
748 /* Force a new descriptor to be generated next
749 time round the loop. */
752 }
753 }
758 "JBD2: Detected IO errors while flushing file data "
763 }
765 /*
766 * Get current oldest transaction in the log before we issue flush
767 * to the filesystem device. After the flush we can be sure that
768 * blocks of all older transactions are checkpointed to persistent
769 * storage and we will be safe to update journal start in the
770 * superblock with the numbers we get here.
771 */
772 update_tail =
781 /* Update tail only if we free significant amount of space */
784 }
789 /*
790 * If the journal is not located on the file system device,
791 * then we must flush the file system device before we issue
792 * the commit record
793 */
799 /* Done it all: now write the commit record asynchronously. */
801 JBD2_FEATURE_INCOMPAT_ASYNC_COMMIT)) {
806 }
810 /* Lo and behold: we have just managed to send a transaction to
811 the log. Before we can commit it, wait for the IO so far to
812 complete. Control buffers being written are on the
813 transaction's t_log_list queue, and metadata buffers are on
814 the io_bufs list.
816 Wait for the buffers in reverse order. That way we are
817 less likely to be woken up until all IOs have completed, and
818 so we incur less scheduling load.
819 */
826 b_assoc_buffers);
835 /*
836 * The list contains temporary buffer heads created by
837 * jbd2_journal_write_metadata_buffer().
838 */
844 /* We also have to refile the corresponding shadowed buffer */
851 /* The metadata is now released for reuse, but we need
852 to remember it against this transaction so that when
853 we finally commit, we can do any checkpointing
854 required. */
859 }
865 /* Here we wait for the revoke record and descriptor record buffers */
880 /* AKPM: bforget here */
881 }
893 JBD2_FEATURE_INCOMPAT_ASYNC_COMMIT)) {
898 }
902 JBD2_FEATURE_INCOMPAT_ASYNC_COMMIT) &&
905 }
910 /*
911 * Now disk caches for filesystem device are flushed so we are safe to
912 * erase checkpointed transactions from the log by updating journal
913 * superblock.
914 */
918 /* End of a transaction! Finally, we can do checkpoint
919 processing: any buffers committed as a result of this
920 transaction can be removed from any checkpoint list it was on
921 before. */
930 restart_loop:
931 /*
932 * As there are other places (journal_unmap_buffer()) adding buffers
933 * to this list we have to be careful and hold the j_list_lock.
934 */
944 /*
945 * Get a reference so that bh cannot be freed before we are
946 * done with it.
947 */
952 /*
953 * If there is undo-protected committed data against
954 * this buffer, then we can remove it now. If it is a
955 * buffer needing such protection, the old frozen_data
956 * field now points to a committed version of the
957 * buffer, so rotate that field to the new committed
958 * data.
959 *
960 * Otherwise, we can just throw away the frozen data now.
961 *
962 * We also know that the frozen data has already fired
963 * its triggers if they exist, so we can clear that too.
964 */
972 }
977 }
985 }
987 /* Only re-checkpoint the buffer_head if it is marked
988 * dirty. If the buffer was added to the BJ_Forget list
989 * by jbd2_journal_forget, it may no longer be dirty and
990 * there's no point in keeping a checkpoint record for
991 * it. */
993 /*
994 * A buffer which has been freed while still being journaled by
995 * a previous transaction.
996 */
998 /*
999 * If the running transaction is the one containing
1000 * "add to orphan" operation (b_next_transaction !=
1001 * NULL), we have to wait for that transaction to
1002 * commit before we can really get rid of the buffer.
1003 * So just clear b_modified to not confuse transaction
1004 * credit accounting and refile the buffer to
1005 * BJ_Forget of the running transaction. If the just
1006 * committed transaction contains "add to orphan"
1007 * operation, we can completely invalidate the buffer
1008 * now. We are rather through in that since the
1009 * buffer may be still accessible when blocksize <
1010 * pagesize and it is attached to the last partial
1011 * page.
1012 */
1021 }
1022 }
1031 /*
1032 * The buffer on BJ_Forget list and not jbddirty means
1033 * it has been freed by this transaction and hence it
1034 * could not have been reallocated until this
1035 * transaction has committed. *BUT* it could be
1036 * reallocated once we have written all the data to
1037 * disk and before we process the buffer on BJ_Forget
1038 * list.
1039 */
1042 }
1048 else
1051 }
1053 /*
1054 * This is a bit sleazy. We use j_list_lock to protect transition
1055 * of a transaction into T_FINISHED state and calling
1056 * __jbd2_journal_drop_transaction(). Otherwise we could race with
1057 * other checkpointing code processing the transaction...
1058 */
1061 /*
1062 * Now recheck if some buffers did not get attached to the transaction
1063 * while the lock was dropped...
1064 */
1069 }
1071 /* Add the transaction to the checkpoint list
1072 * __journal_remove_checkpoint() can not destroy transaction
1073 * under us because it is not marked as T_FINISHED yet */
1084 commit_transaction;
1086 commit_transaction;
1087 }
1090 /* Done with this transaction! */
1100 /*
1101 * File the transaction statistics
1102 */
1116 /*
1117 * weight the commit time higher than the average time so we don't
1118 * react too strongly to vast changes in the commit time
1119 */
1123 else
1138 /* Check if the transaction can be dropped now that we are finished */
1143 }
1148 /*
1149 * Calculate overall stats
1150 */
1164 }