)]}' { "log": [ { "commit": "f1f8935a5c38a2c61e86a42bc971a2539eef2211", "tree": "694950045f2f5d89507d7206cf6595e09cdfbd2c", "parents": [ "34116645d912f65d7eb4508a1db3c9d0e45facb1", "f2a44523b20f323e4aef7c16261d34d6f0a4bf06" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Wed Nov 02 10:06:20 2011 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Wed Nov 02 10:06:20 2011 -0700" }, "message": "Merge branch \u0027for_linus\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4\n\n* \u0027for_linus\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4: (97 commits)\n jbd2: Unify log messages in jbd2 code\n jbd/jbd2: validate sb-\u003es_first in journal_get_superblock()\n ext4: let ext4_ext_rm_leaf work with EXT_DEBUG defined\n ext4: fix a syntax error in ext4_ext_insert_extent when debugging enabled\n ext4: fix a typo in struct ext4_allocation_context\n ext4: Don\u0027t normalize an falloc request if it can fit in 1 extent.\n ext4: remove comments about extent mount option in ext4_new_inode()\n ext4: let ext4_discard_partial_buffers handle unaligned range correctly\n ext4: return ENOMEM if find_or_create_pages fails\n ext4: move vars to local scope in ext4_discard_partial_page_buffers_no_lock()\n ext4: Create helper function for EXT4_IO_END_UNWRITTEN and i_aiodio_unwritten\n ext4: optimize locking for end_io extent conversion\n ext4: remove unnecessary call to waitqueue_active()\n ext4: Use correct locking for ext4_end_io_nolock()\n ext4: fix race in xattr block allocation path\n ext4: trace punch_hole correctly in ext4_ext_map_blocks\n ext4: clean up AGGRESSIVE_TEST code\n ext4: move variables to their scope\n ext4: fix quota accounting during migration\n ext4: migrate cleanup\n ...\n" }, { "commit": "b9075fa968a0a4347aef35e235e2995c0e57dddd", "tree": "cf9f9716784e790d8a43339653256d9cf9178ff3", "parents": [ "ae29bc92da01a2e9d278a9a58c3b307d41cc0254" ], "author": { "name": "Joe Perches", "email": "joe@perches.com", "time": "Mon Oct 31 17:11:33 2011 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Oct 31 17:30:54 2011 -0700" }, "message": "treewide: use __printf not __attribute__((format(printf,...)))\n\nStandardize the style for compiler based printf format verification.\nStandardized the location of __printf too.\n\nDone via script and a little typing.\n\n$ grep -rPl --include\u003d*.[ch] -w \"__attribute__\" * | \\\n grep -vP \"^(tools|scripts|include/linux/compiler-gcc.h)\" | \\\n xargs perl -n -i -e \u0027local $/; while (\u003c\u003e) { s/\\b__attribute__\\s*\\(\\s*\\(\\s*format\\s*\\(\\s*printf\\s*,\\s*(.+)\\s*,\\s*(.+)\\s*\\)\\s*\\)\\s*\\)/__printf($1, $2)/g ; print; }\u0027\n\n[akpm@linux-foundation.org: revert arch bits]\nSigned-off-by: Joe Perches \u003cjoe@perches.com\u003e\nCc: \"Kirill A. Shutemov\" \u003ckirill@shutemov.name\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "0edeb71dc9133bfb505d3bf59642e07cd936613e", "tree": "bcb68e2676d9bba1e4e4e28fb1ba8d382caf26eb", "parents": [ "b82e384c7bb9a19036b4daf58fa216df7cd48aa0" ], "author": { "name": "Tao Ma", "email": "boyu.mt@taobao.com", "time": "Mon Oct 31 17:30:44 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Oct 31 17:30:44 2011 -0400" }, "message": "ext4: Create helper function for EXT4_IO_END_UNWRITTEN and i_aiodio_unwritten\n\nEXT4_IO_END_UNWRITTEN flag set and the increase of i_aiodio_unwritten\nshould be done simultaneously since ext4_end_io_nolock always clear\nthe flag and decrease the counter in the same time.\n\nWe have found some bugs that the flag is set while leaving\ni_aiodio_unwritten unchanged(commit 32c80b32c053d). So this patch just tries\nto create a helper function to wrap them to avoid any future bug.\nThe idea is inspired by Eric.\n\nCc: Eric Sandeen \u003csandeen@redhat.com\u003e\nSigned-off-by: Tao Ma \u003cboyu.mt@taobao.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "5cb81dabcc28863e7d04e6fd9ede154bd8459c14", "tree": "704df9fffdc243449dc5eba697cec133162ee1bf", "parents": [ "fba90ffee813e2425feb9a57c532b3d297af18c3" ], "author": { "name": "Dmitry Monakhov", "email": "dmonakhov@openvz.org", "time": "Sat Oct 29 09:05:00 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Oct 29 09:05:00 2011 -0400" }, "message": "ext4: fix quota accounting during migration\n\nThe tmp_inode should have same uid/gid as the original inode.\nOtherwise new metadata blocks will be accounted to wrong quota-id,\nwhich will result in a quota leak after the inode migration is\ncompleted.\n\nSigned-off-by: Dmitry Monakhov \u003cdmonakhov@openvz.org\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "a4e5d88b1b24827f4f6a3cba43228936a67d81ba", "tree": "0f5b0309f290f5fc23478794c6f4adcd7c18896a", "parents": [ "750c9c47a5f9daa88333ac435a1afe4d4b428230" ], "author": { "name": "Dmitry Monakhov", "email": "dmonakhov@openvz.org", "time": "Tue Oct 25 08:15:12 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Oct 25 08:15:12 2011 -0400" }, "message": "ext4: update EOFBLOCKS flag on fallocate properly\n\nEOFBLOCK_FL should be updated if called w/o FALLOCATE_FL_KEEP_SIZE\nCurrently it happens only if new extent was allocated.\n\nTESTCASE:\nfallocate test_file -n -l4096\nfallocate test_file -l4096\nLast fallocate cmd has updated size, but keept EOFBLOCK_FL set. And\nfsck will complain about that.\n\nAlso remove ping pong in ext4_fallocate() in case of new extents,\nwhere ext4_ext_map_blocks() clear EOFBLOCKS bit, and later\next4_falloc_update_inode() restore it again.\n\nSigned-off-by: Dmitry Monakhov \u003cdmonakhov@openvz.org\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "7fd59c83b05dc1b8af2be4d991ee376f782cd8b0", "tree": "0d320a397b687f822167749afbb11d89d9f21a66", "parents": [ "df3ab17072c31fbd394614711772682f0a956a2c" ], "author": { "name": "Tao Ma", "email": "boyu.mt@taobao.com", "time": "Sat Oct 08 15:56:35 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Oct 08 15:56:35 2011 -0400" }, "message": "ext4: remove the obsolete/broken EXT4_IOC_WAIT_FOR_READONLY ioctl\n\nThere are no users of the EXT4_IOC_WAIT_FOR_READONLY ioctl, and it is\nalso broken. No one sets the set_ro_timer, no one wakes up us and our\nstate is set to TASK_INTERRUPTIBLE not RUNNING. So remove it.\n\nSigned-off-by: Tao Ma \u003cboyu.mt@taobao.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "4113c4caa4f355b8ff8b7ff0510c29c9d00d30b3", "tree": "b978be1044d72ab78739edd441385253f6c932ac", "parents": [ "af909a57fde821627282204ba43f27331342bf26" ], "author": { "name": "Lukas Czerner", "email": "lczerner@redhat.com", "time": "Sat Oct 08 14:34:47 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Oct 08 14:34:47 2011 -0400" }, "message": "ext4: remove deprecated oldalloc\n\nFor a long time now orlov is the default block allocator in the\next4. It performs better than the old one and no one seems to claim\notherwise so we can safely drop it and make oldalloc and orlov mount\noption deprecated.\n\nThis is a part of the effort to reduce number of ext4 options hence the\ntest matrix.\n\nSigned-off-by: Lukas Czerner \u003clczerner@redhat.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "5356f2615cd558c57a1f7d7528d1ad4de3640d96", "tree": "e3590bf14d9a21c4eb365105886382bfb1131b95", "parents": [ "d8990240d8c911064447f8aa5a440f9345a6d692" ], "author": { "name": "Aditya Kali", "email": "adityakali@google.com", "time": "Fri Sep 09 19:20:51 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 19:20:51 2011 -0400" }, "message": "ext4: attempt to fix race in bigalloc code path\n\nCurrently, there exists a race between delayed allocated writes and\nthe writeback when bigalloc feature is in use. The race was because we\nwanted to determine what blocks in a cluster are under delayed\nallocation and we were using buffer_delayed(bh) check for it. But, the\nwriteback codepath clears this bit without any synchronization which\nresulted in a race and an ext4 warning similar to:\n\nEXT4-fs (ram1): ext4_da_update_reserve_space: ino 13, used 1 with only 0\n\t\treserved data blocks\n\nThe race existed in two places.\n(1) between ext4_find_delalloc_range() and ext4_map_blocks() when called from\n writeback code path.\n(2) between ext4_find_delalloc_range() and ext4_da_get_block_prep() (where\n buffer_delayed(bh) is set.\n\nTo fix (1), this patch introduces a new buffer_head state bit -\nBH_Da_Mapped. This bit is set under the protection of\nEXT4_I(inode)-\u003ei_data_sem when we have actually mapped the delayed\nallocated blocks during the writeout time. We can now reliably check\nfor this bit inside ext4_find_delalloc_range() to determine whether\nthe reservation for the blocks have already been claimed or not.\n\nTo fix (2), it was necessary to set buffer_delay(bh) under the\nprotection of i_data_sem. So, I extracted the very beginning of\next4_map_blocks into a new function - ext4_da_map_blocks() - and\nperformed the required setting of bh_delay bit and the quota\nreservation under the protection of i_data_sem. These two fixes makes\nthe checking of buffer_delay(bh) and buffer_da_mapped(bh) consistent,\nthus removing the race.\n\nTested: I was able to reproduce the problem by running \u0027dd\u0027 and\n\u0027fsync\u0027 in parallel. Also, xfstests sometimes used to reproduce this\nrace. After the fix both my test and xfstests were successful and no\nrace (warning message) was observed.\n\nGoogle-Bug-Id: 4997027\n\nSigned-off-by: Aditya Kali \u003cadityakali@google.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n\n" }, { "commit": "d8990240d8c911064447f8aa5a440f9345a6d692", "tree": "c12cda27583eb9616d91ec38fdfd79c6eb490bd5", "parents": [ "df55c99dc8ee4c3c886a5edc8a4aa6b131c95afc" ], "author": { "name": "Aditya Kali", "email": "adityakali@google.com", "time": "Fri Sep 09 19:18:51 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 19:18:51 2011 -0400" }, "message": "ext4: add some tracepoints in ext4/extents.c\n\nThis patch adds some tracepoints in ext4/extents.c and updates a tracepoint in\next4/inode.c.\n\nTested: Built and ran the kernel and verified that these tracepoints work.\nAlso ran xfstests.\n\nSigned-off-by: Aditya Kali \u003cadityakali@google.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n \n\n" }, { "commit": "df55c99dc8ee4c3c886a5edc8a4aa6b131c95afc", "tree": "6e5ea5a435659fa2dee7410f0b0196bdaf3a2054", "parents": [ "e7d5f3156e6827970f75ab27ad7eb0155826eb0b" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 19:16:51 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 19:16:51 2011 -0400" }, "message": "ext4: rename ext4_has_free_blocks() to ext4_has_free_clusters()\n\nRename the function so it is more clear what is going on. Also rename\nthe various variables so it\u0027s clearer what\u0027s happening.\n\nAlso fix a missing blocks to cluster conversion when reading the\nnumber of reserved blocks for root.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "e7d5f3156e6827970f75ab27ad7eb0155826eb0b", "tree": "7eab0a0660052e4a3fe1bba57a869138fb29e7f4", "parents": [ "cff1dfd767d1ee3c773fd8b57fe310957e5f8abb" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 19:14:51 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 19:14:51 2011 -0400" }, "message": "ext4: rename ext4_claim_free_blocks() to ext4_claim_free_clusters()\n\nThis function really claims a number of free clusters, not blocks, so\nrename it so it\u0027s clearer what\u0027s going on.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "cff1dfd767d1ee3c773fd8b57fe310957e5f8abb", "tree": "ace05de33bb5d1e2062724818d57d89eae66004f", "parents": [ "5dee54372c1ea15ab482b959634cda8c01b042bd" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 19:12:51 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 19:12:51 2011 -0400" }, "message": "ext4: rename ext4_free_blocks_after_init() to ext4_free_clusters_after_init()\n\nThis function really returns the number of clusters after initializing\nan uninitalized block bitmap has been initialized.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "5dee54372c1ea15ab482b959634cda8c01b042bd", "tree": "512da0144f6a9f86b5817569d0521b60cddee4c9", "parents": [ "021b65bb1e4e4b625c80bbb82651e5e155721ef3" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 19:10:51 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 19:10:51 2011 -0400" }, "message": "ext4: rename ext4_count_free_blocks() to ext4_count_free_clusters()\n\nThis function really counts the free clusters reported in the block\ngroup descriptors, so rename it to reduce confusion.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "021b65bb1e4e4b625c80bbb82651e5e155721ef3", "tree": "e1826a0ec395ac2acf46c43113f2c6a64a5165d0", "parents": [ "6f16b60690ba04cf476480a6f19b204e4b95b4a6" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 19:08:51 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 19:08:51 2011 -0400" }, "message": "ext4: Rename ext4_free_blks_{count,set}() to refer to clusters\n\nThe field bg_free_blocks_count_{lo,high} in the block group\ndescriptor has been repurposed to hold the number of free clusters for\nbigalloc functions. So rename the functions so it makes it easier to\nread and audit the block allocation and block freeing code.\n\nNote: at this point in bigalloc development we doesn\u0027t support\nonline resize, so this also makes it really obvious all of the places\nwe need to fix up to add support for online resize.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "6f16b60690ba04cf476480a6f19b204e4b95b4a6", "tree": "dbb3efd3912e0a81ea8f439deb561bfc9fc2a9bd", "parents": [ "7b415bf60f6afb0499fd3dc0ee33444f54e28567" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 19:06:51 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 19:06:51 2011 -0400" }, "message": "ext4: enable mounting bigalloc as read/write\n\nNow that we have implemented all of the changes needed for bigalloc,\nwe can finally enable it!\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "7b415bf60f6afb0499fd3dc0ee33444f54e28567", "tree": "9c64fef2b8d60ce64865af6e4c2cc6008026e28c", "parents": [ "27baebb849d46d901e756e6502b0a65a62e43771" ], "author": { "name": "Aditya Kali", "email": "adityakali@google.com", "time": "Fri Sep 09 19:04:51 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 19:04:51 2011 -0400" }, "message": "ext4: Fix bigalloc quota accounting and i_blocks value\n\nWith bigalloc changes, the i_blocks value was not correctly set (it was still\nset to number of blocks being used, but in case of bigalloc, we want i_blocks\nto represent the number of clusters being used). Since the quota subsystem sets\nthe i_blocks value, this patch fixes the quota accounting and makes sure that\nthe i_blocks value is set correctly.\n\nSigned-off-by: Aditya Kali \u003cadityakali@google.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "24aaa8ef4e2b5764ada1fc69787e2fbd4f6276e5", "tree": "7f83cc8e52b5f2edc5d89d2d1808d0972831f9bf", "parents": [ "5704265188ffe4290ed73b3cb685206c3ed8209d" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 18:58:51 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 18:58:51 2011 -0400" }, "message": "ext4: convert the free_blocks field in s_flex_groups to be free_clusters\n\nConvert the free_blocks to be free_clusters to make the final revised\nbigalloc changes easier to read/understand.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n\n\n" }, { "commit": "5704265188ffe4290ed73b3cb685206c3ed8209d", "tree": "6bc51bea59625b2a7c8e4b74bbb66884371f74dd", "parents": [ "0aa060000e83ca3d09ddc446a7174fb0820d99bc" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 18:56:51 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 18:56:51 2011 -0400" }, "message": "ext4: convert s_{dirty,free}blocks_counter to s_{dirty,free}clusters_counter\n\nConvert the percpu counters s_dirtyblocks_counter and\ns_freeblocks_counter in struct ext4_super_info to be\ns_dirtyclusters_counter and s_freeclusters_counter.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "84130193e0e6568dfdfb823f0e1e19aec80aff6e", "tree": "799534ea6cd551ba346e32da2ee2f363851a3257", "parents": [ "53accfa9f819c80056db6f03f9c5cfa4bcba1ed8" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 18:50:51 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 18:50:51 2011 -0400" }, "message": "ext4: teach ext4_free_blocks() about bigalloc and clusters\n\nThe ext4_free_blocks() function now has two new flags that indicate\nwhether a partial cluster at the beginning or the end of the block\nextents should be freed or not. That will be up the caller (i.e.,\ntruncate), who can figure out whether partial clusters at the\nbeginning or the end of a block range can be freed.\n\nWe also have to update the ext4_mb_free_metadata() and\nrelease_blocks_on_commit() machinery to be cluster-based, since it is\nused by ext4_free_blocks().\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "d5b8f31007a93777cfb0603b665858fb7aebebfc", "tree": "19d9dfed9314132302b8e3036a2ada26f9809036", "parents": [ "fd034a84e1ea5c8c8d159cd2089c32e792c269b0" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 18:44:51 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 18:44:51 2011 -0400" }, "message": "ext4: bigalloc changes to block bitmap initialization functions\n\nAdd bigalloc support to ext4_init_block_bitmap() and\next4_free_blocks_after_init().\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "fd034a84e1ea5c8c8d159cd2089c32e792c269b0", "tree": "5992d541a005137a57a44921fd1be6311ee841d2", "parents": [ "49f7f9af4bb4d7972f3a35a74877937fec9f622d" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 18:42:51 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 18:42:51 2011 -0400" }, "message": "ext4: split out ext4_free_blocks_after_init()\n\nThe function ext4_free_blocks_after_init() used to be a #define of\next4_init_block_bitmap(). This actually made it difficult to\nunderstand how the function worked, and made it hard make changes to\nsupport clusters. So as an initial cleanup, I\u0027ve separated out the\nfunctionality of initializing block bitmap from calculating the number\nof free blocks in the new block group.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "281b59959707dfae03ce038cdf231bf4904e170c", "tree": "3a6b36d060a41b19351c29c51d079149cae7511c", "parents": [ "7c2e70879fc0949b4220ee61b7c4553f6976a94d" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 18:34:51 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 09 18:34:51 2011 -0400" }, "message": "ext4: read-only support for bigalloc file systems\n\nThis adds supports for bigalloc file systems. It teaches the mount\ncode just enough about bigalloc superblock fields that it will mount\nthe file system without freaking out that the number of blocks per\ngroup is too big.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "56889787cfa77dfd96f0b3a3e6a4f26c2e4a5134", "tree": "5fb1be2d593fae0bb1a566397c58dc4f7ce010f2", "parents": [ "2be4751b21ae1cacb002da48cfc5bf6743fee8c1" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Sep 03 18:22:38 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Sep 03 18:22:38 2011 -0400" }, "message": "ext4: improve handling of conflicting mount options\n\nIf the user explicitly specifies conflicting mount options for\ndelalloc or dioread_nolock and data\u003djournal, fail the mount, instead\nof printing a warning and continuing (since many user\u0027s won\u0027t look at\ndmesg and notice the warning).\n\nAlso, print a single warning that data\u003djournal implies that delayed\nallocation is not on by default (since it\u0027s not supported), and\nfurthermore that O_DIRECT is not supported. Improve the text in\nDocumentation/filesystems/ext4.txt so this is clear there as well.\n\nSimilarly, if the dioread_nolock mount option is specified when the\nfile system block size !\u003d PAGE_SIZE, fail the mount instead of\nprinting a warning message and ignoring the mount option.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "4e96b2dbbf1d7e81f22047a50f862555a6cb87cb", "tree": "1f9c1d6712d1d16d3c6d04635019d2d1774c54d4", "parents": [ "5930ea643805feb50a2f8383ae12eb6f10935e49" ], "author": { "name": "Allison Henderson", "email": "achender@linux.vnet.ibm.com", "time": "Sat Sep 03 11:51:09 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Sep 03 11:51:09 2011 -0400" }, "message": "ext4: Add new ext4_discard_partial_page_buffers routines\n\nThis patch adds two new routines: ext4_discard_partial_page_buffers\nand ext4_discard_partial_page_buffers_no_lock.\n\nThe ext4_discard_partial_page_buffers routine is a wrapper\nfunction to ext4_discard_partial_page_buffers_no_lock.\nThe wrapper function locks the page and passes it to\next4_discard_partial_page_buffers_no_lock.\nCalling functions that already have the page locked can call\next4_discard_partial_page_buffers_no_lock directly.\n\nThe ext4_discard_partial_page_buffers_no_lock function\nzeros a specified range in a page, and unmaps the\ncorresponding buffer heads. Only block aligned regions of the\npage will have their buffer heads unmapped. Unblock aligned regions\nwill be mapped if needed so that they can be updated with the\npartial zero out. This function is meant to\nbe used to update a page and its buffer heads to be zeroed\nand unmapped when the corresponding blocks have been released\nor will be released.\n\nThis routine is used in the following scenarios:\n* A hole is punched and the non page aligned regions\n of the head and tail of the hole need to be discarded\n\n* The file is truncated and the partial page beyond EOF needs\n to be discarded\n\n* The end of a hole is in the same page as EOF. After the\n page is flushed, the partial page beyond EOF needs to be\n discarded.\n\n* A write operation begins or ends inside a hole and the partial\n page appearing before or after the write needs to be discarded\n\n* A write operation extends EOF and the partial page beyond EOF\n needs to be discarded\n\nThis function takes a flag EXT4_DISCARD_PARTIAL_PG_ZERO_UNMAPPED\nwhich is used when a write operation begins or ends in a hole.\nWhen the EXT4_DISCARD_PARTIAL_PG_ZERO_UNMAPPED flag is used, only\nbuffer heads that are already unmapped will have the corresponding\nregions of the page zeroed.\n\nSigned-off-by: Allison Henderson \u003cachender@linux.vnet.ibm.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "1cd9f0976aa4606db8d6e3dc3edd0aca8019372a", "tree": "3928541b60787c1add5120bb34a4016529de3d6b", "parents": [ "8c0bec2151a47906bf779c6715a10ce04453ab77" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Aug 31 11:54:51 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Aug 31 11:54:51 2011 -0400" }, "message": "ext2,ext3,ext4: don\u0027t inherit APPEND_FL or IMMUTABLE_FL for new inodes\n\nThis doesn\u0027t make much sense, and it exposes a bug in the kernel where\nattempts to create a new file in an append-only directory using\nO_CREAT will fail (but still leave a zero-length file). This was\ndiscovered when xfstests #79 was generalized so it could run on all\nfile systems.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nCc:stable@kernel.org\n" }, { "commit": "8c0bec2151a47906bf779c6715a10ce04453ab77", "tree": "0165e80ba408b5db1e9e2adf9264bf4186b06768", "parents": [ "fcb8ce5cfe30ca9ca5c9a79cdfe26d1993e65e0c" ], "author": { "name": "Jiaying Zhang", "email": "jiayingz@google.com", "time": "Wed Aug 31 11:50:51 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Aug 31 11:50:51 2011 -0400" }, "message": "ext4: remove i_mutex lock in ext4_evict_inode to fix lockdep complaining\n\nThe i_mutex lock and flush_completed_IO() added by commit 2581fdc810\nin ext4_evict_inode() causes lockdep complaining about potential\ndeadlock in several places. In most/all of these LOCKDEP complaints\nit looks like it\u0027s a false positive, since many of the potential\ncircular locking cases can\u0027t take place by the time the\next4_evict_inode() is called; but since at the very least it may mask\nreal problems, we need to address this.\n\nThis change removes the flush_completed_IO() and i_mutex lock in\next4_evict_inode(). Instead, we take a different approach to resolve\nthe software lockup that commit 2581fdc810 intends to fix. Rather\nthan having ext4-dio-unwritten thread wait for grabing the i_mutex\nlock of an inode, we use mutex_trylock() instead, and simply requeue\nthe work item if we fail to grab the inode\u0027s i_mutex lock.\n\nThis should speed up work queue processing in general and also\nprevents the following deadlock scenario: During page fault,\nshrink_icache_memory is called that in turn evicts another inode B.\nInode B has some pending io_end work so it calls ext4_ioend_wait()\nthat waits for inode B\u0027s i_ioend_count to become zero. However, inode\nB\u0027s ioend work was queued behind some of inode A\u0027s ioend work on the\nsame cpu\u0027s ext4-dio-unwritten workqueue. As the ext4-dio-unwritten\nthread on that cpu is processing inode A\u0027s ioend work, it tries to\ngrab inode A\u0027s i_mutex lock. Since the i_mutex lock of inode A is\nstill hold before the page fault happened, we enter a deadlock.\n\nSigned-off-by: Jiaying Zhang \u003cjiayingz@google.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "60ad4466821a96913a9b567115e194ed1087c2d7", "tree": "cd488ba72a60f856b85a467763fb633cbe7ef2d9", "parents": [ "1b8e94993c4752d98c33903aa836acc15f7e6d5c", "79a77c5ac34cc27ccbfbdf7113b41cdd93534eab" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Aug 01 13:56:03 2011 -1000" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Aug 01 13:56:03 2011 -1000" }, "message": "Merge branch \u0027for_linus\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4\n\n* \u0027for_linus\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4: (60 commits)\n ext4: prevent memory leaks from ext4_mb_init_backend() on error path\n ext4: use EXT4_BAD_INO for buddy cache to avoid colliding with valid inode #\n ext4: use ext4_msg() instead of printk in mballoc\n ext4: use ext4_kvzalloc()/ext4_kvmalloc() for s_group_desc and s_group_info\n ext4: introduce ext4_kvmalloc(), ext4_kzalloc(), and ext4_kvfree()\n ext4: use the correct error exit path in ext4_init_inode_table()\n ext4: add missing kfree() on error return path in add_new_gdb()\n ext4: change umode_t in tracepoint headers to be an explicit __u16\n ext4: fix races in ext4_sync_parent()\n ext4: Fix overflow caused by missing cast in ext4_fallocate()\n ext4: add action of moving index in ext4_ext_rm_idx for Punch Hole\n ext4: simplify parameters of reserve_backup_gdb()\n ext4: simplify parameters of add_new_gdb()\n ext4: remove lock_buffer in bclean() and setup_new_group_blocks()\n ext4: simplify journal handling in setup_new_group_blocks()\n ext4: let setup_new_group_blocks() set multiple bits at a time\n ext4: fix a typo in ext4_group_extend()\n ext4: let ext4_group_add_blocks() handle 0 blocks quickly\n ext4: let ext4_group_add_blocks() return an error code\n ext4: rename ext4_add_groupblocks() to ext4_group_add_blocks()\n ...\n\nFix up conflict in fs/ext4/inode.c: commit aacfc19c626e (\"fs: simplify\nthe blockdev_direct_IO prototype\") had changed the ext4_ind_direct_IO()\nfunction for the new simplified calling convention, while commit\ndae1e52cb126 (\"ext4: move ext4_ind_* functions from inode.c to\nindirect.c\") moved the function to another file.\n" }, { "commit": "9933fc0ac1ac14b795819cd63d05ea92112f690a", "tree": "bff42e3494fd5401e6b171ddae8f52ecd1defd91", "parents": [ "33853a0dde359ded0534204eb6857ad5166d515b" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Aug 01 08:45:02 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Aug 01 08:45:02 2011 -0400" }, "message": "ext4: introduce ext4_kvmalloc(), ext4_kzalloc(), and ext4_kvfree()\n\nIntroduce new helper functions which try kmalloc, and then fall back\nto vmalloc if necessary, and use them for allocating and deallocating\ns_flex_groups.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "c3e94d1df9bdd9e2c4ba7e8f534f7925f1756f97", "tree": "b0f23df82b491e04b64d7d67e4eecc80d1f4c6a0", "parents": [ "2b79b09d13e35577151bd13ba08809911baccd1c" ], "author": { "name": "Yongqiang Yang", "email": "xiaoqiangnk@gmail.com", "time": "Tue Jul 26 22:05:53 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jul 26 22:05:53 2011 -0400" }, "message": "ext4: let setup_new_group_blocks() set multiple bits at a time\n\nRename mb_set_bits() to ext4_set_bits() and make it a global function\nso that setup_new_group_blocks() can use it.\n\nSigned-off-by: Yongqiang Yang \u003cxiaoqiangnk@gmail.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "cc7365dfe48cb2191f1572bf69e30d3e58716313", "tree": "1d0a533d6ffcee71900894741995a1d0cf91ab0f", "parents": [ "0529155e8a4bcb77dfc9ceaea19c6501487e452b" ], "author": { "name": "Yongqiang Yang", "email": "xiaoqiangnk@gmail.com", "time": "Tue Jul 26 21:46:07 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jul 26 21:46:07 2011 -0400" }, "message": "ext4: let ext4_group_add_blocks() return an error code\n\nThis patch lets ext4_group_add_blocks() return an error code if it\nfails, so that upper functions can handle error correctly.\n\nSigned-off-by: Yongqiang Yang \u003cxiaoqiangnk@gmail.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "0529155e8a4bcb77dfc9ceaea19c6501487e452b", "tree": "a67262d87fcfa101ea8ea3af9d90725a9de22f2c", "parents": [ "ce723c31b58f54fb865036805475ee7a8c5dc173" ], "author": { "name": "Yongqiang Yang", "email": "xiaoqiangnk@gmail.com", "time": "Tue Jul 26 21:43:56 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jul 26 21:43:56 2011 -0400" }, "message": "ext4: rename ext4_add_groupblocks() to ext4_group_add_blocks()\n\nSigned-off-by: Yongqiang Yang \u003cxiaoqiangnk@gmail.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "8f82f840ec6ab873f520364d443ff6fa1b3f8e22", "tree": "72d90cdc8f7311ef913b7471e53f718bebbf7414", "parents": [ "2d859db3e4a82a365572592d57624a5f996ed0ec" ], "author": { "name": "Yongqiang Yang", "email": "xiaoqiangnk@gmail.com", "time": "Tue Jul 26 21:35:44 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jul 26 21:35:44 2011 -0400" }, "message": "ext4: prevent parallel resizers by atomic bit ops\n\nBefore this patch, parallel resizers are allowed and protected by a\nmutex lock, actually, there is no need to support parallel resizer, so\nthis patch prevents parallel resizers by atmoic bit ops, like\nlock_page() and unlock_page() do.\n\nTo do this, the patch removed the mutex lock s_resize_lock from struct\next4_sb_info and added a unsigned long field named s_resize_flags\nwhich inidicates if there is a resizer.\n\nSigned-off-by: Yongqiang Yang \u003cxiaoqiangnk@gmail.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "02c24a82187d5a628c68edfe71ae60dc135cd178", "tree": "c8dbaba4d82e2b20ed4335910a564a1f7d90fcf6", "parents": [ "22735068d53c7115e384bc88dea95b17e76a6839" ], "author": { "name": "Josef Bacik", "email": "josef@redhat.com", "time": "Sat Jul 16 20:44:56 2011 -0400" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Wed Jul 20 20:47:59 2011 -0400" }, "message": "fs: push i_mutex and filemap_write_and_wait down into -\u003efsync() handlers\n\nBtrfs needs to be able to control how filemap_write_and_wait_range() is called\nin fsync to make it less of a painful operation, so push down taking i_mutex and\nthe calling of filemap_write_and_wait() down into the -\u003efsync() handlers. Some\nfile systems can drop taking the i_mutex altogether it seems, like ext3 and\nocfs2. For correctness sake I just pushed everything down in all cases to make\nsure that we keep the current behavior the same for everybody, and then each\nindividual fs maintainer can make up their mind about what to do from there.\nThanks,\n\nAcked-by: Jan Kara \u003cjack@suse.cz\u003e\nSigned-off-by: Josef Bacik \u003cjosef@redhat.com\u003e\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "3d56b8d2c74cc3f375ce332b3ac3519e009d79ee", "tree": "47c13dc80779a3d8d93902897a500b056375689c", "parents": [ "b3d4c2b10b68d205d3eb1b5c17dcb4649a502798" ], "author": { "name": "Tao Ma", "email": "boyu.mt@taobao.com", "time": "Mon Jul 11 00:03:38 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jul 11 00:03:38 2011 -0400" }, "message": "ext4: Speed up FITRIM by recording flags in ext4_group_info\n\nIn ext4, when FITRIM is called every time, we iterate all the\ngroups and do trim one by one. It is a bit time wasting if the\ngroup has been trimmed and there is no change since the last\ntrim.\n\nSo this patch adds a new flag in ext4_group_info-\u003ebb_state to\nindicate that the group has been trimmed, and it will be cleared\nif some blocks is freed(in release_blocks_on_commit). Another\ntrim_minlen is added in ext4_sb_info to record the last minlen\nwe use to trim the volume, so that if the caller provide a small\none, we will go on the trim regardless of the bb_state.\n\nA simple test with my intel x25m ssd:\ndf -h shows:\n/dev/sdb1 40G 21G 17G 56% /mnt/ext4\nBlock size: 4096\n\nrun the FITRIM with the following parameter:\nrange.start \u003d 0;\nrange.len \u003d UINT64_MAX;\nrange.minlen \u003d 1048576;\n\nwithout the patch:\n[root@boyu-tm linux-2.6]# time ./ftrim /mnt/ext4/a\nreal\t0m5.505s\nuser\t0m0.000s\nsys\t0m1.224s\n[root@boyu-tm linux-2.6]# time ./ftrim /mnt/ext4/a\nreal\t0m5.359s\nuser\t0m0.000s\nsys\t0m1.178s\n[root@boyu-tm linux-2.6]# time ./ftrim /mnt/ext4/a\nreal\t0m5.228s\nuser\t0m0.000s\nsys\t0m1.151s\n\nwith the patch:\n[root@boyu-tm linux-2.6]# time ./ftrim /mnt/ext4/a\nreal\t0m5.625s\nuser\t0m0.000s\nsys\t0m1.269s\n[root@boyu-tm linux-2.6]# time ./ftrim /mnt/ext4/a\nreal\t0m0.002s\nuser\t0m0.000s\nsys\t0m0.001s\n[root@boyu-tm linux-2.6]# time ./ftrim /mnt/ext4/a\nreal\t0m0.002s\nuser\t0m0.000s\nsys\t0m0.001s\n\nA big improvement for the 2nd and 3rd run.\n\nEven after I delete some big image files, it is still much\nfaster than iterating the whole disk.\n\n[root@boyu-tm test]# time ./ftrim /mnt/ext4/a\nreal\t0m1.217s\nuser\t0m0.000s\nsys\t0m0.196s\n\nCc: Lukas Czerner \u003clczerner@redhat.com\u003e\nReviewed-by: Andreas Dilger \u003cadilger.kernel@dilger.ca\u003e\nSigned-off-by: Tao Ma \u003cboyu.mt@taobao.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "7132de744ba76930d13033061018ddd7e3e8cd91", "tree": "1da773f7293e056e4849dc590dac35854662f666", "parents": [ "275d3ba6b40d0f098693b9089c6fee9bd4e55d74" ], "author": { "name": "Maxim Patlasov", "email": "maxim.patlasov@gmail.com", "time": "Sun Jul 10 19:37:48 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sun Jul 10 19:37:48 2011 -0400" }, "message": "ext4: fix i_blocks/quota accounting when extent insertion fails\n\nThe current implementation of ext4_free_blocks() always calls\ndquot_free_block This looks quite sensible in the most cases: blocks\nto be freed are associated with inode and were accounted in quota and\ni_blocks some time ago.\n\nHowever, there is a case when blocks to free were not accounted by the\ntime calling ext4_free_blocks() yet:\n\n1. delalloc is on, write_begin pre-allocated some space in quota\n2. write-back happens, ext4 allocates some blocks in ext4_ext_map_blocks()\n3. then ext4_ext_map_blocks() gets an error (e.g. ENOSPC) from\n ext4_ext_insert_extent() and calls ext4_free_blocks().\n\nIn this scenario, ext4_free_blocks() calls dquot_free_block() who, in\nturn, decrements i_blocks for blocks which were not accounted yet (due\nto delalloc) After clean umount, e2fsck reports something like:\n\n\u003e Inode 21, i_blocks is 5080, should be 5128. Fix\u003cy\u003e?\nbecause i_blocks was erroneously decremented as explained above.\n\nThe patch fixes the problem by passing the new flag\nEXT4_FREE_BLOCKS_NO_QUOT_UPDATE to ext4_free_blocks(), to request\nthat the dquot_free_block() call be skipped.\n\nSigned-off-by: Maxim Patlasov \u003cmaxim.patlasov@gmail.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nCc: stable@kernel.org\n" }, { "commit": "f86186b44b4164600cce03d0d93ad48ec21fa429", "tree": "48aafabbbe46d22de84e4e9b3ebf7c5b35fd6d1e", "parents": [ "dae1e52cb1267bf8f52e5e47a80fab566d7e8aa4" ], "author": { "name": "Eric Sandeen", "email": "sandeen@redhat.com", "time": "Tue Jun 28 10:01:31 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jun 28 10:01:31 2011 -0400" }, "message": "ext4: refactor duplicated block placement code\n\nI found that ext4_ext_find_goal() and ext4_find_near()\nshare the same code for returning a coloured start block\nbased on i_block_group.\n\nWe can refactor this into a common function so that they\ndon\u0027t diverge in the future.\n\nThanks to adilger for suggesting the new function name.\n\nSigned-off-by: Eric Sandeen \u003csandeen@redhat.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "dae1e52cb1267bf8f52e5e47a80fab566d7e8aa4", "tree": "2537e9f8f138e4935f88e605244174c9b2400bf4", "parents": [ "9f125d641beb898f5bf2fe69583192c18043517a" ], "author": { "name": "Amir Goldstein", "email": "amir73il@users.sf.net", "time": "Mon Jun 27 19:40:50 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jun 27 19:40:50 2011 -0400" }, "message": "ext4: move ext4_ind_* functions from inode.c to indirect.c\n\nThis patch moves functions from inode.c to indirect.c.\nThe moved functions are ext4_ind_* functions and their helpers.\nFunctions called from inode.c are declared extern.\n\nSigned-off-by: Amir Goldstein \u003camir73il@users.sf.net\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "1f7d1e77419050831a905353683807fa69a26625", "tree": "0f32626160b1ecab1e6067ff0e94746c3da068c4", "parents": [ "8bb2b247124ba6093455d4aef26743b1bef27bc5" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jun 27 19:16:02 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jun 27 19:16:02 2011 -0400" }, "message": "ext4: move __ext4_check_blockref to block_validity.c\n\nIn preparation for moving the indirect functions to a separate file,\nmove __ext4_check_blockref() to block_validity.c and rename it to\next4_check_blockref() which is exported as globally visible function.\n\nAlso, rename the cpp macro ext4_check_inode_blockref() to\next4_ind_check_inode(), to make it clear that it is only valid for use\nwith non-extent mapped inodes.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "ff9893dc8aa622a4f122293a6861566a284edea5", "tree": "ca7d798360c32379fb4d3d0913d349ac79f55c6d", "parents": [ "ed7a7e16724a4123fce1fc0ff1f5131a0596f189" ], "author": { "name": "Amir Goldstein", "email": "amir73il@users.sf.net", "time": "Mon Jun 27 16:36:31 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jun 27 16:36:31 2011 -0400" }, "message": "ext4: split ext4_ind_truncate from ext4_truncate\n\nWe are about to move all indirect inode functions to a new file.\nBefore we do that, let\u0027s split ext4_ind_truncate() out of ext4_truncate()\nleaving only generic code in the latter, so we will be able to move\next4_ind_truncate() to the new file.\n\nSigned-off-by: Amir Goldstein \u003camir73il@users.sf.net\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "aa38572954ade525817fe88c54faebf85e5a61c0", "tree": "ef398ec06c97134592f62a49c99f3f80041b427c", "parents": [ "d6e9bd256c88ce5f4b668249e363a74f51393daa" ], "author": { "name": "Christoph Hellwig", "email": "hch@infradead.org", "time": "Fri May 27 06:53:02 2011 -0400" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Fri May 27 07:04:40 2011 -0400" }, "message": "fs: pass exact type of data dirties to -\u003edirty_inode\n\nTell the filesystem if we just updated timestamp (I_DIRTY_SYNC) or\nanything else, so that the filesystem can track internally if it\nneeds to push out a transaction for fdatasync or not.\n\nThis is just the prototype change with no user for it yet. I plan\nto push large XFS changes for the next merge window, and getting\nthis trivial infrastructure in this window would help a lot to avoid\ntree interdependencies.\n\nAlso remove incorrect comments that -\u003edirty_inode can\u0027t block. That\nhas been changed a long time ago, and many implementations rely on it.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "556b27abf73833923d5cd4be80006292e1b31662", "tree": "588fa7c3db66afb545921cdfc894f0a41e66dc49", "parents": [ "a4bb6b64e39abc0e41ca077725f2a72c868e7622" ], "author": { "name": "Vivek Haldar", "email": "haldar@google.com", "time": "Wed May 25 07:41:54 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed May 25 07:41:54 2011 -0400" }, "message": "ext4: do not normalize block requests from fallocate()\n\nCurrently, an fallocate request of size slightly larger than a power of\n2 is turned into two block requests, each a power of 2, with the extra\nblocks pre-allocated for future use. When an application calls\nfallocate, it already has an idea about how large the file may grow so\nthere is usually little benefit to reserve extra blocks on the\npreallocation list. This reduces disk fragmentation.\n\nTested: fsstress. Also verified manually that fallocat\u0027ed files are\ncontiguously laid out with this change (whereas without it they begin at\npower-of-2 boundaries, leaving blocks in between). CPU usage of\nfallocate is not appreciably higher. In a tight fallocate loop, CPU\nusage hovers between 5%-8% with this change, and 5%-7% without it.\n\nUsing a simulated file system aging program which the file system to\n70%, the percentage of free extents larger than 8MB (as measured by\ne2freefrag) increased from 38.8% without this change, to 69.4% with\nthis change.\n\nSigned-off-by: Vivek Haldar \u003chaldar@google.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "a4bb6b64e39abc0e41ca077725f2a72c868e7622", "tree": "0d911caa13d445d64cce5ea37f424bf066731ea6", "parents": [ "e861304b8ed83fe43e36d46794d72641c82d4636" ], "author": { "name": "Allison Henderson", "email": "achender@linux.vnet.ibm.com", "time": "Wed May 25 07:41:50 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed May 25 07:41:50 2011 -0400" }, "message": "ext4: enable \"punch hole\" functionality\n\nThis patch adds new routines: \"ext4_punch_hole\" \"ext4_ext_punch_hole\"\nand \"ext4_ext_check_cache\"\n\nfallocate has been modified to call ext4_punch_hole when the punch hole\nflag is passed. At the moment, we only support punching holes in\nextents, so this routine is pretty much a wrapper for the ext4_ext_punch_hole\nroutine.\n\nThe ext4_ext_punch_hole routine first completes all outstanding writes\nwith the associated pages, and then releases them. The unblock\naligned data is zeroed, and all blocks in between are punched out.\n\nThe ext4_ext_check_cache routine is very similar to ext4_ext_in_cache\nexcept it accepts a ext4_ext_cache parameter instead of a ext4_extent\nparameter. This routine is used by ext4_ext_punch_hole to check and\nsee if a block in a hole that has been cached. The ext4_ext_cache\nparameter is necessary because the members ext4_extent structure are\nnot large enough to hold a 32 bit value. The existing\next4_ext_in_cache routine has become a wrapper to this new function.\n\n[ext4 punch hole patch series 5/5 v7] \n\nSigned-off-by: Allison Henderson \u003cachender@us.ibm.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nReviewed-by: Mingming Cao \u003ccmm@us.ibm.com\u003e\n" }, { "commit": "308488518dfcbe3be250085cd582f5b0c1ce72a9", "tree": "4696b50debf9794f2cbb966cccbedadb93dc996a", "parents": [ "55f020db66ce187fb8c8e4002a94b0eb714da450" ], "author": { "name": "Allison Henderson", "email": "achender@linux.vnet.ibm.com", "time": "Wed May 25 07:41:32 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed May 25 07:41:32 2011 -0400" }, "message": "ext4: add new function ext4_block_zero_page_range()\n\nThis patch modifies the existing ext4_block_truncate_page() function\nwhich was used by the truncate code path, and which zeroes out block\nunaligned data, by adding a new length parameter, and renames it to\next4_block_zero_page_rage(). This function can now be used to zero out the\nhead of a block, the tail of a block, or the middle\nof a block.\n\nThe ext4_block_truncate_page() function is now a wrapper to\next4_block_zero_page_range().\n\n[ext4 punch hole patch series 2/5 v7] \n\nSigned-off-by: Allison Henderson \u003cachender@us.ibm.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nReviewed-by: Mingming Cao \u003ccmm@us.ibm.com\u003e\n" }, { "commit": "55f020db66ce187fb8c8e4002a94b0eb714da450", "tree": "e98214511542f57fa93074be12e27c4819520333", "parents": [ "ae81230686282af745ebb7a74c0332349cb9131a" ], "author": { "name": "Allison Henderson", "email": "achender@linux.vnet.ibm.com", "time": "Wed May 25 07:41:26 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed May 25 07:41:26 2011 -0400" }, "message": "ext4: add flag to ext4_has_free_blocks\n\nThis patch adds an allocation request flag to the ext4_has_free_blocks\nfunction which enables the use of reserved blocks. This will allow a\npunch hole to proceed even if the disk is full. Punching a hole may\nrequire additional blocks to first split the extents.\n\nBecause ext4_has_free_blocks is a low level function, the flag needs\nto be passed down through several functions listed below:\n\next4_ext_insert_extent\next4_ext_create_new_leaf\next4_ext_grow_indepth\next4_ext_split\next4_ext_new_meta_block\next4_mb_new_blocks\next4_claim_free_blocks\next4_has_free_blocks\n\n[ext4 punch hole patch series 1/5 v7]\n\nSigned-off-by: Allison Henderson \u003cachender@us.ibm.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nReviewed-by: Mingming Cao \u003ccmm@us.ibm.com\u003e\n" }, { "commit": "ae81230686282af745ebb7a74c0332349cb9131a", "tree": "bd293ae7a338e582991ecb2930397fb7b010c6cc", "parents": [ "c5e06d101aaf72f1f2192a661414459775e9bd74" ], "author": { "name": "Aditya Kali", "email": "adityakali@google.com", "time": "Tue May 24 19:00:39 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue May 24 19:00:39 2011 -0400" }, "message": "ext4: reserve inodes and feature code for \u0027quota\u0027 feature\n\nI am working on patch to add quota as a built-in feature for ext4\nfilesystem. The implementation is based on the design given at\nhttps://ext4.wiki.kernel.org/index.php/Design_For_1st_Class_Quota_in_Ext4.\nThis patch reserves the inode numbers 3 and 4 for quota purposes and\nalso reserves EXT4_FEATURE_RO_COMPAT_QUOTA feature code.\n\nSigned-off-by: Aditya Kali \u003cadityakali@google.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "c5e06d101aaf72f1f2192a661414459775e9bd74", "tree": "96d05d41be2bfea6d51be915ce196f033a5d9bf3", "parents": [ "d02a9391f79cab65cde74cd9e8ccd2290a565229" ], "author": { "name": "Johann Lombardi", "email": "johann@whamcloud.com", "time": "Tue May 24 18:31:25 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue May 24 18:31:25 2011 -0400" }, "message": "ext4: add support for multiple mount protection\n\nPrevent an ext4 filesystem from being mounted multiple times.\nA sequence number is stored on disk and is periodically updated (every 5\nseconds by default) by a mounted filesystem.\nAt mount time, we now wait for s_mmp_update_interval seconds to make sure\nthat the MMP sequence does not change.\nIn case of failure, the nodename, bdevname and the time at which the MMP\nblock was last updated is displayed.\n\nSigned-off-by: Andreas Dilger \u003cadilger@whamcloud.com\u003e\nSigned-off-by: Johann Lombardi \u003cjohann@whamcloud.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "77f4135f2a219a2127be6cc1208c42e6175b11dd", "tree": "8f85549d2354c5a69a5b29197f68a554daad1324", "parents": [ "93917411be8db5d21abf15c781dfa43c5cc6edf2" ], "author": { "name": "Vivek Haldar", "email": "haldar@google.com", "time": "Sun May 22 21:24:16 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sun May 22 21:24:16 2011 -0400" }, "message": "ext4: count hits/misses of extent cache and expose in sysfs\n\nThe number of hits and misses for each filesystem is exposed in\n/sys/fs/ext4/\u003cdev\u003e/extent_cache_{hits, misses}.\n\nTested: fsstress, manual checks.\nSigned-off-by: Vivek Haldar \u003chaldar@google.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "e1290b3e62c496ade19939ce036f35bb69306820", "tree": "aaf8fc2fd2b9b7c9c1ce15303bb8debf7ab3d01b", "parents": [ "4ed5c033c11b33149d993734a6a8de1016e8f03f" ], "author": { "name": "Lukas Czerner", "email": "lczerner@redhat.com", "time": "Fri May 20 13:49:51 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri May 20 13:49:51 2011 -0400" }, "message": "ext4: Remove unnecessary wait_event ext4_run_lazyinit_thread()\n\nFor some reason we have been waiting for lazyinit thread to start in the\next4_run_lazyinit_thread() but it is not needed since it was jus\nunnecessary complexity, so get rid of it. We can also remove li_task and\nli_wait_task since it is not used anymore.\n\nSigned-off-by: Lukas Czerner \u003clczerner@redhat.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nReviewed-by: Eric Sandeen \u003csandeen@redhat.com\u003e\n" }, { "commit": "4ed5c033c11b33149d993734a6a8de1016e8f03f", "tree": "826892fddc9cef7cbfac541eb13bb8eebc95c539", "parents": [ "0e499890c1fd9e0a1bed02002161c4c7873d7489" ], "author": { "name": "Lukas Czerner", "email": "lczerner@redhat.com", "time": "Fri May 20 13:49:04 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri May 20 13:49:04 2011 -0400" }, "message": "ext4: Use schedule_timeout_interruptible() for waiting in lazyinit thread\n\nIn order to make lazyinit eat approx. 10% of io bandwidth at max, we\nare sleeping between zeroing each single inode table. For that purpose\nwe are using timer which wakes up thread when it expires. It is set\nvia add_timer() and this may cause troubles in the case that thread\nhas been woken up earlier and in next iteration we call add_timer() on\nstill running timer hence hitting BUG_ON in add_timer(). We could fix\nthat by using mod_timer() instead however we can use\nschedule_timeout_interruptible() for waiting and hence simplifying\nthings a lot.\n\nThis commit exchange the old \"waiting mechanism\" with simple\nschedule_timeout_interruptible(), setting the time to sleep. Hence we\ndo not longer need li_wait_daemon waiting queue and others, so get rid\nof it.\n\nAddresses-Red-Hat-Bugzilla: #699708\n\nSigned-off-by: Lukas Czerner \u003clczerner@redhat.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nReviewed-by: Eric Sandeen \u003csandeen@redhat.com\u003e\n" }, { "commit": "2846e82004a8d5ef0a63cd3209c84ea5cd796f11", "tree": "3b20c08ce64e918d4217bb95228fc597c63bf0e0", "parents": [ "66bb82798d9ff896271d13f5020f7fb9b7d88e1a" ], "author": { "name": "Amir Goldstein", "email": "amir73il@users.sf.net", "time": "Mon May 09 10:46:41 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon May 09 10:46:41 2011 -0400" }, "message": "ext4: move ext4_add_groupblocks() to mballoc.c\n\nIn preparation for the next patch, the function ext4_add_groupblocks()\nis moved to mballoc.c, where it could use some static functions.\n\nSigned-off-by: Amir Goldstein \u003camir73il@users.sf.net\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "2035e776050aea57fb5255557216473e82793f2c", "tree": "6a97e536fd5fbdc29e4b471195a5dd5a0df35fc6", "parents": [ "26626f1172fb4f3f323239a6a5cf4e082643fa46" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Apr 18 17:29:14 2011 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Apr 18 17:29:14 2011 -0400" }, "message": "ext4: check for ext[23] file system features when mounting as ext[23]\n\nProvide better emulation for ext[23] mode by enforcing that the file\nsystem does not have any unsupported file system features as defined\nby ext[23] when emulating the ext[23] file system driver when\nCONFIG_EXT4_USE_FOR_EXT23 is defined.\n\nThis causes the file system type information in /proc/mounts to be\ncorrect for the automatically mounted root file system. This also\nmeans that \"mount -t ext2 /dev/sda /mnt\" will fail if /dev/sda\ncontains an ext3 or ext4 file system, just as one would expect if the\noriginal ext2 file system driver were in use.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "50e0168cc3406fc1a04d57eb08f500a173d1660d", "tree": "19f8e15048c37bfface138e19eb93855e02c266c", "parents": [ "0795ccea24714c790187e3d4f23c8e5be515f42d" ], "author": { "name": "Akinobu Mita", "email": "akinobu.mita@gmail.com", "time": "Wed Mar 23 16:42:07 2011 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Wed Mar 23 19:46:17 2011 -0700" }, "message": "ext4: use little-endian bitops\n\nAs a preparation for removing ext2 non-atomic bit operations from\nasm/bitops.h. This converts ext2 non-atomic bit operations to\nlittle-endian bit operations.\n\nSigned-off-by: Akinobu Mita \u003cakinobu.mita@gmail.com\u003e\nAcked-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nCc: Andreas Dilger \u003cadilger.kernel@dilger.ca\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "e9e3bcecf44c04b9e6b505fd8e2eb9cea58fb94d", "tree": "9f347a48889a00071dbe1f12be4c50ec7a45542b", "parents": [ "2892c15ddda6a76dc10b7499e56c0f3b892e5a69" ], "author": { "name": "Eric Sandeen", "email": "sandeen@redhat.com", "time": "Sat Feb 12 08:17:34 2011 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Feb 12 08:17:34 2011 -0500" }, "message": "ext4: serialize unaligned asynchronous DIO\n\next4 has a data corruption case when doing non-block-aligned\nasynchronous direct IO into a sparse file, as demonstrated\nby xfstest 240.\n\nThe root cause is that while ext4 preallocates space in the\nhole, mappings of that space still look \"new\" and \ndio_zero_block() will zero out the unwritten portions. When\nmore than one AIO thread is going, they both find this \"new\"\nblock and race to zero out their portion; this is uncoordinated\nand causes data corruption.\n\nDave Chinner fixed this for xfs by simply serializing all\nunaligned asynchronous direct IO. I\u0027ve done the same here.\nThe difference is that we only wait on conversions, not all IO.\nThis is a very big hammer, and I\u0027m not very pleased with\nstuffing this into ext4_file_write(). But since ext4 is\nDIO_LOCKING, we need to serialize it at this high level.\n\nI tried to move this into ext4_ext_direct_IO, but by then\nwe have the i_mutex already, and we will wait on the\nwork queue to do conversions - which must also take the\ni_mutex. So that won\u0027t work.\n\nThis was originally exposed by qemu-kvm installing to\na raw disk image with a normal sector-63 alignment. I\u0027ve\ntested a backport of this patch with qemu, and it does\navoid the corruption. It is also quite a lot slower\n(14 min for package installs, vs. 8 min for well-aligned)\nbut I\u0027ll take slow correctness over fast corruption any day.\n\nMingming suggested that we can track outstanding\nconversions, and wait on those so that non-sparse\nfiles won\u0027t be affected, and I\u0027ve implemented that here;\nunaligned AIO to nonsparse files won\u0027t take a perf hit.\n\n[tytso@mit.edu: Keep the mutex as a hashed array instead\n of bloating the ext4 inode]\n\n[tytso@mit.edu: Fix up namespace issues so that global\n variables are protected with an \"ext4_\" prefix.]\n\nSigned-off-by: Eric Sandeen \u003csandeen@redhat.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "2fe17c1075836b66678ed2a305fd09b6773883aa", "tree": "eb5287be8138686682eef9622872cfc7657e0664", "parents": [ "64c23e86873ee410554d6d1c76b60da47025e96f" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Fri Jan 14 13:07:43 2011 +0100" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Mon Jan 17 02:25:31 2011 -0500" }, "message": "fallocate should be a file operation\n\nCurrently all filesystems except XFS implement fallocate asynchronously,\nwhile XFS forced a commit. Both of these are suboptimal - in case of O_SYNC\nI/O we really want our allocation on disk, especially for the !KEEP_SIZE\ncase where we actually grow the file with user-visible zeroes. On the\nother hand always commiting the transaction is a bad idea for fast-path\nuses of fallocate like for example in recent Samba versions. Given\nthat block allocation is a data plane operation anyway change it from\nan inode operation to a file operation so that we have the file structure\navailable that lets us check for O_SYNC.\n\nThis also includes moving the code around for a few of the filesystems,\nand remove the already unnedded S_ISDIR checks given that we only wire\nup fallocate for regular files.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "008d23e4852d78bb2618f2035f8b2110b6a6b968", "tree": "81c88f744f6f3fc84132527c1ddc0b4da410c5e2", "parents": [ "8f685fbda43deccd130d192c9fcef1444649eaca", "bfc672dcf323877228682aff79dff8ecd9f30ff8" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Jan 13 10:05:56 2011 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Jan 13 10:05:56 2011 -0800" }, "message": "Merge branch \u0027for-next\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial\n\n* \u0027for-next\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial: (43 commits)\n Documentation/trace/events.txt: Remove obsolete sched_signal_send.\n writeback: fix global_dirty_limits comment runtime -\u003e real-time\n ppc: fix comment typo singal -\u003e signal\n drivers: fix comment typo diable -\u003e disable.\n m68k: fix comment typo diable -\u003e disable.\n wireless: comment typo fix diable -\u003e disable.\n media: comment typo fix diable -\u003e disable.\n remove doc for obsolete dynamic-printk kernel-parameter\n remove extraneous \u0027is\u0027 from Documentation/iostats.txt\n Fix spelling milisec -\u003e ms in snd_ps3 module parameter description\n Fix spelling mistakes in comments\n Revert conflicting V4L changes\n i7core_edac: fix typos in comments\n mm/rmap.c: fix comment\n sound, ca0106: Fix assignment to \u0027channel\u0027.\n hrtimer: fix a typo in comment\n init/Kconfig: fix typo\n anon_inodes: fix wrong function name in comment\n fix comment typos concerning \"consistent\"\n poll: fix a typo in comment\n ...\n\nFix up trivial conflicts in:\n - drivers/net/wireless/iwlwifi/iwl-core.c (moved to iwl-legacy.c)\n - fs/ext4/ext4.h\n\nAlso fix missed \u0027diabled\u0027 typo in drivers/net/bnx2x/bnx2x.h while at it.\n" }, { "commit": "3889fd57ea3c58209354862523275774fca9db03", "tree": "1e68fb9b2691c0b792a36be7d87c987e8508dac6", "parents": [ "b40971426a837e9dc9c66e1b6bbcb3874eafe4e0" ], "author": { "name": "Jiaying Zhang", "email": "jiayingz@google.com", "time": "Mon Jan 10 12:47:05 2011 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 10 12:47:05 2011 -0500" }, "message": "ext4: flush the i_completed_io_list during ext4_truncate\n\nTed first found the bug when running 2.6.36 kernel with dioread_nolock\nmount option that xfstests #13 complained about wrong file size during fsck.\nHowever, the bug exists in the older kernels as well although it is\nsomehow harder to trigger.\n\nThe problem is that ext4_end_io_work() can happen after we have truncated an\ninode to a smaller size. Then when ext4_end_io_work() calls \next4_convert_unwritten_extents(), we may reallocate some blocks that have \nbeen truncated, so the inode size becomes inconsistent with the allocated\nblocks. \n\nThe following patch flushes the i_completed_io_list during truncate to reduce \nthe risk that some pending end_io requests are executed later and convert \nalready truncated blocks to initialized. \n\nNote that although the fix helps reduce the problem a lot there may still \nbe a race window between vmtruncate() and ext4_end_io_work(). The fundamental\nproblem is that if vmtruncate() is called without either i_mutex or i_alloc_sem\nheld, it can race with an ongoing write request so that the io_end request is\nprocessed later when the corresponding blocks have been truncated.\n\nTed and I have discussed the problem offline and we saw a few ways to fix\nthe race completely:\n\na) We guarantee that i_mutex lock and i_alloc_sem write lock are both hold \nwhenever vmtruncate() is called. The i_mutex lock prevents any new write\nrequests from entering writeback and the i_alloc_sem prevents the race\nfrom ext4_page_mkwrite(). Currently we hold both locks if vmtruncate()\nis called from do_truncate(), which is probably the most common case.\nHowever, there are places where we may call vmtruncate() without holding\neither i_mutex or i_alloc_sem. I would like to ask for other people\u0027s\nopinions on what locks are expected to be held before calling vmtruncate().\nThere seems a disagreement among the callers of that function.\n\nb) We change the ext4 write path so that we change the extent tree to contain \nthe newly allocated blocks and update i_size both at the same time --- when \nthe write of the data blocks is completed.\n\nc) We add some additional locking to synchronize vmtruncate() and \next4_end_io_work(). This approach may have performance implications so we\nneed to be careful.\n\nAll of the above proposals may require more substantial changes, so\nwe may consider to take the following patch as a bandaid.\n\nSigned-off-by: Jiaying Zhang \u003cjiayingz@google.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n\n" }, { "commit": "8aefcd557d26d0023a36f9ec5afbf55e59f8f26b", "tree": "e13143306cd64525cddd2cc2513c448275a1d95a", "parents": [ "353eb83c1422c6326eaab30ce044a179c6018169" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 10 12:29:43 2011 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 10 12:29:43 2011 -0500" }, "message": "ext4: dynamically allocate the jbd2_inode in ext4_inode_info as necessary\n\nReplace the jbd2_inode structure (which is 48 bytes) with a pointer\nand only allocate the jbd2_inode when it is needed --- that is, when\nthe file system has a journal present and the inode has been opened\nfor writing. This allows us to further slim down the ext4_inode_info\nstructure.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "353eb83c1422c6326eaab30ce044a179c6018169", "tree": "fd43e39b344de5ee43d82c90f0affda68a65f2df", "parents": [ "8a2005d3f84457b7d7d8646ab5195341d9e5f06a" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 10 12:18:25 2011 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 10 12:18:25 2011 -0500" }, "message": "ext4: drop i_state_flags on architectures with 64-bit longs\n\nWe can store the dynamic inode state flags in the high bits of\nEXT4_I(inode)-\u003ei_flags, and eliminate i_state_flags. This saves 8\nbytes from the size of ext4_inode_info structure, which when\nmultiplied by the number of the number of in the inode cache, can save\na lot of memory.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "8a2005d3f84457b7d7d8646ab5195341d9e5f06a", "tree": "4d94161103e806435745e1544fb24e6398b2e06b", "parents": [ "b05e6ae58a13b56e3e11882c1fc71948c9b29760" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 10 12:13:42 2011 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 10 12:13:42 2011 -0500" }, "message": "ext4: reorder ext4_inode_info structure elements to remove unneeded padding\n\nBy reordering the elements in the ext4_inode_info structure, we can\nreduce the padding needed on an x86_64 system by 16 bytes.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "b05e6ae58a13b56e3e11882c1fc71948c9b29760", "tree": "452cbadcbc8091b4db95f917f28b0f9de845dabf", "parents": [ "01f49d0b9d0209dc1194255b11601e4b94447b36" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 10 12:13:26 2011 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 10 12:13:26 2011 -0500" }, "message": "ext4: drop ec_type from the ext4_ext_cache structure\n\nWe can encode the ec_type information by using ee_len \u003d\u003d 0 to denote\nEXT4_EXT_CACHE_NO, ee_start \u003d\u003d 0 to denote EXT4_EXT_CACHE_GAP, and if\nneither is true, then the cache type must be EXT4_EXT_CACHE_EXTENT.\nThis allows us to reduce the size of ext4_ext_inode by another 8\nbytes. (ec_type is 4 bytes, plus another 4 bytes of padding)\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n\n" }, { "commit": "01f49d0b9d0209dc1194255b11601e4b94447b36", "tree": "c3ec53c7725bf7a9188e844d8c8c09432d2be6ae", "parents": [ "f232109773ff5b0c840a6761d74940b9cf0d66ec" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 10 12:13:03 2011 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 10 12:13:03 2011 -0500" }, "message": "ext4: use ext4_lblk_t instead of sector_t for logical blocks\n\nThis fixes a number of places where we used sector_t instead of\next4_lblk_t for logical blocks, which for ext4 are still 32-bit data\ntypes. No point wasting space in the ext4_inode_info structure, and\nrequiring 64-bit arithmetic on 32-bit systems, when it isn\u0027t\nnecessary.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "f232109773ff5b0c840a6761d74940b9cf0d66ec", "tree": "a32da5ebd1a3e074e9f52107f3bdc23babb6340c", "parents": [ "ad4fb9cafe100a4a9de6e0529015e584d94ac8dc" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 10 12:12:36 2011 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 10 12:12:36 2011 -0500" }, "message": "ext4: replace i_delalloc_reserved_flag with EXT4_STATE_DELALLOC_RESERVED\n\nRemove the short element i_delalloc_reserved_flag from the\next4_inode_info structure and replace it a new bit in i_state_flags.\nSince we have an ext4_inode_info for every ext4 inode cached in the\ninode cache, any savings we can produce here is a very good thing from\na memory utilization perspective.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "f7c21177af0b32a2cd9ee36189637f0c1f0e1e17", "tree": "ba83d4ddcd4b7e15ff575f0b75013ba9ed62f249", "parents": [ "f9a62d090cf47fae2fe6f6bd8eb9f24482573fd8" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 10 12:10:55 2011 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 10 12:10:55 2011 -0500" }, "message": "ext4: Use ext4_error_file() to print the pathname to the corrupted inode\n\nWhere the file pointer is available, use ext4_error_file() instead of\next4_error_inode().\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "4b7bd364700d9ac8372eff48832062b936d0793b", "tree": "0dbf78c95456a0b02d07fcd473281f04a87e266d", "parents": [ "c0d8768af260e2cbb4bf659ae6094a262c86b085", "90a8a73c06cc32b609a880d48449d7083327e11a" ], "author": { "name": "Jiri Kosina", "email": "jkosina@suse.cz", "time": "Wed Dec 22 18:57:02 2010 +0100" }, "committer": { "name": "Jiri Kosina", "email": "jkosina@suse.cz", "time": "Wed Dec 22 18:57:02 2010 +0100" }, "message": "Merge branch \u0027master\u0027 into for-next\n\nConflicts:\n\tMAINTAINERS\n\tarch/arm/mach-omap2/pm24xx.c\n\tdrivers/scsi/bfa/bfa_fcpim.c\n\nNeeded to update to apply fixes for which the old branch was too\noutdated.\n" }, { "commit": "af0b44a1970fed1cda31d2969c99c46ffc515160", "tree": "b382d80df604c0bbd61836c13ae0b6f3020728e5", "parents": [ "cad3f00763dcf9dfc62cbddf4bd714ab5a71a0eb" ], "author": { "name": "Eric Sandeen", "email": "sandeen@redhat.com", "time": "Sun Dec 19 22:10:31 2010 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sun Dec 19 22:10:31 2010 -0500" }, "message": "ext4: zero out nanosecond timestamps for small inodes\n\nWhen nanosecond timestamp resolution isn\u0027t supported on an ext4\npartition (inode size \u003d 128), stat() appears to be returning\nuninitialized garbage in the nanosecond component of timestamps.\n\nEXT4_INODE_GET_XTIME should zero out tv_nsec when EXT4_FITS_IN_INODE\nevaluates to false.\n\nReported-by: Jordan Russell \u003cjr-list-2010@quo.to\u003e\nSigned-off-by: Eric Sandeen \u003csandeen@redhat.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "cad3f00763dcf9dfc62cbddf4bd714ab5a71a0eb", "tree": "02ec7c4959f5506f0b2fe128b1318e257ee6f0e4", "parents": [ "b17b35ec13adfeb0346d4b329110b14adc509327" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sun Dec 19 22:07:02 2010 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sun Dec 19 22:07:02 2010 -0500" }, "message": "ext4: optimize ext4_check_dir_entry() with unlikely() annotations\n\nThis function gets called a lot for large directories, and the answer\nis almost always \"no, no, there\u0027s no problem\". This means using\nunlikely() is a good thing.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "a2595b8aa67011419dae26b47e474f46df902989", "tree": "d44d79256f92f32b7958a04e89907f7e1a755767", "parents": [ "673c610033a8202c037ecd068c7a235495acda17" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Dec 15 20:30:48 2010 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Dec 15 20:30:48 2010 -0500" }, "message": "ext4: Add second mount options field since the s_mount_opt is full up\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "673c610033a8202c037ecd068c7a235495acda17", "tree": "e47ca541bf33f1d43d4ced9b72d6100853896236", "parents": [ "fd8c37eccdda21153298997417144b38b1623196" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Dec 15 20:28:48 2010 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Dec 15 20:28:48 2010 -0500" }, "message": "ext4: Move struct ext4_mount_options from ext4.h to super.c\n\nMove the ext4_mount_options structure definition from ext4.h, since it\nis only used in super.c.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "fd8c37eccdda21153298997417144b38b1623196", "tree": "313e022d9d82f890e728dce66ce6e115ea3970b1", "parents": [ "b0c3844d8af6b9f3f18f31e1b0502fbefa2166be" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Dec 15 20:26:48 2010 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Dec 15 20:26:48 2010 -0500" }, "message": "ext4: Simplify the usage of clear_opt() and set_opt() macros\n\nChange clear_opt() and set_opt() to take a superblock pointer instead\nof a pointer to EXT4_SB(sb)-\u003es_mount_opt. This makes it easier for us\nto support a second mount option field.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "1449032be17abb69116dbc393f67ceb8bd034f92", "tree": "f62757457241c2fdc14105afc12cb2718f7a2e68", "parents": [ "e8a7e48bb248a1196484d3f8afa53bded2b24e71" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Dec 14 15:27:50 2010 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Dec 14 15:27:50 2010 -0500" }, "message": "ext4: Turn off multiple page-io submission by default\n\nJon Nelson has found a test case which causes postgresql to fail with\nthe error:\n\npsql:t.sql:4: ERROR: invalid page header in block 38269 of relation base/16384/16581\n\nUnder memory pressure, it looks like part of a file can end up getting\nreplaced by zero\u0027s. Until we can figure out the cause, we\u0027ll roll\nback the change and use block_write_full_page() instead of\next4_bio_write_page(). The new, more efficient writing function can\nbe used via the mount option mblk_io_submit, so we can test and fix\nthe new page I/O code.\n\nTo reproduce the problem, install postgres 8.4 or 9.0, and pin enough\nmemory such that the system just at the end of triggering writeback\nbefore running the following sql script:\n\nbegin;\ncreate temporary table foo as select x as a, ARRAY[x] as b FROM\ngenerate_series(1, 10000000 ) AS x;\ncreate index foo_a_idx on foo (a);\ncreate index foo_b_idx on foo USING GIN (b);\nrollback;\n\nIf the temporary table is created on a hard drive partition which is\nencrypted using dm_crypt, then under memory pressure, approximately\n30-40% of the time, pgsql will issue the above failure.\n\nThis patch should fix this problem, and the problem will come back if\nthe file system is mounted with the mblk_io_submit mount option.\n\nReported-by: Jon Nelson \u003cjnelson@jamponi.net\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "83668e7141c7a0aa4035bde94344b81f9cf966ab", "tree": "34d9fd52470b475d6e9d88ece8ca1ba80bf85a42", "parents": [ "f7ad6d2e9201a6e1c9ee6530a291452eb695feb8" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Nov 08 13:45:33 2010 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Nov 08 13:45:33 2010 -0500" }, "message": "ext4: fix potential race when freeing ext4_io_page structures\n\nUse an atomic_t and make sure we don\u0027t free the structure while we\nmight still be submitting I/O for that page.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "f7ad6d2e9201a6e1c9ee6530a291452eb695feb8", "tree": "006cdcfd487404fb61986e3030d96cb33866755d", "parents": [ "ce7e010aef63dc6b37a2354f7c9f5f4aedb37978" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Nov 08 13:43:33 2010 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Nov 08 13:43:33 2010 -0500" }, "message": "ext4: handle writeback of inodes which are being freed\n\nThe following BUG can occur when an inode which is getting freed when\nit still has dirty pages outstanding, and it gets deleted (in this\nbecause it was the target of a rename). In ordered mode, we need to\nmake sure the data pages are written just in case we crash before the\nrename (or unlink) is committed. If the inode is being freed then\nwhen we try to igrab the inode, we end up tripping the BUG_ON at\nfs/ext4/page-io.c:146.\n\nTo solve this problem, we need to keep track of the number of io\ncallbacks which are pending, and avoid destroying the inode until they\nhave all been completed. That way we don\u0027t have to bump the inode\ncount to keep the inode from being destroyed; an approach which\ndoesn\u0027t work because the count could have already been dropped down to\nzero before the inode writeback has started (at which point we\u0027re not\nallowed to bump the count back up to 1, since it\u0027s already started\ngetting freed).\n\nThanks to Dave Chinner for suggesting this approach, which is also\nused by XFS.\n\n kernel BUG at /scratch_space/linux-2.6/fs/ext4/page-io.c:146!\n Call Trace:\n [\u003cffffffff811075b1\u003e] ext4_bio_write_page+0x172/0x307\n [\u003cffffffff811033a7\u003e] mpage_da_submit_io+0x2f9/0x37b\n [\u003cffffffff811068d7\u003e] mpage_da_map_and_submit+0x2cc/0x2e2\n [\u003cffffffff811069b3\u003e] mpage_add_bh_to_extent+0xc6/0xd5\n [\u003cffffffff81106c66\u003e] write_cache_pages_da+0x2a4/0x3ac\n [\u003cffffffff81107044\u003e] ext4_da_writepages+0x2d6/0x44d\n [\u003cffffffff81087910\u003e] do_writepages+0x1c/0x25\n [\u003cffffffff810810a4\u003e] __filemap_fdatawrite_range+0x4b/0x4d\n [\u003cffffffff810815f5\u003e] filemap_fdatawrite_range+0xe/0x10\n [\u003cffffffff81122a2e\u003e] jbd2_journal_begin_ordered_truncate+0x7b/0xa2\n [\u003cffffffff8110615d\u003e] ext4_evict_inode+0x57/0x24c\n [\u003cffffffff810c14a3\u003e] evict+0x22/0x92\n [\u003cffffffff810c1a3d\u003e] iput+0x212/0x249\n [\u003cffffffff810bdf16\u003e] dentry_iput+0xa1/0xb9\n [\u003cffffffff810bdf6b\u003e] d_kill+0x3d/0x5d\n [\u003cffffffff810be613\u003e] dput+0x13a/0x147\n [\u003cffffffff810b990d\u003e] sys_renameat+0x1b5/0x258\n [\u003cffffffff81145f71\u003e] ? _atomic_dec_and_lock+0x2d/0x4c\n [\u003cffffffff810b2950\u003e] ? cp_new_stat+0xde/0xea\n [\u003cffffffff810b29c1\u003e] ? sys_newlstat+0x2d/0x38\n [\u003cffffffff810b99c6\u003e] sys_rename+0x16/0x18\n [\u003cffffffff81002a2b\u003e] system_call_fastpath+0x16/0x1b\n\nReported-by: Nick Bowler \u003cnbowler@elliptictech.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nTested-by: Nick Bowler \u003cnbowler@elliptictech.com\u003e\n" }, { "commit": "b595076a180a56d1bb170e6eceda6eb9d76f4cd3", "tree": "bc01ec7283808013e0b8ce7713fd6fc40f810429", "parents": [ "6aaccece1c483f189f76f1282b3984ff4c7ecb0a" ], "author": { "name": "Uwe Kleine-König", "email": "u.kleine-koenig@pengutronix.de", "time": "Mon Nov 01 15:38:34 2010 -0400" }, "committer": { "name": "Jiri Kosina", "email": "jkosina@suse.cz", "time": "Mon Nov 01 15:38:34 2010 -0400" }, "message": "tree-wide: fix comment/printk typos\n\n\"gadget\", \"through\", \"command\", \"maintain\", \"maintain\", \"controller\", \"address\",\n\"between\", \"initiali[zs]e\", \"instead\", \"function\", \"select\", \"already\",\n\"equal\", \"access\", \"management\", \"hierarchy\", \"registration\", \"interest\",\n\"relative\", \"memory\", \"offset\", \"already\",\n\nSigned-off-by: Uwe Kleine-König \u003cu.kleine-koenig@pengutronix.de\u003e\nSigned-off-by: Jiri Kosina \u003cjkosina@suse.cz\u003e\n" }, { "commit": "eee4adc709afe40d8c02fa154c63dbeb55d911e3", "tree": "e65d8235eb7cf745a1d9dc2ac9ab1c62bdd45758", "parents": [ "61d08673de1fe68bfba86203258377bf39f234b6" ], "author": { "name": "Eric Sandeen", "email": "sandeen@redhat.com", "time": "Wed Oct 27 21:30:15 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Oct 27 21:30:15 2010 -0400" }, "message": "ext4: move ext4_mb_{get,put}_buddy_cache_lock and make them static\n\nThese functions are only used within fs/ext4/mballoc.c, so move them\nso they are used after they are defined, and then make them be static.\n\nSigned-off-by: Eric Sandeen \u003csandeen@redhat.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "61d08673de1fe68bfba86203258377bf39f234b6", "tree": "5cb32998c69eca626df54b50cb01e50a83c4db81", "parents": [ "4a873a472b3bbcfd425d7ae210afdec28c04e2e5" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Oct 27 21:30:15 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Oct 27 21:30:15 2010 -0400" }, "message": "ext4: rename mark_bitmap_end() to ext4_mark_bitmap_end()\n\nFix a namespace leak from fs/ext4\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n\n\n" }, { "commit": "4a873a472b3bbcfd425d7ae210afdec28c04e2e5", "tree": "88aa333bfafcc5303b7a3074865f51f67ad836b9", "parents": [ "bf89d16f6ef5389f1b9d8046e838ec87b9b3f8b9" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Oct 27 21:30:14 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Oct 27 21:30:14 2010 -0400" }, "message": "ext4: move flush_completed_IO to fs/ext4/fsync.c and make it static\n\nFix a namespace leak by moving the function to the file where it is\nused and making it static.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "1f109d5a17b438c4a54cbf6fd87a249e3d72fb21", "tree": "f58c6fd431975bf900b502b80122e175065da657", "parents": [ "5dabfc78dcedbe46cb2e4872dde448de3cec2979" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Oct 27 21:30:14 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Oct 27 21:30:14 2010 -0400" }, "message": "ext4: make various ext4 functions be static\n\nThese functions have no need to be exported beyond file context.\n\nNo functions needed to be moved for this commit; just some function\ndeclarations changed to be static and removed from header files.\n\n(A similar patch was submitted by Eric Sandeen, but I wanted to handle\ncode movement in separate patches to make sure code changes didn\u0027t\naccidentally get dropped.)\n\nSigned-off-by: Eric Sandeen \u003csandeen@redhat.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "5dabfc78dcedbe46cb2e4872dde448de3cec2979", "tree": "804ef3e76289978ef6690c2b8f379a14a60b15f0", "parents": [ "7f93cff90fa9be6ed45f6189e136153d1d8631b0" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Oct 27 21:30:14 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Oct 27 21:30:14 2010 -0400" }, "message": "ext4: rename {exit,init}_ext4_*() to ext4_{exit,init}_*()\n\nThis is a cleanup to avoid namespace leaks out of fs/ext4\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "7360d1731e5dc78aec867e65e55f9fb58782b5fe", "tree": "2cc0d139ec129c19150ef481d6adb9b0fd947c89", "parents": [ "367a51a339020ba4d9edb0ce0f21d65bd50b00c9" ], "author": { "name": "Lukas Czerner", "email": "lczerner@redhat.com", "time": "Wed Oct 27 21:30:12 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Oct 27 21:30:12 2010 -0400" }, "message": "ext4: Add batched discard support for ext4\n\nWalk through allocation groups and trim all free extents. It can be\ninvoked through FITRIM ioctl on the file system. The main idea is to\nprovide a way to trim the whole file system if needed, since some SSD\u0027s\nmay suffer from performance loss after the whole device was filled (it\ndoes not mean that fs is full!).\n\nIt search for free extents in allocation groups specified by Byte range\nstart -\u003e start+len. When the free extent is within this range, blocks\nare marked as used and then trimmed. Afterwards these blocks are marked\nas free in per-group bitmap.\n\nSince fstrim is a long operation it is good to have an ability to\ninterrupt it by a signal. This was added by Dmitry Monakhov.\nThanks Dimitry.\n\nSigned-off-by: Lukas Czerner \u003clczerner@redhat.com\u003e\nSigned-off-by: Dmitry Monakhov \u003cdmonakhov@openvz.org\u003e\nReviewed-by: Jan Kara \u003cjack@suse.cz\u003e\nReviewed-by: Dmitry Monakhov \u003cdmonakhov@openvz.org\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "bd2d0210cf22f2bd0cef72eb97cf94fc7d31d8cc", "tree": "f0d1902b7ff4294114614cc706855c3d6b131f73", "parents": [ "1de3e3df917459422cb2aecac440febc8879d410" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Oct 27 21:30:10 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Oct 27 21:30:10 2010 -0400" }, "message": "ext4: use bio layer instead of buffer layer in mpage_da_submit_io\n\nCall the block I/O layer directly instad of going through the buffer\nlayer. This should give us much better performance and scalability,\nas well as lowering our CPU utilization when doing buffered writeback.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n\n" }, { "commit": "640e9396566a1e1f52f2db294755a23f1e62cc97", "tree": "013b0028ceff606beb1290cc9f42704f2a94ab3d", "parents": [ "c999af2b347a55174f702702e0df814d05ef5491" ], "author": { "name": "Eric Sandeen", "email": "sandeen@redhat.com", "time": "Wed Oct 27 21:30:08 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Oct 27 21:30:08 2010 -0400" }, "message": "ext4: remove unused ext4_sb_info members\n\nNot that these take up a lot of room, but the structure is long enough\nas it is, and there\u0027s no need to confuse people with these various\nundocumented \u0026 unused structure members...\n\nSigned-off-by: Eric Sandeen \u003csandeen@redaht.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "e0d10bfa91b0a089a9e2c378b5c42f4e96171d95", "tree": "254d6b0b7d7ca2dfd817171d8d641c1a648e9c46", "parents": [ "c41303ced67c4ebf51bf2e7d0f139155e09e0939" ], "author": { "name": "Toshiyuki Okajima", "email": "toshi.okajima@jp.fujitsu.com", "time": "Wed Oct 27 21:30:06 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Oct 27 21:30:06 2010 -0400" }, "message": "ext4: improve llseek error handling for overly large seek offsets\n\nThe llseek system call should return EINVAL if passed a seek offset\nwhich results in a write error. What this maximum offset should be\ndepends on whether or not the huge_file file system feature is set,\nand whether or not the file is extent based or not.\n\n\nIf the file has no \"EXT4_EXTENTS_FL\" flag, the maximum size which can be \nwritten (write systemcall) is different from the maximum size which can be \nsought (lseek systemcall).\n\nFor example, the following 2 cases demonstrates the differences\nbetween the maximum size which can be written, versus the seek offset\nallowed by the llseek system call:\n\n#1: mkfs.ext3 \u003cdev\u003e; mount -t ext4 \u003cdev\u003e\n#2: mkfs.ext3 \u003cdev\u003e; tune2fs -Oextent,huge_file \u003cdev\u003e; mount -t ext4 \u003cdev\u003e\n\nTable. the max file size which we can write or seek\n at each filesystem feature tuning and file flag setting\n+\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d+\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d+\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d+\n| \\ File flag| | |\n| \\ | !EXT4_EXTENTS_FL | EXT4_EXTETNS_FL |\n|case \\| | |\n+------------+-------------------------------+-------------------------------+\n| #1 | write: 2194719883264 | write: -------------- |\n| | seek: 2199023251456 | seek: -------------- |\n+------------+-------------------------------+-------------------------------+\n| #2 | write: 4402345721856 | write: 17592186044415 |\n| | seek: 17592186044415 | seek: 17592186044415 |\n+------------+-------------------------------+-------------------------------+\n\nThe differences exist because ext4 has 2 maxbytes which are sb-\u003es_maxbytes\n(\u003d extent-mapped maxbytes) and EXT4_SB(sb)-\u003es_bitmap_maxbytes (\u003d block-mapped \nmaxbytes). Although generic_file_llseek uses only extent-mapped maxbytes.\n(llseek of ext4_file_operations is generic_file_llseek which uses\nsb-\u003es_maxbytes.)\n\nTherefore we create ext4 llseek function which uses 2 maxbytes.\n\nThe new own function originates from generic_file_llseek().\nIf the file flag, \"EXT4_EXTENTS_FL\" is not set, the function alters \ninode-\u003ei_sb-\u003es_maxbytes into EXT4_SB(inode-\u003ei_sb)-\u003es_bitmap_maxbytes.\n\nSigned-off-by: Toshiyuki Okajima \u003ctoshi.okajima@jp.fujitsu.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nCc: Andreas Dilger \u003cadilger.kernel@dilger.ca\u003e\n" }, { "commit": "857ac889cce8a486d47874db4d2f9620e7e9e5de", "tree": "12401895197d819fcbf2335244d91259f4640aa2", "parents": [ "bfff68738f1cb5c93dab1114634cea02aae9e7ba" ], "author": { "name": "Lukas Czerner", "email": "lczerner@redhat.com", "time": "Wed Oct 27 21:30:05 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Oct 27 21:30:05 2010 -0400" }, "message": "ext4: add interface to advertise ext4 features in sysfs\n\nUser-space should have the opportunity to check what features doest ext4\nsupport in each particular copy. This adds easy interface by creating new\n\"features\" directory in sys/fs/ext4/. In that directory files\nadvertising feature names can be created.\n\nAdd lazy_itable_init to the feature list.\n\nSigned-off-by: Lukas Czerner \u003clczerner@redhat.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "bfff68738f1cb5c93dab1114634cea02aae9e7ba", "tree": "b6cdf3f26e86464c7088cab62d837eb32f559fb9", "parents": [ "e6fa0be699449d28a20e815bfe9ce26725ec4962" ], "author": { "name": "Lukas Czerner", "email": "lczerner@redhat.com", "time": "Wed Oct 27 21:30:05 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Oct 27 21:30:05 2010 -0400" }, "message": "ext4: add support for lazy inode table initialization\n\nWhen the lazy_itable_init extended option is passed to mke2fs, it\nconsiderably speeds up filesystem creation because inode tables are\nnot zeroed out. The fact that parts of the inode table are\nuninitialized is not a problem so long as the block group descriptors,\nwhich contain information regarding how much of the inode table has\nbeen initialized, has not been corrupted However, if the block group\nchecksums are not valid, e2fsck must scan the entire inode table, and\nthe the old, uninitialized data could potentially cause e2fsck to\nreport false problems.\n\nHence, it is important for the inode tables to be initialized as soon\nas possble. This commit adds this feature so that mke2fs can safely\nuse the lazy inode table initialization feature to speed up formatting\nfile systems.\n\nThis is done via a new new kernel thread called ext4lazyinit, which is\ncreated on demand and destroyed, when it is no longer needed. There\nis only one thread for all ext4 filesystems in the system. When the\nfirst filesystem with inititable mount option is mounted, ext4lazyinit\nthread is created, then the filesystem can register its request in the\nrequest list.\n\nThis thread then walks through the list of requests picking up\nscheduled requests and invoking ext4_init_inode_table(). Next schedule\ntime for the request is computed by multiplying the time it took to\nzero out last inode table with wait multiplier, which can be set with\nthe (init_itable\u003dn) mount option (default is 10). We are doing\nthis so we do not take the whole I/O bandwidth. When the thread is no\nlonger necessary (request list is empty) it frees the appropriate\nstructures and exits (and can be created later later by another\nfilesystem).\n\nWe do not disturb regular inode allocations in any way, it just do not\ncare whether the inode table is, or is not zeroed. But when zeroing, we\nhave to skip used inodes, obviously. Also we should prevent new inode\nallocations from the group, while zeroing is on the way. For that we\ntake write alloc_sem lock in ext4_init_inode_table() and read alloc_sem\nin the ext4_claim_inode, so when we are unlucky and allocator hits the\ngroup which is currently being zeroed, it just has to wait.\n\nThis can be suppresed using the mount option no_init_itable.\n\nSigned-off-by: Lukas Czerner \u003clczerner@redhat.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "fb1813f4a8a27bbd4735967e46931e61fc837a3e", "tree": "c9d7c9d851c81663a8e501ba5c14f2a4b332f893", "parents": [ "b853fd364810a241050778124842a8c415c72a69" ], "author": { "name": "Curt Wohlgemuth", "email": "curtw@google.com", "time": "Wed Oct 27 21:29:12 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Oct 27 21:29:12 2010 -0400" }, "message": "ext4: use dedicated slab caches for group_info structures\n\next4_group_info structures are currently allocated with kmalloc().\nWith a typical 4K block size, these are 136 bytes each -- meaning\nthey\u0027ll each consume a 256-byte slab object. On a system with many\next4 large partitions, that\u0027s a lot of wasted kernel slab space.\n(E.g., a single 1TB partition will have about 8000 block groups, using\nabout 2MB of slab, of which nearly 1MB is wasted.)\n\nThis patch creates an array of slab pointers created as needed --\ndepending on the superblock block size -- and uses these slabs to\nallocate the group info objects.\n\nGoogle-Bug-Id: 2980809\n\nSigned-off-by: Curt Wohlgemuth \u003ccurtw@google.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "5f248c9c251c60af3403902b26e08de43964ea0b", "tree": "6d3328e72a7e4015a64017eb30be18095c6a3c64", "parents": [ "f6cec0ae58c17522a7bc4e2f39dae19f199ab534", "dca332528bc69e05f67161e1ed59929633d5e63d" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Aug 10 11:26:52 2010 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Aug 10 11:26:52 2010 -0700" }, "message": "Merge branch \u0027for-linus\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6\n\n* \u0027for-linus\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6: (96 commits)\n no need for list_for_each_entry_safe()/resetting with superblock list\n Fix sget() race with failing mount\n vfs: don\u0027t hold s_umount over close_bdev_exclusive() call\n sysv: do not mark superblock dirty on remount\n sysv: do not mark superblock dirty on mount\n btrfs: remove junk sb_dirt change\n BFS: clean up the superblock usage\n AFFS: wait for sb synchronization when needed\n AFFS: clean up dirty flag usage\n cifs: truncate fallout\n mbcache: fix shrinker function return value\n mbcache: Remove unused features\n add f_flags to struct statfs(64)\n pass a struct path to vfs_statfs\n update VFS documentation for method changes.\n All filesystems that need invalidate_inode_buffers() are doing that explicitly\n convert remaining -\u003eclear_inode() to -\u003eevict_inode()\n Make -\u003edrop_inode() just return whether inode needs to be dropped\n fs/inode.c:clear_inode() is gone\n fs/inode.c:evict() doesn\u0027t care about delete vs. non-delete paths now\n ...\n\nFix up trivial conflicts in fs/nilfs2/super.c\n" }, { "commit": "0930fcc1ee2f0a810b938bc283a3a262d7adccbb", "tree": "5e5d10894f1e31a7aede75110b43d7a41347631d", "parents": [ "7da08fd17a6e42d80f0f3897a5cbd682e77bcdb4" ], "author": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Mon Jun 07 13:16:22 2010 -0400" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Mon Aug 09 16:48:30 2010 -0400" }, "message": "convert ext4 to -\u003eevict_inode()\n\npretty much brute-force...\n\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "0cfc9255a1efb0467de2162950197750570ecec0", "tree": "3bb2510d8b6d373d7db3a49bcda3cbbebd10330e", "parents": [ "8dd420466c7bfc459fa04680bd5690bfc41a4553" ], "author": { "name": "Eric Sandeen", "email": "sandeen@redhat.com", "time": "Thu Aug 05 01:46:37 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Thu Aug 05 01:46:37 2010 -0400" }, "message": "ext4: re-inline ext4_rec_len_(to|from)_disk functions\n\ncommit 3d0518f4, \"ext4: New rec_len encoding for very\nlarge blocksizes\" made several changes to this path, but from\na perf perspective, un-inlining ext4_rec_len_from_disk() seems\nmost significant. This function is called from ext4_check_dir_entry(),\nwhich on a file-creation workload is called extremely often.\n\nI tested this with bonnie:\n\n# bonnie++ -u root -s 0 -f -x 200 -d /mnt/test -n 32\n\n(this does 200 iterations) and got this for the file creations:\n\next4 stock: Average \u003d 21206.8 files/s\next4 inlined: Average \u003d 22346.7 files/s (+5%)\n\nSigned-off-by: Eric Sandeen \u003csandeen@redhat.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "8b67f04ab9de5d8f3a71aef72bf02c995a506db5", "tree": "dd05968730762f5b18de4c6b0720843669e4e9db", "parents": [ "ca0e05e4b15193aeba72b995e90de990db7f8304" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sun Aug 01 23:14:20 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sun Aug 01 23:14:20 2010 -0400" }, "message": "ext4: Add mount options in superblock\n\nAllow mount options to be stored in the superblock. Also add default\nmount option bits for nobarrier, block_validity, discard, and nodelalloc.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "79e8303677fc15f508b9877e0fea1925c4add6f3", "tree": "85891ab05b2a9e5dd47966fd16bc372df6d4bb88", "parents": [ "62d2b5f2dcd3707b070efb16bbfdf6947c38c194" ], "author": { "name": "Eric Sandeen", "email": "sandeen@redhat.com", "time": "Tue Jul 27 11:56:07 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jul 27 11:56:07 2010 -0400" }, "message": "ext4: fix ext4_get_blocks references\n\next4_get_blocks got renamed to ext4_map_blocks, but left stale\ncomments and a prototype littered around.\n\nSigned-off-by: Eric Sandeen \u003csandeen@redhat.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "5b3ff237bef43b9e7fb7d1eb858e29b73fd664f9", "tree": "e3810d974a0e51a8c4b9046abdd36a5a4022abb3", "parents": [ "552ef8024f909d9b3a7442d0ab0d48a22de24e9e" ], "author": { "name": "jiayingz@google.com (Jiaying Zhang)", "email": "", "time": "Tue Jul 27 11:56:06 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jul 27 11:56:06 2010 -0400" }, "message": "ext4: move aio completion after unwritten extent conversion\n\nThis patch is to be applied upon Christoph\u0027s \"direct-io: move aio_complete\ninto -\u003eend_io\" patch. It adds iocb and result fields to struct ext4_io_end_t,\nso that we can call aio_complete from ext4_end_io_nolock() after the extent\nconversion has finished.\n\nI have verified with Christoph\u0027s aio-dio test that used to fail after a few\nruns on an original kernel but now succeeds on the patched kernel.\n\nSee http://thread.gmane.org/gmane.comp.file-systems.ext4/19659 for details.\n\nSigned-off-by: Jiaying Zhang \u003cjiayingz@google.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "89eeddf03327e19cfcbb18efa98e5470e2f5c563", "tree": "2ca9f7ed13b348677a2d4b2fe8bf40e041a72f5f", "parents": [ "66e61a9e9504f61b9a928c9055368c81da613a50" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jul 27 11:56:04 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jul 27 11:56:04 2010 -0400" }, "message": "ext4: Define s_jnl_backup_type in superblock\n\nThis has been in use by e2fsprogs for a while; define it to keep the\nsuper block fields in sync.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "66e61a9e9504f61b9a928c9055368c81da613a50", "tree": "afcd8147b4e4771103f75f5a03b836950882dece", "parents": [ "1c13d5c0872870cca3e612aa045d492ead9ab004" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jul 27 11:56:04 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jul 27 11:56:04 2010 -0400" }, "message": "ext4: Once a day, printk file system error information to dmesg\n\nThis allows us to grab any file system error messages by scraping\n/var/log/messages. This will make it easy for us to do error analysis\nacross the very large number of machines as we deploy ext4 across the\nfleet.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "1c13d5c0872870cca3e612aa045d492ead9ab004", "tree": "6e3dd0d3f49ff56dda9fc6cd72c233759bc24e09", "parents": [ "c398eda0e43a791be0fca6f197a1e2bbb9f16070" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jul 27 11:56:03 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jul 27 11:56:03 2010 -0400" }, "message": "ext4: Save error information to the superblock for analysis\n\nSave number of file system errors, and the time function name, line\nnumber, block number, and inode number of the first and most recent\nerrors reported on the file system in the superblock.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "c398eda0e43a791be0fca6f197a1e2bbb9f16070", "tree": "d7b2b95490f96a75e116a3aa13c17767aa630342", "parents": [ "60fd4da34d55a9cc0d857fc76dc12cf8cab4ed02" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jul 27 11:56:40 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jul 27 11:56:40 2010 -0400" }, "message": "ext4: Pass line numbers to ext4_error() and friends\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "60fd4da34d55a9cc0d857fc76dc12cf8cab4ed02", "tree": "72c6b3d9c7680070a751da56bd9068f71e7b106f", "parents": [ "90c7201b97bb7ac5a4e2605abc0efb5fdfb957f0" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jul 27 11:54:40 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jul 27 11:54:40 2010 -0400" }, "message": "ext4: Cleanup ext4_check_dir_entry so __func__ is now implicit\n \nAlso start passing the line number to ext4_check_dir since we\u0027re going\nto need it in upcoming patch.\n \nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "e29136f80e775b0310273932b4297a62f5574a29", "tree": "d10d56b15b7968744ea0becdf61440aae7e609c5", "parents": [ "c67d859e39896e4286249da89c4ca0ef8bd949cb" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jun 29 12:54:28 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jun 29 12:54:28 2010 -0400" }, "message": "ext4: Enhance ext4_grp_locked_error() to take block and function numbers\n\nAlso use a macro definition so that __func__ and __LINE__ is implicit.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "c67d859e39896e4286249da89c4ca0ef8bd949cb", "tree": "e483a8e61fe876506d8ed819fbfe29eac6c493a7", "parents": [ "4a9cdec73f79b2858e9ecf0b6cfac7f6b200bf3a" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jun 29 11:07:07 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jun 29 11:07:07 2010 -0400" }, "message": "ext4: clean up ext4_abort() so __func__ is now implicit\n\nUse a macro definition for ext4_abort() to clean up the .c files a wee\nbit.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "4a9cdec73f79b2858e9ecf0b6cfac7f6b200bf3a", "tree": "0e06b201e009e5e2a661811e61ef3184138bb8d3", "parents": [ "c6ac12a6159c802ae8b757dd13563564e64333df" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jun 29 11:00:23 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jun 29 11:00:23 2010 -0400" }, "message": "ext4: Add new superblock fields reserved for the Next3 snapshot feature\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "206f7ab4f49a2021fcb8687f25395be77711ddee", "tree": "19764d36a25ec1e088d32572a1c0936eeaf19636", "parents": [ "5a0790c2c4a18435759a70e1562450035d778339" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Mon Jun 14 14:42:49 2010 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jun 14 14:42:49 2010 -0400" }, "message": "ext4: remove vestiges of nobh support\n\nThe nobh option was only supported for writeback mode, but given that all\nwrite paths actually create buffer heads it effectively was a no-op already.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" } ], "next": "a0375156ca1041574b5d47cc7e32f10b891151b0" }