)]}' { "log": [ { "commit": "d4da6c9ccf648f3f1cb5bf9d981a62c253d30e28", "tree": "709f8bdc50a3a1d47632047eb3670b4a4a6ff045", "parents": [ "c35102c3e15f90fe604523a2fbffd9dc158b455a" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Nov 02 10:15:27 2009 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Nov 02 10:15:27 2009 -0800" }, "message": "Revert \"ext4: Remove journal_checksum mount option and enable it by default\"\n\nThis reverts commit d0646f7b636d067d715fab52a2ba9c6f0f46b0d7, as\nrequested by Eric Sandeen.\n\nIt can basically cause an ext4 filesystem to miss recovery (and thus get\nmounted with errors) if the journal checksum does not match.\n\nQuoth Eric:\n\n \"My hand-wavy hunch about what is happening is that we\u0027re finding a\n bad checksum on the last partially-written transaction, which is\n not surprising, but if we have a wrapped log and we\u0027re doing the\n initial scan for head/tail, and we abort scanning on that bad\n checksum, then we are essentially running an unrecovered filesystem.\n\n But that\u0027s hand-wavy and I need to go look at the code.\n\n We lived without journal checksums on by default until now, and at\n this point they\u0027re doing more harm than good, so we should revert\n the default-changing commit until we can fix it and do some good\n power-fail testing with the fixes in place.\"\n\nSee\n\n\thttp://bugzilla.kernel.org/show_bug.cgi?id\u003d14354\n\nfor all the gory details.\n\nRequested-by: Eric Sandeen \u003csandeen@redhat.com\u003e\nCc: Theodore Tso \u003ctytso@mit.edu\u003e\nCc: Alexey Fisher \u003cbug-track@fisher-privat.net\u003e\nCc: Maxim Levitsky \u003cmaximlevitsky@gmail.com\u003e\nCc: Aneesh Kumar K.V \u003caneesh.kumar@linux.vnet.ibm.com\u003e\nCc: Mathias Burén \u003cmathias.buren@gmail.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "f0e2dfa7f3e1361ca8fc91c25e67fc4e92613cc9", "tree": "8fa5be2f535b00140b0c6330c92b20584e87cb9e", "parents": [ "1f94533d9cd75f6d2826018d54a971b9cc085992" ], "author": { "name": "Eric Sandeen", "email": "sandeen@redhat.com", "time": "Thu Oct 01 02:21:07 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Thu Oct 01 02:21:07 2009 -0400" }, "message": "ext4: drop ext4dev compat\n\nKconfig \u0026 super.c promised it\u0027d be gone by 2.6.31, so it\u0027s\nabout time to drop it.\n\nSigned-off-by: Eric Sandeen \u003csandeen@redhat.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "296c355cd6443d89fa251885a8d78778fe111dc4", "tree": "5cf7c8b115617dc3829a16a5969894d37b73173c", "parents": [ "90576c0b9a0b5323fc4bd7f23f49be0d234f36d1" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Sep 30 00:32:42 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Sep 30 00:32:42 2009 -0400" }, "message": "ext4: Use tracepoints for mb_history trace file\n\nThe /proc/fs/ext4/\u003cdev\u003e/mb_history was maintained manually, and had a\nnumber of problems: it required a largish amount of memory to be\nallocated for each ext4 filesystem, and the s_mb_history_lock\nintroduced a CPU contention problem. \n\nBy ripping out the mb_history code and replacing it with ftrace\ntracepoints, and we get more functionality: timestamps, event\nfiltering, the ability to correlate mballoc history with other ext4\ntracepoints, etc.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "90576c0b9a0b5323fc4bd7f23f49be0d234f36d1", "tree": "d4a1ab6f923f1c9c7c87f13a828db72c1f4412c1", "parents": [ "d3d1faf6a74496ea4435fd057c6a2cad49f3e523" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Sep 29 15:51:30 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Sep 29 15:51:30 2009 -0400" }, "message": "ext4, jbd2: Drop unneeded printks at mount and unmount time\n\nThere are a number of kernel printk\u0027s which are printed when an ext4\nfilesystem is mounted and unmounted. Disable them to economize space\nin the system logs. In addition, disabling the mballoc stats by\ndefault saves a number of unneeded atomic operations for every block\nallocation or deallocation.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n\n" }, { "commit": "d3d1faf6a74496ea4435fd057c6a2cad49f3e523", "tree": "9f1cc0e2efb9a4fe42bb6b57c087d8450a854dc1", "parents": [ "f3dc272fd5e2ae08244796bb39e7e1ce4b25d3b3" ], "author": { "name": "Curt Wohlgemuth", "email": "curtw@google.com", "time": "Tue Sep 29 11:01:03 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Sep 29 11:01:03 2009 -0400" }, "message": "ext4: Handle nested ext4_journal_start/stop calls without a journal\n\nThis patch fixes a problem with handling nested calls to\next4_journal_start/ext4_journal_stop, when there is no journal present.\n\nSigned-off-by: Curt Wohlgemuth \u003ccurtw@google.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "8d5d02e6b176565c77ff03604908b1453a22044d", "tree": "0d29e4f28233f24960c7921c1c0a7608077bf713", "parents": [ "4c0425ff68b1b87b802ffeda7b6a46ff7da7241c" ], "author": { "name": "Mingming Cao", "email": "cmm@us.ibm.com", "time": "Mon Sep 28 15:48:29 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Sep 28 15:48:29 2009 -0400" }, "message": "ext4: async direct IO for holes and fallocate support\n\nFor async direct IO that covers holes or fallocate, the end_io\ncallback function now queued the convertion work on workqueue but\ndon\u0027t flush the work rightaway as it might take too long to afford.\n\nBut when fsync is called after all the data is completed, user expects\nthe metadata also being updated before fsync returns.\n\nThus we need to flush the conversion work when fsync() is called.\nThis patch keep track of a listed of completed async direct io that\nhas a work queued on workqueue. When fsync() is called, it will go\nthrough the list and do the conversion.\n\nSigned-off-by: Mingming Cao \u003ccmm@us.ibm.com\u003e\n" }, { "commit": "4c0425ff68b1b87b802ffeda7b6a46ff7da7241c", "tree": "a8718f5f4574af8e15fd876b24f4aec88d62451b", "parents": [ "0031462b5b392f90d17f1d75abb795883c44e969" ], "author": { "name": "Mingming Cao", "email": "cmm@us.ibm.com", "time": "Mon Sep 28 15:48:41 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Sep 28 15:48:41 2009 -0400" }, "message": "ext4: Use end_io callback to avoid direct I/O fallback to buffered I/O\n\nCurrently the DIO VFS code passes create \u003d 0 when writing to the\nmiddle of file. It does this to avoid block allocation for holes, so\nas not to expose stale data out when there is a parallel buffered read\n(which does not hold the i_mutex lock). Direct I/O writes into holes\nfalls back to buffered IO for this reason.\n\nSince preallocated extents are treated as holes when doing a\nget_block() look up (buffer is not mapped), direct IO over fallocate\nalso falls back to buffered IO. Thus ext4 actually silently falls\nback to buffered IO in above two cases, which is undesirable.\n\nTo fix this, this patch creates unitialized extents when a direct I/O\nwrite into holes in sparse files, and registering an end_io callback which\nconverts the uninitialized extent to an initialized extent after the\nI/O is completed.\n\nSinged-Off-By: Mingming Cao \u003ccmm@us.ibm.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "55138e0bc29c0751e2152df9ad35deea542f29b3", "tree": "40dbc77de3e7a426030bd740ba8e2fd0d2171523", "parents": [ "71780577306fd1e76c7a92e3b308db624d03adb9" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Sep 29 13:31:31 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Sep 29 13:31:31 2009 -0400" }, "message": "ext4: Adjust ext4_da_writepages() to write out larger contiguous chunks\n\nWork around problems in the writeback code to force out writebacks in\nlarger chunks than just 4mb, which is just too small. This also works\naround limitations in the ext4 block allocator, which can\u0027t allocate\nmore than 2048 blocks at a time. So we need to defeat the round-robin\ncharacteristics of the writeback code and try to write out as many\nblocks in one inode before allowing the writeback code to move on to\nanother inode. We add a a new per-filesystem tunable,\nmax_writeback_mb_bump, which caps this to a default of 128mb per\ninode.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "0d54b217a247f39605361f867fefbb9e099a5432", "tree": "5af6a2cc4cbc6c327e735ac5edb642d47a1f0013", "parents": [ "61e225dc341107be304fd1088146c2a5e88ff9e0" ], "author": { "name": "Alexey Dobriyan", "email": "adobriyan@gmail.com", "time": "Mon Sep 21 17:01:09 2009 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Sep 22 07:17:24 2009 -0700" }, "message": "const: make struct super_block::s_qcop const\n\nSigned-off-by: Alexey Dobriyan \u003cadobriyan@gmail.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "61e225dc341107be304fd1088146c2a5e88ff9e0", "tree": "e6d3e1dc5506e232497f17721175a081a5306b5b", "parents": [ "00d3803b656a5f0935518d746f6bb27d5181d29d" ], "author": { "name": "Alexey Dobriyan", "email": "adobriyan@gmail.com", "time": "Mon Sep 21 17:01:08 2009 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Sep 22 07:17:24 2009 -0700" }, "message": "const: make struct super_block::dq_op const\n\nSigned-off-by: Alexey Dobriyan \u003cadobriyan@gmail.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "fb0a387dcdcd21aab1b09ee7fd80b7c979bdbbfd", "tree": "dcb12c5fce8f7ccb8b183936ea71a29aba3f3846", "parents": [ "c40ce3c9ea97425a12d7e44031a98fe50add6fc1" ], "author": { "name": "Eric Sandeen", "email": "sandeen@redhat.com", "time": "Wed Sep 16 14:45:10 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Sep 16 14:45:10 2009 -0400" }, "message": "ext4: limit block allocations for indirect-block files to \u003c 2^32\n\nToday, the ext4 allocator will happily allocate blocks past\n2^32 for indirect-block files, which results in the block\nnumbers getting truncated, and corruption ensues.\n\nThis patch limits such allocations to \u003c 2^32, and adds\nBUG_ONs if we do get blocks larger than that.\n\nThis should address RH Bug 519471, ext4 bitmap allocator \nmust limit blocks to \u003c 2^32\n\n* ext4_find_goal() is modified to choose a goal \u003c UINT_MAX,\n so that our starting point is in an acceptable range.\n\n* ext4_xattr_block_set() is modified such that the goal block\n is \u003c UINT_MAX, as above.\n\n* ext4_mb_regular_allocator() is modified so that the group\n search does not continue into groups which are too high\n\n* ext4_mb_use_preallocated() has a check that we don\u0027t use\n preallocated space which is too far out\n\n* ext4_alloc_blocks() and ext4_xattr_block_set() add some BUG_ONs\n\nNo attempt has been made to limit inode locations to \u003c 2^32,\nso we may wind up with blocks far from their inodes. Doing\nthis much already will lead to some odd ENOSPC issues when the\n\"lower 32\" gets full, and further restricting inodes could\nmake that even weirder.\n\nFor high inodes, choosing a goal of the original, % UINT_MAX,\nmay be a bit odd, but then we\u0027re in an odd situation anyway,\nand I don\u0027t know of a better heuristic.\n\nSigned-off-by: Eric Sandeen \u003csandeen@redhat.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "3661d28615ea580c1db02a972fd4d3898df1cb01", "tree": "35b5ee30b88913c3e0711f763f0fa4d3bca27807", "parents": [ "7ad9bb651fc2036ea94bed94da76a4b08959a911" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Sep 14 22:59:50 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Sep 14 22:59:50 2009 -0400" }, "message": "ext4: Fix include/trace/events/ext4.h to work with Systemtap\n\nUsing relative pathnames in #include statements interacts badly with\nSystemTap, since the fs/ext4/*.h header files are not packaged up as\npart of a distribution kernel\u0027s header files. Since systemtap doesn\u0027t\nuse TP_fast_assign(), we can use a blind structure definition and then\nmake sure the needed header files are defined before the ext4 source\nfiles #include the trace/events/ext4.h header file.\n\nhttps://bugzilla.redhat.com/show_bug.cgi?id\u003d512478\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "7ad9bb651fc2036ea94bed94da76a4b08959a911", "tree": "2669266f02c35b1b24d13d0adc4b3ac5afbdf7fd", "parents": [ "1f7bebb9e911d870fa8f997ddff838e82b5715ea" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 11 16:51:28 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Sep 11 16:51:28 2009 -0400" }, "message": "ext4: Fix initalization of s_flex_groups\n\nThe s_flex_groups array should have been initialized using atomic_add\nto sum up the free counts from the block groups that make up a\nflex_bg. By using atomic_set, the value of the s_flex_groups array\nwas set to the values of the last block group in the flex_bg. \n\nThe impact of this bug is that the block and inode allocation\nalgorithms might not pick the best flex_bg for new allocation.\n\nThanks to Damien Guibouret for pointing out this problem!\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "71290b368ad5e1e0b0b300c9d5638490a9fd1a2d", "tree": "a48503e3ddf3715613df2a3e29a7220cea3368b4", "parents": [ "08c3a8133810d955d97f7146c50c43e4073f2148" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Thu Sep 10 17:31:04 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Thu Sep 10 17:31:04 2009 -0400" }, "message": "ext4: Don\u0027t update superblock write time when filesystem is read-only\n\nThis avoids updating the superblock write time when we are mounting\nthe root file system read/only but we need to replay the journal; at\nthat point, for people who are east of GMT and who make their clock\ntick in localtime for Windows bug-for-bug compatibility, and this will\ncause e2fsck to complain and force a full file system check.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n\n" }, { "commit": "d0646f7b636d067d715fab52a2ba9c6f0f46b0d7", "tree": "f7b3ae9510e8c789651d99fee0c22867e6ccba94", "parents": [ "a3710fd1ee8cd542c5de63cf2c39f8912031f867" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Sep 05 12:50:43 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Sep 05 12:50:43 2009 -0400" }, "message": "ext4: Remove journal_checksum mount option and enable it by default\n\nThere\u0027s no real cost for the journal checksum feature, and we should\nmake sure it is enabled all the time.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n\n\n" }, { "commit": "a13fb1a4533f26c1e2b0204d5283b696689645af", "tree": "1f779dfe2057bef2a5985989f2a347ed32ca9179", "parents": [ "38877f4e8dbbec12c6fde85ee1fce1dc27ef3290" ], "author": { "name": "Eric Sandeen", "email": "sandeen@redhat.com", "time": "Tue Aug 18 00:20:23 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Aug 18 00:20:23 2009 -0400" }, "message": "ext4: Add feature set check helper for mount \u0026 remount paths\n\nA user reported that although his root ext4 filesystem was mounting\nfine, other filesystems would not mount, with the:\n\n\"Filesystem with huge files cannot be mounted RDWR without CONFIG_LBDAF\"\n\nerror on his 32-bit box built without CONFIG_LBDAF. This is because\nthe test at mount time for this situation was not being re-checked\non remount, and the normal boot process makes an ro-\u003erw transition,\nso this was being missed.\n\nRefactor to make a common helper function to test the filesystem\nfeatures against the type of mount request (RO vs. RW) so that we \nstay consistent.\n\nAddresses Red-Hat-Bugzilla: #517650\n\nSigned-off-by: Eric Sandeen \u003csandeen@redhat.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "bf43d84b185e2ff54598f8c58a5a8e63148b6e90", "tree": "1e7a7ca7e5d328c41ef6757ea33d709d8e47fcfb", "parents": [ "0ccff1a49def92d6b838a6da166c89004b3a4d0c" ], "author": { "name": "Eric Sandeen", "email": "sandeen@redhat.com", "time": "Mon Aug 17 23:48:51 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Aug 17 23:48:51 2009 -0400" }, "message": "ext4: reject too-large filesystems on 32-bit kernels\n\next4 will happily mount a \u003e 16T filesystem on a 32-bit box, but\nthis is not safe; writes to the block device will wrap past 16T\nand the page cache can\u0027t index past 16T (232 index * 4k pages).\n\nAdding another test to the existing \"too many sectors\" test\nshould do the trick.\n\nAdd a comment, a relevant return value, and fix the reference\nto the CONFIG_LBD(AF) option as well.\n\nSigned-off-by: Eric Sandeen \u003csandeen@redhat.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "78f1ddbb498283c2445c11b0dfa666424c301803", "tree": "aa25853e60d224812103ea5b5e520fc41d57cb05", "parents": [ "43b38520296d0c1730c78c878e1d6d1a49122091" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jul 27 23:09:47 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jul 27 23:09:47 2009 -0400" }, "message": "ext4: Avoid null pointer dereference when decoding EROFS w/o a journal\n\nWe need to check to make sure a journal is present before checking the\njournal flags in ext4_decode_error().\n\nSigned-off-by: Eric Sesterhenn \u003ceric.sesterhenn@lsexperts.de\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "d4bfe2f76d785cc77611a4bda8cedaff358d8c7d", "tree": "a8c953fe752afebadb4f0fb4aa3e80dbab934f7f", "parents": [ "6582a0e6f6bc7bf64817b9e1a424782855292ab0" ], "author": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Mon Jun 08 19:54:26 2009 -0400" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Wed Jun 24 08:17:04 2009 -0400" }, "message": "switch ext4 to inode-\u003ei_acl\n\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "31583d6acf940d2951bc8716557b06d9de5a0c4b", "tree": "607aef385b0998f0cb7ff63b05407afed5182840", "parents": [ "ee37ba7a4212c7420f12e6a2ad8a3966649ede7a", "f740f5ca056f0a4eff3abdf272a8a4ba3965d57d" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Jun 19 17:43:04 2009 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Jun 19 17:43:04 2009 -0700" }, "message": "Merge branch \u0027for-linus\u0027 of git://git.kernel.dk/linux-2.6-block\n\n* \u0027for-linus\u0027 of git://git.kernel.dk/linux-2.6-block:\n Fix kernel-doc parameter name typo in blk-settings.c:\n block: rename CONFIG_LBD to CONFIG_LBDAF\n block: Fix bounce_pfn setting\n hd: stop defining MAJOR_NR\n" }, { "commit": "90c699a9ee4be165966d40f1837909ccb8890a68", "tree": "ff136ce7b73c7d7bbf5eb4241d01cb3b930d3566", "parents": [ "3a02c8e8142f7f133d4c6e72bc3e1d830e6b8b9e" ], "author": { "name": "Bartlomiej Zolnierkiewicz", "email": "bzolnier@gmail.com", "time": "Fri Jun 19 08:08:50 2009 +0200" }, "committer": { "name": "Jens Axboe", "email": "jens.axboe@oracle.com", "time": "Fri Jun 19 08:08:50 2009 +0200" }, "message": "block: rename CONFIG_LBD to CONFIG_LBDAF\n\nFollow-up to \"block: enable by default support for large devices\nand files on 32-bit archs\".\n\nRename CONFIG_LBD to CONFIG_LBDAF to:\n- allow update of existing [def]configs for \"default y\" change\n- reflect that it is used also for large files support nowadays\n\nSigned-off-by: Bartlomiej Zolnierkiewicz \u003cbzolnier@gmail.com\u003e\nSigned-off-by: Jens Axboe \u003cjens.axboe@oracle.com\u003e\n" }, { "commit": "11013911daea4820147ae6d7094dd7c6894e8651", "tree": "f8e9f9d2058e0dfc826d4df3d88a7eb18a56b3f3", "parents": [ "f157a4aa98a18bd3817a72bea90d48494e2586e7" ], "author": { "name": "Andreas Dilger", "email": "adilger@sun.com", "time": "Sat Jun 13 11:45:35 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Jun 13 11:45:35 2009 -0400" }, "message": "ext4: teach the inode allocator to use a goal inode number\n\nEnhance the inode allocator to take a goal inode number as a\nparemeter; if it is specified, it takes precedence over Orlov or\nparent directory inode allocation algorithms.\n\nThe extents migration function uses the goal inode number so that the\nextent trees allocated the migration function use the correct flex_bg.\nIn the future, the goal inode functionality will also be used to\nallocate an adjacent inode for the extended attributes.\n\nAlso, for testing purposes the goal inode number can be specified via\n/sys/fs/{dev}/inode_goal. This can be useful for testing inode\nallocation beyond 2^32 blocks on very large filesystems.\n\nSigned-off-by: Andreas Dilger \u003cadilger@sun.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "4ab2f15b7f709c3626a7eed075a7225b4c775c7e", "tree": "bfefc592c4c2eb176162134c615132e75f810486", "parents": [ "bc0b0d6d69ee9022f18ae264e62beb30ddeb322a" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Jun 13 10:09:36 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Jun 13 10:09:36 2009 -0400" }, "message": "ext4: move the abort flag from s_mount_opts to s_mount_flags\n\nWe\u0027re running out of space in the mount options word, and\nEXT4_MOUNT_ABORT isn\u0027t really a mount option, but a run-time flag. So\nmove it to become EXT4_MF_FS_ABORTED in s_mount_flags.\n\nAlso remove bogus ext2_fs.h / ext4.h simultaneous #include protection,\nwhich can never happen.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "7f4520cc6242780ce720aa440ad4b391f998b558", "tree": "c8f1d99e019f2e29a967851031f4a60bf7ab1467", "parents": [ "748de6736c1e482e111f9d1b5a5d5b1787600cad" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Jun 13 10:09:41 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Jun 13 10:09:41 2009 -0400" }, "message": "ext4: change s_mount_opt to be an unsigned int\n\nWe can only fit 32 options in s_mount_opt because an unsigned long is\n32-bits on a x86 machine. So use an unsigned int to save space on\n64-bit platforms.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "337eb00a2c3a421999c39c94ce7e33545ee8baa7", "tree": "d9b780d095b638b1d8fa23841ff70347cf5daa08", "parents": [ "4195f73d1329e49727bcceb028e58cb38376c2b0" ], "author": { "name": "Alessio Igor Bogani", "email": "abogani@texware.it", "time": "Tue May 12 15:10:54 2009 +0200" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Thu Jun 11 21:36:11 2009 -0400" }, "message": "Push BKL down into -\u003eremount_fs()\n\n[xfs, btrfs, capifs, shmem don\u0027t need BKL, exempt]\n\nSigned-off-by: Alessio Igor Bogani \u003cabogani@texware.it\u003e\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "ebc1ac164560a241d9bf1b7519062910c3f90a01", "tree": "db17fd3043b15f8269cce2c2d00213814022fc30", "parents": [ "01ba687577647beef6c5f2ea59bfb56fac9fcde2" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Mon May 11 23:35:03 2009 +0200" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Thu Jun 11 21:36:09 2009 -0400" }, "message": "-\u003ewrite_super lock_super pushdown\n\nPush down lock_super into -\u003ewrite_super instances and remove it from the\ncaller.\n\nFollowing filesystem don\u0027t need -\u003es_lock in -\u003ewrite_super and are skipped:\n\n * bfs, nilfs2 - no other uses of s_lock and have internal locks in\n\t-\u003ewrite_super\n * ext2 - uses BKL in ext2_write_super and has internal calls without s_lock\n * reiserfs - no other uses of s_lock as has reiserfs_write_lock (BKL) in\n \t-\u003ewrite_super\n * xfs - no other uses of s_lock and uses internal lock (buffer lock on\n\tsuperblock buffer) to serialize -\u003ewrite_super. Also xfs_fs_write_super\n\tis superflous and will go away in the next merge window\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "bbd6851a3213a525128473e978b692ab6ac11aba", "tree": "8ebddebadd8992871ab98456187cb00849a82058", "parents": [ "6cfd0148425e528b859b26e436b01f23f6926224" ], "author": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Wed May 06 10:43:07 2009 -0400" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Thu Jun 11 21:36:08 2009 -0400" }, "message": "Push lock_super() into the -\u003eremount_fs() of filesystems that care about it\n\nNote that since we can\u0027t run into contention between remount_fs and write_super\n(due to exclusion on s_umount), we have to care only about filesystems that\ntouch lock_super() on their own. Out of those ext3, ext4, hpfs, sysv and ufs\ndo need it; fat doesn\u0027t since its -\u003eremount_fs() only accesses assign-once\ndata (basically, it\u0027s \"we have no atime on directories and only have atime on\nfiles for vfat; force nodiratime and possibly noatime into *flags\").\n\n[folded a build fix from hch]\n\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "6cfd0148425e528b859b26e436b01f23f6926224", "tree": "60e3257053554ff198fe5825e6f12a00c3b4422a", "parents": [ "a9e220f8322e2b0e0b8903fe00265461cffad3f0" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Tue May 05 15:40:36 2009 +0200" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Thu Jun 11 21:36:07 2009 -0400" }, "message": "push BKL down into -\u003eput_super\n\nMove BKL into -\u003eput_super from the only caller. A couple of\nfilesystems had trivial enough -\u003eput_super (only kfree and NULLing of\ns_fs_info + stuff in there) to not get any locking: coda, cramfs, efs,\nhugetlbfs, omfs, qnx4, shmem, all others got the full treatment. Most\nof them probably don\u0027t need it, but I\u0027d rather sort that out individually.\nPreferably after all the other BKL pushdowns in that area.\n\n[AV: original used to move lock_super() down as well; these changes are\nremoved since we don\u0027t do lock_super() at all in generic_shutdown_super()\nnow]\n[AV: fuse, btrfs and xfs are known to need no damn BKL, exempt]\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "a9e220f8322e2b0e0b8903fe00265461cffad3f0", "tree": "b3be7d58b8eb9fd810636223f0458191ec1b9d75", "parents": [ "62c6943b4b1e818aea60c11c5a68a50785b83119" ], "author": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Tue May 05 22:10:44 2009 -0400" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Thu Jun 11 21:36:07 2009 -0400" }, "message": "No need to do lock_super() for exclusion in generic_shutdown_super()\n\nWe can\u0027t run into contention on it. All other callers of lock_super()\neither hold s_umount (and we have it exclusive) or hold an active\nreference to superblock in question, which prevents the call of\ngeneric_shutdown_super() while the reference is held. So we can\nreplace lock_super(s) with get_fs_excl() in generic_shutdown_super()\n(and corresponding change for unlock_super(), of course).\n\nSince ext4 expects s_lock held for its put_super, take lock_super()\ninto it. The rest of filesystems do not care at all.\n\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "8c85e125124a473d6f3e9bb187b0b84207f81d91", "tree": "d883424a156c00c55193e46567efdffddb6ef6b9", "parents": [ "517bfae28353e996160518add4d00033d3886e61" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Tue Apr 28 18:00:26 2009 +0200" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Thu Jun 11 21:36:06 2009 -0400" }, "message": "remove -\u003ewrite_super call in generic_shutdown_super\n\nWe just did a full fs writeout using sync_filesystem before, and if\nthat\u0027s not enough for the filesystem it can perform it\u0027s own writeout\nin -\u003eput_super, which many filesystems already do.\n\nMove a call to foofs_write_super into every foofs_put_super for now to\nguarantee identical behaviour until it\u0027s cleaned up by the individual\nfilesystem maintainers.\n\nExceptions:\n\n - affs already has identical copy \u0026 pasted code at the beginning of\n affs_put_super so no need to do it twice.\n - xfs does the right thing without it and I have changes pending for\n the xfs tree touching this are so I don\u0027t really need conflicts\n here..\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "c9059598ea8981d02356eead3188bf7fa4d717b8", "tree": "03e73b20a30e988da7c6a3e0ad93b2dc5843274d", "parents": [ "0a33f80a8373eca7f4bea3961d1346c3815fa5ed", "b0fd271d5fba0b2d00888363f3869e3f9b26caa9" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Jun 11 10:52:27 2009 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Jun 11 11:10:35 2009 -0700" }, "message": "Merge branch \u0027for-2.6.31\u0027 of git://git.kernel.dk/linux-2.6-block\n\n* \u0027for-2.6.31\u0027 of git://git.kernel.dk/linux-2.6-block: (153 commits)\n block: add request clone interface (v2)\n floppy: fix hibernation\n ramdisk: remove long-deprecated \"ramdisk\u003d\" boot-time parameter\n fs/bio.c: add missing __user annotation\n block: prevent possible io_context-\u003erefcount overflow\n Add serial number support for virtio_blk, V4a\n block: Add missing bounce_pfn stacking and fix comments\n Revert \"block: Fix bounce limit setting in DM\"\n cciss: decode unit attention in SCSI error handling code\n cciss: Remove no longer needed sendcmd reject processing code\n cciss: change SCSI error handling routines to work with interrupts enabled.\n cciss: separate error processing and command retrying code in sendcmd_withirq_core()\n cciss: factor out fix target status processing code from sendcmd functions\n cciss: simplify interface of sendcmd() and sendcmd_withirq()\n cciss: factor out core of sendcmd_withirq() for use by SCSI error handling code\n cciss: Use schedule_timeout_uninterruptible in SCSI error handling code\n block: needs to set the residual length of a bidi request\n Revert \"block: implement blkdev_readpages\"\n block: Fix bounce limit setting in DM\n Removed reference to non-existing file Documentation/PCI/PCI-DMA-mapping.txt\n ...\n\nManually fix conflicts with tracing updates in:\n\tblock/blk-sysfs.c\n\tdrivers/ide/ide-atapi.c\n\tdrivers/ide/ide-cd.c\n\tdrivers/ide/ide-floppy.c\n\tdrivers/ide/ide-tape.c\n\tinclude/trace/events/block.h\n\tkernel/trace/blktrace.c\n" }, { "commit": "b31e15527a9bb71b6a11a425d17ce139a62f5af5", "tree": "3b8fdb014e3b960b27369643de9ad1213ec2cbba", "parents": [ "03f5d8bcf094a5e3b501bd2ae1553656efa8d1be" ], "author": { "name": "Eric Sandeen", "email": "sandeen@redhat.com", "time": "Thu Jun 04 17:36:36 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Thu Jun 04 17:36:36 2009 -0400" }, "message": "ext4: Change all super.c messages to print the device\n\nThis patch changes ext4 super.c to include the device name with all \nwarning/error messages, by using a new utility function ext4_msg. \nIt\u0027s a rather large patch, but very mechanic. I left debug printks\nalone.\n\nThis is a straightforward port of a patch which Andi Kleen did for\next3.\n\nCc: Andi Kleen \u003cak@linux.intel.com\u003e\nSigned-off-by: Eric Sandeen \u003csandeen@redhat.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "0b8e58a140cae2ba1c4a21ccae7c6c3c939c51f9", "tree": "70fc974b7f4b258a3cf0a64a825dbebc9e1f1150", "parents": [ "bfcd3555af478dbf04c87adc9bb1a739d0a6ccff" ], "author": { "name": "Andreas Dilger", "email": "adilger@sun.com", "time": "Wed Jun 03 17:59:28 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Jun 03 17:59:28 2009 -0400" }, "message": "ext4: super.c whitespace cleanup\n\nCleanup of whitespace and formatting. Initially driven by confusing indents\nfor the ext4_{block,inode}_bitmap() et. al. helper routines, but figured I\u0027d\ncleanup some other 80-column wrapping and other indenting problems at the\nsame time.\n\nSigned-off-by: Andreas Dilger \u003cadilger@sun.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "88b6edd17c62b7d346d21f4087893ce7d4ef828a", "tree": "e6c80d48f184861c965a58bd88fd3a023b65a1c9", "parents": [ "759d427aa5a9d88a81afd11817cdeb40aea85234" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon May 25 11:50:39 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon May 25 11:50:39 2009 -0400" }, "message": "ext4: Clean up calls to ext4_get_group_desc()\n\nIf the caller isn\u0027t planning on modifying the block group descriptors,\nthere\u0027s no need to pass in a pointer to a struct buffer_head. Nuking\nthis saves a tiny amount of CPU time and stack space usage.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "e1defc4ff0cf57aca6c5e3ff99fa503f5943c1f1", "tree": "d60d15a082171c58ac811d547d51a9c3119f23e3", "parents": [ "9bd7de51ee8537094656149eaf45338cadb7d7d4" ], "author": { "name": "Martin K. Petersen", "email": "martin.petersen@oracle.com", "time": "Fri May 22 17:17:49 2009 -0400" }, "committer": { "name": "Jens Axboe", "email": "jens.axboe@oracle.com", "time": "Fri May 22 23:22:54 2009 +0200" }, "message": "block: Do away with the notion of hardsect_size\n\nUntil now we have had a 1:1 mapping between storage device physical\nblock size and the logical block sized used when addressing the device.\nWith SATA 4KB drives coming out that will no longer be the case. The\nsector size will be 4KB but the logical block size will remain\n512-bytes. Hence we need to distinguish between the physical block size\nand the logical ditto.\n\nThis patch renames hardsect_size to logical_block_size.\n\nSigned-off-by: Martin K. Petersen \u003cmartin.petersen@oracle.com\u003e\nSigned-off-by: Jens Axboe \u003cjens.axboe@oracle.com\u003e\n" }, { "commit": "f68301656b5f5d2de104f2687add6beeb8f3c3b9", "tree": "b5f559c14d81031f7f0c43c229625bdc808e0163", "parents": [ "0568c518937ee3a9b6a94d18bae9c150fe5d6832" ], "author": { "name": "Manish Katiyar", "email": "mkatiyar@gmail.com", "time": "Sun May 17 23:52:44 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sun May 17 23:52:44 2009 -0400" }, "message": "ext4: Fix memory leak in ext4_fill_super() in case of a failed mount\n\nSigned-off-by: Manish Katiyar \u003cmkatiyar@gmail.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "6fd058f7791087648c683eb8572edf3be3c4c23c", "tree": "0d80791532d2d022c91f20013003716eaf0afb40", "parents": [ "2ac3b6e00acb46406c993d57921f86a594aafe08" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sun May 17 15:38:01 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sun May 17 15:38:01 2009 -0400" }, "message": "ext4: Add a comprehensive block validity check to ext4_get_blocks()\n\nTo catch filesystem bugs or corruption which could lead to the\nfilesystem getting severly damaged, this patch adds a facility for\ntracking all of the filesystem metadata blocks by contiguous regions\nin a red-black tree. This allows quick searching of the tree to\nlocate extents which might overlap with filesystem metadata blocks.\n\nThis facility is also used by the multi-block allocator to assure that\nit is not allocating blocks out of the system zone, as well as by the\nroutines used when reading indirect blocks and extents information\nfrom disk to make sure their contents are valid.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "955ce5f5be67dfe0d1d096b543af33fe8a1ce3dd", "tree": "68b0bdbef1594a3e43c1ef28ae8e096b40a06ae4", "parents": [ "eefd7f03b86b8a319890e7fac5a6fcc7f8694b76" ], "author": { "name": "Aneesh Kumar K.V", "email": "aneesh.kumar@linux.vnet.ibm.com", "time": "Sat May 02 20:35:09 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat May 02 20:35:09 2009 -0400" }, "message": "ext4: Convert ext4_lock_group to use sb_bgl_lock\n\nWe have sb_bgl_lock() and ext4_group_info.bb_state\nbit spinlock to protech group information. The later is only\nused within mballoc code. Consolidate them to use sb_bgl_lock().\nThis makes the mballoc.c code much simpler and also avoid\nconfusion with two locks protecting same info.\n\nSigned-off-by: Aneesh Kumar K.V \u003caneesh.kumar@linux.vnet.ibm.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "f40339031b04279c3fdde7ac5fe97db33b2a7694", "tree": "62b565c12488c63e620e5686304c16ed3434b735", "parents": [ "bb23c20a851a5038b255a3c0d0aa56093c1da3f8" ], "author": { "name": "Curt Wohlgemuth", "email": "curtw@google.com", "time": "Fri May 01 20:27:20 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri May 01 20:27:20 2009 -0400" }, "message": "ext4: Make the length of the mb_history file tunable\n\nIn memory-constrained systems with many partitions, the ~68K for each\npartition for the mb_history buffer can be excessive.\n\nThis patch adds a new mount option, mb_history_length, as well as a\nway of setting the default via a module parameter (or via a sysfs\nparameter in /sys/module/ext4/parameter/default_mb_history_length).\nIf the mb_history_length is set to zero, the mb_history facility is\ndisabled entirely.\n\nSigned-off-by: Curt Wohlgemuth \u003ccurtw@google.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n\n" }, { "commit": "bb23c20a851a5038b255a3c0d0aa56093c1da3f8", "tree": "257211bf2bf5ffd53fe24b0528928ca4d3f2ecba", "parents": [ "596397b77c895d0fa3674f579c94ad5ea88ef01d" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri May 01 19:44:44 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri May 01 19:44:44 2009 -0400" }, "message": "ext4: Move fs/ext4/group.h into ext4.h\n\nMove the function prototypes in group.h into ext4.h so they are all\ndefined in one place.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "596397b77c895d0fa3674f579c94ad5ea88ef01d", "tree": "bd4f9916556b4d5bc59ee4b5171248df44e2c5c4", "parents": [ "ca0faba0e8ac844dc0279825eb8db876b5962ea5" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri May 01 13:49:15 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri May 01 13:49:15 2009 -0400" }, "message": "ext4: Move fs/ext4/namei.h into ext4.h\n\nThe fs/ext4/namei.h header file had only a single function\ndeclaration, and should have never been a standalone file. Move it\ninto ext4.h, where should have been from the beginning.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "9bffad1ed2a003a355ed1b42424a0ae3575275ed", "tree": "9016e7b0e04a0e5319680f9e1f89fc1abb13c765", "parents": [ "879c5e6b7cb4c689d08ca9b2e353d8ab3dc425d5" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Jun 17 11:48:11 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Jun 17 11:48:11 2009 -0400" }, "message": "ext4: convert instrumentation from markers to tracepoints\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "32ed5058ce90024efcd811254b4b1de0468099df", "tree": "0054cc5c385b4ba02abd95a761ccb01b453ba05f", "parents": [ "3b9d4ed26680771295d904a6b83e88e620780893" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Apr 25 22:53:39 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Apr 25 22:53:39 2009 -0400" }, "message": "ext4: Replace lock/unlock_super() with an explicit lock for resizing\n \nUse a separate lock to protect s_groups_count and the other block\ngroup descriptors which get changed via an on-line resize operation,\nso we can stop overloading the use of lock_super().\n \nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n\n" }, { "commit": "3b9d4ed26680771295d904a6b83e88e620780893", "tree": "905b0e95697839c446c86250cf38dd256f5e846a", "parents": [ "a63c9eb2ce6f5028da90f282798232c4f398ceb8" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Apr 25 22:54:04 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Apr 25 22:54:04 2009 -0400" }, "message": "ext4: Replace lock/unlock_super() with an explicit lock for the orphan list\n\nUse a separate lock to protect the orphan list, so we can stop\noverloading the use of lock_super().\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "a63c9eb2ce6f5028da90f282798232c4f398ceb8", "tree": "3b32193dfc80a3925f5ea5a6545765f5176a6f2d", "parents": [ "114e9fc90703bd6aac0229fb559e97caa6c49770" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri May 01 01:59:42 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri May 01 01:59:42 2009 -0400" }, "message": "ext4: ext4_mark_recovery_complete() doesn\u0027t need to use lock_super\n\nThe function ext4_mark_recovery_complete() is called from two call\npaths: either (a) while mounting the filesystem, in which case there\u0027s\nno danger of any other CPU calling write_super() until the mount is\ncompleted, and (b) while remounting the filesystem read-write, in\nwhich case the fs core has already locked the superblock. This also\nallows us to take out a very vile unlock_super()/lock_super() pair in\next4_remount().\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "114e9fc90703bd6aac0229fb559e97caa6c49770", "tree": "722343de92b421c252a9e33b0e5e44955115080a", "parents": [ "8df9675f8b498d0bfa1f0b5b06f56bf1ff366dd5" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Apr 25 15:48:07 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Apr 25 15:48:07 2009 -0400" }, "message": "ext4: Remove outdated comment about lock_super()\n\next4_fill_super() is no longer called by read_super(), and it is no\nlonger called with the superblock locked. The\nunlock_super()/lock_super() is no longer present, so this comment is\nentirely superfluous.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "8df9675f8b498d0bfa1f0b5b06f56bf1ff366dd5", "tree": "38fd56a82049f50b4d774af47b9d39f116071755", "parents": [ "9ca92389c5312a51e819c15c762f0abdc7f3129b" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri May 01 08:50:38 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri May 01 08:50:38 2009 -0400" }, "message": "ext4: Avoid races caused by on-line resizing and SMP memory reordering\n\nExt4\u0027s on-line resizing adds a new block group and then, only at the\nlast step adjusts s_groups_count. However, it\u0027s possible on SMP\nsystems that another CPU could see the updated the s_group_count and\nnot see the newly initialized data structures for the just-added block\ngroup. For this reason, it\u0027s important to insert a SMP read barrier\nafter reading s_groups_count and before reading any (for example) the\nnew block group descriptors allowed by the increased value of\ns_groups_count.\n\nUnfortunately, we rather blatently violate this locking protocol\ndocumented in fs/ext4/resize.c. Fortunately, (1) on-line resizes\nhappen relatively rarely, and (2) it seems rare that the filesystem\ncode will immediately try to use just-added block group before any\nmemory ordering issues resolve themselves. So apparently problems\nhere are relatively hard to hit, since ext3 has been vulnerable to the\nsame issue for years with no one apparently complaining.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "9ca92389c5312a51e819c15c762f0abdc7f3129b", "tree": "0f99256a5632614134573283853c577676cb1b99", "parents": [ "7234ab2a55e77784b44cf2d862136d9e41b8d98a" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri May 01 12:52:25 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri May 01 12:52:25 2009 -0400" }, "message": "ext4: Use separate super_operations structure for no_journal filesystems\n\nBy using a separate super_operations structure for filesystems that\nhave and don\u0027t have journals, we can simply ext4_write_super() ---\nwhich is only needed when no journal is present --- and ext4_freeze(),\next4_unfreeze(), and ext4_sync_fs(), which are only needed when the\njournal is present.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "7234ab2a55e77784b44cf2d862136d9e41b8d98a", "tree": "cad3f1ee096243529125b3d6a028cc1426773b9c", "parents": [ "e2d670523c6c4ccb0fca9f3ab1b8f066d9aa57d6" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Thu Apr 30 21:24:04 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Thu Apr 30 21:24:04 2009 -0400" }, "message": "ext4: Fix and simplify s_dirt handling\n\nThe s_dirt flag wasn\u0027t completely handled correctly, but it didn\u0027t\nreally matter when journalling was enabled. It turns out that when\next4 runs without a journal, we don\u0027t clear s_dirt in places where we\nshould have, with the result that the high-level write_super()\nfunction was writing the superblock when it wasn\u0027t necessary.\n\nSo we fix this by making ext4_commit_super() clear the s_dirt flag,\nand removing many of the other places where s_dirt is manipulated.\nWhen journalling is enabled, the s_dirt flag might be left set more\noften, but s_dirt really doesn\u0027t matter when journalling is enabled.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "e2d670523c6c4ccb0fca9f3ab1b8f066d9aa57d6", "tree": "648f9a29142831ded24fd92d22d3add5c3190185", "parents": [ "f7c439504ccba0cca43271e651013ab97a221c62" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri May 01 00:33:44 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri May 01 00:33:44 2009 -0400" }, "message": "ext4: Simplify ext4_commit_super()\u0027s function signature\n\nThe ext4_commit_super() function took both a struct super_block * and\na struct ext4_super_block *, but the struct ext4_super_block can be\nderived from the struct super_block.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "f7c439504ccba0cca43271e651013ab97a221c62", "tree": "35f2489b2503bdc9273435e8b433ac58b8a1f276", "parents": [ "c5ca7c7636fa689a9746b6032f83aa7fffec31c6" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Apr 24 23:31:59 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Apr 24 23:31:59 2009 -0400" }, "message": "ext4: Use is_power_of_2() for clarity\n\nSigned-off-by: Robert P. J. Day \u003crpjday@crashcourse.ca\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "c5ca7c7636fa689a9746b6032f83aa7fffec31c6", "tree": "eebbdd1d477b5062148ee61c9e1bf1d4da3e9e05", "parents": [ "29fa89d088941d79765d60f22d5ccdd6b8696e11" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Apr 27 22:48:48 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Apr 27 22:48:48 2009 -0400" }, "message": "ext4: Fallback to vmalloc if kmalloc can\u0027t allocate s_flex_groups array\n\nFor very large filesystems, the s_flex_groups array can get quite big.\nFor example, a filesystem that can be resized up to 16TB will have\n8192 flex groups (assuming the default flex_bg size of 16), so the\narray is 96k, which is *very* marginal for kmalloc(). On the other\nhand, a 160GB filesystem without the resize_inode feature will only\nrequire 960 bytes. So we try to allocate the array first using\nkmalloc(), and if that fails, we\u0027ll try to use vmalloc() instead.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "0f2ddca66d70c8ccba7486cf2d79c6b60e777abd", "tree": "7d58c31ab30ba2b9e94780008a2083ac87f80db5", "parents": [ "e44543b83bf4ab84dc6bd5b88158c78b1ed1c208" ], "author": { "name": "From: Thiemo Nagel", "email": "thiemo.nagel@ph.tum.de", "time": "Tue Apr 07 14:07:47 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Apr 07 14:07:47 2009 -0400" }, "message": "ext4: check block device size on mount\n\nSigned-off-by: Thiemo Nagel \u003cthiemo.nagel@ph.tum.de\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "06705bff9114531a997a7d0c2520bea0f2927410", "tree": "f7bef499cd491c8171db45da5b02c168655d4236", "parents": [ "e7c9e3e99adf6c49c5d593a51375916acc039d1e" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Mar 28 10:59:57 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Mar 28 10:59:57 2009 -0400" }, "message": "ext4: Regularize mount options\n\nAdd support for using the mount options \"barrier\" and \"nobarrier\", and\n\"auto_da_alloc\" and \"noauto_da_alloc\", which is more consistent than\n\"barrier\u003d\u003c0|1\u003e\" or \"auto_da_alloc\u003d\u003c0|1\u003e\". Most other ext3/ext4 mount\noptions use the foo/nofoo naming convention. We allow the old forms\nof these mount options for backwards compatibility.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "afd4672dc7610b7feef5190168aa917cc2e417e4", "tree": "53a3aa709232b00473c8da70b792b350150956ff", "parents": [ "7d39db14a42cbd719c7515b9da8f85a2eb6a0633" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Mar 16 23:12:23 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Mar 16 23:12:23 2009 -0400" }, "message": "ext4: Add auto_da_alloc mount option\n\nAdd a mount option which allows the user to disable automatic\nallocation of blocks whose allocation by delayed allocation when the\nfile was originally truncated or when the file is renamed over an\nexisting file. This feature is intended to save users from the\neffects of naive application writers, but it reduces the effectiveness\nof the delayed allocation code. This mount option disables this\nsafety feature, which may be desirable for prodcutions systems where\nthe risk of unclean shutdowns or unexpected system crashes is low.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "7d39db14a42cbd719c7515b9da8f85a2eb6a0633", "tree": "5c93b9f76c9895183d1e973ed296cd9b7a1d9a0e", "parents": [ "9f24e4208f7ee2748f157368b63287dc903fcf60" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Mar 04 19:31:53 2009 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Mar 04 19:31:53 2009 -0500" }, "message": "ext4: Use struct flex_groups to calculate get_orlov_stats()\n\nInstead of looping over all of the block groups in a flex group\nsumming their summary statistics, start tracking used_dirs in struct\nflex_groups, and use struct flex_groups instead. This should save a\nbit of CPU for mkdir-heavy workloads.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "9f24e4208f7ee2748f157368b63287dc903fcf60", "tree": "255989fe69ebfb2b031dc7cf6dbe975df67c711a", "parents": [ "b713a5ec55bf73c833f9883cdd761b20ee61a1ab" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Mar 04 19:09:10 2009 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Mar 04 19:09:10 2009 -0500" }, "message": "ext4: Use atomic_t\u0027s in struct flex_groups\n\nReduce pressure on the sb_bgl_lock family of locks by using atomic_t\u0027s\nto track the number of free blocks and inodes in each flex_group.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n\n\n" }, { "commit": "b713a5ec55bf73c833f9883cdd761b20ee61a1ab", "tree": "77bbc689f442cad3ce8ca21d7b2c7cea2738d519", "parents": [ "3197ebdb130473a92760100cbfe0d7e671838f48" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Mar 31 09:11:14 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Mar 31 09:11:14 2009 -0400" }, "message": "ext4: remove /proc tuning knobs\n\nRemove tuning knobs in /proc/fs/ext4/\u003cdev/* since they have been\nreplaced by knobs in sysfs at /sys/fs/ext4/\u003cdev\u003e/*.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "3197ebdb130473a92760100cbfe0d7e671838f48", "tree": "7101dc642e91026a65264adb7845ce3561d691fe", "parents": [ "afc32f7ee9febc020c73da61402351d4c90437f3" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Mar 31 09:10:09 2009 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Mar 31 09:10:09 2009 -0400" }, "message": "ext4: Add sysfs support\n\nAdd basic sysfs support so that information about the mounted\nfilesystem and various tuning parameters can be accessed via\n/sys/fs/ext4/\u003cdev\u003e/*.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "afc32f7ee9febc020c73da61402351d4c90437f3", "tree": "7b78aaaac87eb704074f6ece996b2c78a69fbe18", "parents": [ "d6014301b5599fba395c42a1e96a7fe86f7d0b2d" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Feb 28 19:39:58 2009 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Feb 28 19:39:58 2009 -0500" }, "message": "ext4: Track lifetime disk writes\n\nAdd a new superblock value which tracks the lifetime amount of writes\nto the filesystem. This is useful in estimating the amount of wear on\nsolid state drives (SSD\u0027s) caused by writes to the filesystem.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "705895b61133ef43d106fe6a6bbdb2eec923867e", "tree": "ea05232098c0425fda052240a8bb0e6218bb5e82", "parents": [ "3d0518f4758eca4339e75e5b9dbb7e06a5ce08b4" ], "author": { "name": "Pekka Enberg", "email": "penberg@cs.helsinki.fi", "time": "Sun Feb 15 18:07:52 2009 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sun Feb 15 18:07:52 2009 -0500" }, "message": "ext4: allocate -\u003es_blockgroup_lock separately\n\nAs spotted by kmemtrace, struct ext4_sb_info is 17664 bytes on 64-bit\nwhich makes it a very bad fit for SLAB allocators. The culprit of the\nwasted memory is -\u003es_blockgroup_lock which can be as big as 16 KB when\nNR_CPUS \u003e\u003d 32.\n\nTo fix that, allocate -\u003es_blockgroup_lock, which fits nicely in a order 2\npage in the worst case, separately. This shinks down struct ext4_sb_info\nenough to fit a 2 KB slab cache so now we allocate 16 KB + 2 KB instead of\n32 KB saving 14 KB of memory.\n\nAcked-by: Andreas Dilger \u003cadilger@sun.com\u003e\nSigned-off-by: Pekka Enberg \u003cpenberg@cs.helsinki.fi\u003e\nCc: \u003clinux-ext4@vger.kernel.org\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "a269eb18294d35874c53311acc2cd0b5ef477ce5", "tree": "4da256ba45385688bd7f1e8b638ce76f884c8313", "parents": [ "81a052273998f94b098945c4c313e05246956eb2" ], "author": { "name": "Jan Kara", "email": "jack@suse.cz", "time": "Mon Jan 26 17:04:39 2009 +0100" }, "committer": { "name": "Jan Kara", "email": "jack@suse.cz", "time": "Thu Mar 26 02:18:36 2009 +0100" }, "message": "ext4: Use lowercase names of quota functions\n\nUse lowercase names of quota functions instead of old uppercase ones.\n\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\nAcked-by: Mingming Cao \u003ccmm@us.ibm.com\u003e\nCC: linux-ext4@vger.kernel.org\n" }, { "commit": "60e58e0f30e723464c2a7d34b71b8675566c572d", "tree": "2797ae1bccdad12d53c989a6dccea1c8ffd2bce3", "parents": [ "643d00ccc311664188c8209bf8b596a30e139c3a" ], "author": { "name": "Mingming Cao", "email": "cmm@us.ibm.com", "time": "Thu Jan 22 18:13:05 2009 +0100" }, "committer": { "name": "Jan Kara", "email": "jack@suse.cz", "time": "Thu Mar 26 02:18:34 2009 +0100" }, "message": "ext4: quota reservation for delayed allocation\n\nUses quota reservation/claim/release to handle quota properly for delayed\nallocation in the three steps: 1) quotas are reserved when data being copied\nto cache when block allocation is defered 2) when new blocks are allocated.\nreserved quotas are converted to the real allocated quota, 2) over-booked\nquotas for metadata blocks are released back.\n\nSigned-off-by: Mingming Cao \u003ccmm@us.ibm.com\u003e\nAcked-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\n" }, { "commit": "edf7245362f7b8b8c76c4a6cad3604bf80884848", "tree": "e5a78aeac197c945e1ef6c1321b3ec5dd78378e7", "parents": [ "a219ce3748bbc596cec85c44754b3f6b994f1e1d" ], "author": { "name": "Jan Kara", "email": "jack@suse.cz", "time": "Mon Jan 12 19:05:26 2009 +0100" }, "committer": { "name": "Jan Kara", "email": "jack@suse.cz", "time": "Thu Mar 26 02:18:34 2009 +0100" }, "message": "ext4: Remove unnecessary quota functions\n\next4_dquot_initialize() and ext4_dquot_drop() is no longer\nneeded because of modified quota locking.\n\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\n" }, { "commit": "8b1a8ff8b321a9384304aeea4dbdb9747daf7ee8", "tree": "7be11423c5b5a10e085122b5a3e8d004e5fa865a", "parents": [ "ebd3610b110bbb18ea6f9f2aeed1e1068c537227" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Feb 28 00:08:53 2009 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Feb 28 00:08:53 2009 -0500" }, "message": "ext4: Remove duplicate call to ext4_commit_super() in ext4_freeze()\n\nCommit c4be0c1d added error checking to ext4_freeze() when calling\next4_commit_super(). Unfortunately the patch failed to remove the\noriginal call to ext4_commit_super(), with the net result that when\nfreezing the filesystem, the superblock gets written twice, the first\ntime without error checking.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n\n" }, { "commit": "9eddacf9e9c03578ef2c07c9534423e823d677f8", "tree": "6b317bb2e531ba56c9bc7ece8c41ec039d12d309", "parents": [ "c88ccea3143975294f5a52097546bcbb75975f52" ], "author": { "name": "Jan Kara", "email": "jack@suse.cz", "time": "Tue Feb 10 06:46:05 2009 -0500" }, "committer": { "name": "Theodore Tso", "email": "tytso@mit.edu", "time": "Tue Feb 10 06:46:05 2009 -0500" }, "message": "Revert \"ext4: wait on all pending commits in ext4_sync_fs()\"\n\nThis undoes commit 14ce0cb411c88681ab8f3a4c9caa7f42e97a3184.\n\nSince jbd2_journal_start_commit() is now fixed to return 1 when we\nstarted a transaction commit, there\u0027s some transaction waiting to be\ncommitted or there\u0027s a transaction already committing, we don\u0027t\nneed to call ext4_force_commit() in ext4_sync_fs(). Furthermore\next4_force_commit() can unnecessarily create sync transaction which is\nexpensive so it\u0027s worthwhile to remove it when we can.\n\nhttp://bugzilla.kernel.org/show_bug.cgi?id\u003d12224\n\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nCc: Eric Sandeen \u003csandeen@redhat.com\u003e\nCc: linux-ext4@vger.kernel.org\n" }, { "commit": "c4be0c1dc4cdc37b175579be1460f15ac6495e9a", "tree": "716ea88318211ed27cadcebda0fd85c1f8246edb", "parents": [ "69347a236b22c3962ea812511495e502dedfd50c" ], "author": { "name": "Takashi Sato", "email": "t-sato@yk.jp.nec.com", "time": "Fri Jan 09 16:40:58 2009 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Jan 09 16:54:42 2009 -0800" }, "message": "filesystem freeze: add error handling of write_super_lockfs/unlockfs\n\nCurrently, ext3 in mainline Linux doesn\u0027t have the freeze feature which\nsuspends write requests. So, we cannot take a backup which keeps the\nfilesystem\u0027s consistency with the storage device\u0027s features (snapshot and\nreplication) while it is mounted.\n\nIn many case, a commercial filesystem (e.g. VxFS) has the freeze feature\nand it would be used to get the consistent backup.\n\nIf Linux\u0027s standard filesystem ext3 has the freeze feature, we can do it\nwithout a commercial filesystem.\n\nSo I have implemented the ioctls of the freeze feature.\nI think we can take the consistent backup with the following steps.\n1. Freeze the filesystem with the freeze ioctl.\n2. Separate the replication volume or create the snapshot\n with the storage device\u0027s feature.\n3. Unfreeze the filesystem with the unfreeze ioctl.\n4. Take the backup from the separated replication volume\n or the snapshot.\n\nThis patch:\n\nVFS:\nChanged the type of write_super_lockfs and unlockfs from \"void\"\nto \"int\" so that they can return an error.\nRename write_super_lockfs and unlockfs of the super block operation\nfreeze_fs and unfreeze_fs to avoid a confusion.\n\next3, ext4, xfs, gfs2, jfs:\nChanged the type of write_super_lockfs and unlockfs from \"void\"\nto \"int\" so that write_super_lockfs returns an error if needed,\nand unlockfs always returns 0.\n\nreiserfs:\nChanged the type of write_super_lockfs and unlockfs from \"void\"\nto \"int\" so that they always return 0 (success) to keep a current behavior.\n\nSigned-off-by: Takashi Sato \u003ct-sato@yk.jp.nec.com\u003e\nSigned-off-by: Masayuki Hamaguchi \u003cm-hamaguchi@ys.jp.nec.com\u003e\nCc: \u003cxfs-masters@oss.sgi.com\u003e\nCc: \u003clinux-ext4@vger.kernel.org\u003e\nCc: Christoph Hellwig \u003chch@lst.de\u003e\nCc: Dave Kleikamp \u003cshaggy@austin.ibm.com\u003e\nCc: Dave Chinner \u003cdavid@fromorbit.com\u003e\nCc: Alasdair G Kergon \u003cagk@redhat.com\u003e\nCc: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "2150edc6c5cf00f7adb54538b9ea2a3e9cedca3f", "tree": "f72a0d85e66f500b4cead348a231e3d3b9f357bc", "parents": [ "cd764695b67386a81964f68e9c66efd9f13f4d29", "4b905671d2ea09fd48fed72c581df17e40823f39" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Jan 08 17:14:59 2009 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Jan 08 17:14:59 2009 -0800" }, "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: (57 commits)\n jbd2: Fix oops in jbd2_journal_init_inode() on corrupted fs\n ext4: Remove \"extents\" mount option\n block: Add Kconfig help which notes that ext4 needs CONFIG_LBD\n ext4: Make printk\u0027s consistently prefixed with \"EXT4-fs: \"\n ext4: Add sanity checks for the superblock before mounting the filesystem\n ext4: Add mount option to set kjournald\u0027s I/O priority\n jbd2: Submit writes to the journal using WRITE_SYNC\n jbd2: Add pid and journal device name to the \"kjournald2 starting\" message\n ext4: Add markers for better debuggability\n ext4: Remove code to create the journal inode\n ext4: provide function to release metadata pages under memory pressure\n ext3: provide function to release metadata pages under memory pressure\n add releasepage hooks to block devices which can be used by file systems\n ext4: Fix s_dirty_blocks_counter if block allocation failed with nodelalloc\n ext4: Init the complete page while building buddy cache\n ext4: Don\u0027t allow new groups to be added during block allocation\n ext4: mark the blocks/inode bitmap beyond end of group as used\n ext4: Use new buffer_head flag to check uninit group bitmaps initialization\n ext4: Fix the race between read_inode_bitmap() and ext4_new_inode()\n ext4: code cleanup\n ...\n" }, { "commit": "83982b6f47201c4c7767210d24d7d8c99567a0b3", "tree": "f1c19b1c6b5a34dd0c5de7519b78414b7a9267ee", "parents": [ "4d783b093cd4f3e2738527365979cbd1c5101065" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jan 06 14:53:16 2009 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jan 06 14:53:16 2009 -0500" }, "message": "ext4: Remove \"extents\" mount option\n\nThis mount option is largely superfluous, and in fact the way it was\nimplemented was buggy; if a filesystem which did not have the extents\nfeature flag was mounted -o extents, the filesystem would attempt to\ncreate and use extents-based file even though the extents feature flag\nwas not eabled. The simplest thing to do is to nuke the mount option\nentirely. It\u0027s not all that useful to force the non-creation of new\nextent-based files if the filesystem can support it.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "abda14189251563a50f56da5ea2e37e904ac4cba", "tree": "4c6e3a00f247cad1c41896f749c2c01cebff579f", "parents": [ "4ec110281379826c5cf6ed14735e47027c3c5765" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jan 06 00:20:32 2009 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jan 06 00:20:32 2009 -0500" }, "message": "ext4: Make printk\u0027s consistently prefixed with \"EXT4-fs: \"\n\nPreviously, some were \"ext4: \", and some were \"EXT4: \"; change them to\nbe consistent with most ext4 printk\u0027s, which is to use \"EXT4-fs: \".\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "4ec110281379826c5cf6ed14735e47027c3c5765", "tree": "593bcbafe3541264e4effe5310546617de0a76ce", "parents": [ "b3881f74b31b7d47d0f1c4d89ac3e7f0b9c05e3e" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jan 06 14:53:26 2009 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jan 06 14:53:26 2009 -0500" }, "message": "ext4: Add sanity checks for the superblock before mounting the filesystem\n\nThis avoids insane superblock configurations that could lead to kernel\noops due to null pointer derefences.\n\nhttp://bugzilla.kernel.org/show_bug.cgi?id\u003d12371\n\nThanks to David Maciejak at Fortinet\u0027s FortiGuard Global Security\nResearch Team who discovered this bug independently (but at\napproximately the same time) as Thiemo Nagel, who submitted the patch.\n\nSigned-off-by: Thiemo Nagel \u003cthiemo.nagel@ph.tum.de\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nCc: stable@kernel.org\n" }, { "commit": "b3881f74b31b7d47d0f1c4d89ac3e7f0b9c05e3e", "tree": "131190b7ec627fd2ef2ecc818a7b9c17b83ccd63", "parents": [ "40a1984d22294ab202f616e432bb8d3481897675" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 05 22:46:26 2009 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 05 22:46:26 2009 -0500" }, "message": "ext4: Add mount option to set kjournald\u0027s I/O priority\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nCc: Jens Axboe \u003cjens.axboe@oracle.com\u003e\n" }, { "commit": "a5b5ee320185adc091a3a31630d278806b19d8f0", "tree": "91754a6c5645a9d3dd0f9bee828550f704939bfc", "parents": [ "157091a2c3cdc71422cbc71eace205cf1b9f2200" ], "author": { "name": "Jan Kara", "email": "jack@suse.cz", "time": "Tue Nov 25 15:31:35 2008 +0100" }, "committer": { "name": "Mark Fasheh", "email": "mfasheh@suse.com", "time": "Mon Jan 05 08:40:26 2009 -0800" }, "message": "ext4: Add default allocation routines for quota structures\n\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\nSigned-off-by: Mark Fasheh \u003cmfasheh@suse.com\u003e\n" }, { "commit": "17bd13b31ce4fe7f789d8848e8cbc8cb42b10544", "tree": "ced03fa069a1493421b6c0b0c11e5a163b5dbed6", "parents": [ "ee0d5ffe0da2aa992004447113e28622621a983f" ], "author": { "name": "Jan Kara", "email": "jack@suse.cz", "time": "Wed Aug 20 18:14:35 2008 +0200" }, "committer": { "name": "Mark Fasheh", "email": "mfasheh@suse.com", "time": "Mon Jan 05 08:36:56 2009 -0800" }, "message": "ext4: Use sb_any_quota_loaded() instead of sb_any_quota_enabled()\n\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\nSigned-off-by: Mark Fasheh \u003cmfasheh@suse.com\u003e\n" }, { "commit": "c31910672376dfb8d020e32afa7249763bcd924a", "tree": "3f2b95a1d4a4da76d85d5bf32534fa3d15a82eac", "parents": [ "c39a7f84d7845aa95d1c7c168f38215aedcc13c2" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jan 06 11:14:25 2009 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Jan 06 11:14:25 2009 -0500" }, "message": "ext4: Remove code to create the journal inode\n\nThis code has been obsolete in quite some time, since the supported\nmethod for adding a journal inode is to use tune2fs (or to creating\nnew filesystem with a journal via mke2fs or mkfs.ext4).\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "c39a7f84d7845aa95d1c7c168f38215aedcc13c2", "tree": "3e9d741df74eef7e6438dfd9a7ab5a32dd5a5501", "parents": [ "6b082b531228c43d454c082fc0f969da1695b060" ], "author": { "name": "Toshiyuki Okajima", "email": "toshi.okajima@jp.fujitsu.com", "time": "Mon Jan 05 22:38:48 2009 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 05 22:38:48 2009 -0500" }, "message": "ext4: provide function to release metadata pages under memory pressure\n\nPages in the page cache belonging to ext4 data files are released via\nthe ext4_releasepage() function specified in the ext4 inode\u0027s\naddress_space_ops. However, metadata blocks (such as indirect blocks,\ndirectory blocks, etc) are managed via the block device\naddress_space_ops, and they can not be released by\ntry_to_free_buffers() if they have a journal head attached to them.\n\nTo address this, we supply a release_metadata function which calls\njbd2_journal_try_to_free_buffers() function to free the metadata, and\nwhich is called by the block device\u0027s blkdev_releasepage() function.\n\nSigned-off-by: Toshiyuki Okajima \u003ctoshi.okajima@jp.fujitsu.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nCc: linux-fsdevel@vger.kernel.org\n" }, { "commit": "560671a0d3c9ad2d647fa6d09375a262e1f19c4f", "tree": "a52673326726062d53b35643d51a16739cd804fc", "parents": [ "e8134b27e351e813414da3b95aa8eac6d3908088" ], "author": { "name": "Aneesh Kumar K.V", "email": "aneesh.kumar@linux.vnet.ibm.com", "time": "Mon Jan 05 22:20:24 2009 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 05 22:20:24 2009 -0500" }, "message": "ext4: Use high 16 bits of the block group descriptor\u0027s free counts fields\n\nRename the lower bits with suffix _lo and add helper\nto access the values. Also rename bg_itable_unused_hi\nto bg_pad as in e2fsprogs.\n\nSigned-off-by: Aneesh Kumar K.V \u003caneesh.kumar@linux.vnet.ibm.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "5d1b1b3f492f8696ea18950a454a141381b0f926", "tree": "e6277cd3e01c074403b9da7390de1daa6b9f248f", "parents": [ "b7be019e80da4db96d283734d55366014509911c" ], "author": { "name": "Aneesh Kumar K.V", "email": "aneesh.kumar@linux.vnet.ibm.com", "time": "Mon Jan 05 22:19:52 2009 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 05 22:19:52 2009 -0500" }, "message": "ext4: fix BUG when calling ext4_error with locked block group\n\nThe mballoc code likes to call ext4_error while it is holding locked\nblock groups. This can causes a scheduling in atomic context BUG. We\ncan\u0027t just unlock the block group and relock it after/if ext4_error\nreturns since that might result in race conditions in the case where\nthe filesystem is set to continue after finding errors.\n\nSigned-off-by: Aneesh Kumar K.V \u003caneesh.kumar@linux.vnet.ibm.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "b3a6ffe16b5cc48abe7db8d04882dc45280eb693", "tree": "7bd0860ca93beb9aa8c5cb54a3081617d8d12de9", "parents": [ "3c18ce71af754cefae75103dbae28817e04b2db4" ], "author": { "name": "Jens Axboe", "email": "jens.axboe@oracle.com", "time": "Fri Dec 12 09:51:16 2008 +0100" }, "committer": { "name": "Jens Axboe", "email": "jens.axboe@oracle.com", "time": "Mon Dec 29 08:29:51 2008 +0100" }, "message": "Get rid of CONFIG_LSF\n\nWe have two seperate config entries for large devices/files. One\nis CONFIG_LBD that guards just the devices, the other is CONFIG_LSF\nthat handles large files. This doesn\u0027t make a lot of sense, you typically\nwant both or none. So get rid of CONFIG_LSF and change CONFIG_LBD wording\nto indicate that it covers both.\n\nAcked-by: Jean Delvare \u003ckhali@linux-fr.org\u003e\nSigned-off-by: Jens Axboe \u003cjens.axboe@oracle.com\u003e\n" }, { "commit": "3a06d778dfeda7eaeeb79bfa49cf97f2aae132b4", "tree": "08c813063950404356c9c64678eed72f21f217b9", "parents": [ "1a0d3786dd57dbd74f340322054c3d618b999dcf" ], "author": { "name": "Aneesh Kumar K.V", "email": "aneesh.kumar@linux.vnet.ibm.com", "time": "Sat Nov 22 15:04:59 2008 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Nov 22 15:04:59 2008 -0500" }, "message": "ext4: sparse fixes\n\n* Change EXT4_HAS_*_FEATURE to return a boolean\n* Add a function prototype for ext4_fiemap() in ext4.h\n* Make ext4_ext_fiemap_cb() and ext4_xattr_fiemap() be static functions\n* Add lock annotations to mb_free_blocks()\n\nSigned-off-by: Aneesh Kumar K.V \u003caneesh.kumar@linux.vnet.ibm.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "a9df9a49102f3578909cba7bd33784eb3b9caaa4", "tree": "1d383d422bf7185e8e87c1bcfc80f9beb3074cf8", "parents": [ "cde6436004ad9cd8cab5a874b6fa8b01f1da91bf" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 05 22:18:16 2009 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 05 22:18:16 2009 -0500" }, "message": "ext4: Make ext4_group_t be an unsigned int\n\nNearly all places in the ext3/4 code which uses \"unsigned long\" is\nprobably a bug, since on 32-bit systems a ulong a 32-bits, which means\nwe are wasting stack space on 64-bit systems.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "30773840c19cea60dcef39545960d541b1ac1cf8", "tree": "f220a2dce451a40dc7264e8fd70c77c5a3908873", "parents": [ "d7cfa4684d82f58e5d7cb73b8a3c88c169937f25" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Jan 03 20:27:38 2009 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sat Jan 03 20:27:38 2009 -0500" }, "message": "ext4: add fsync batch tuning knobs\n\nAdd new mount options, min_batch_time and max_batch_time, which\ncontrols how long the jbd2 layer should wait for additional filesystem\noperations to get batched with a synchronous write transaction.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "fde4d95ad8711c84a36735a17136c45b19746af9", "tree": "e4d4dcaeb18083be204ba8fe55a75400ded699ae", "parents": [ "fd98496f467b3d26d05ab1498f41718b5ef13de5" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 05 22:17:35 2009 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 05 22:17:35 2009 -0500" }, "message": "ext4: remove extraneous newlines from calls to ext4_error() and ext4_warning()\n\nThis removes annoying blank syslog entries emitted by ext4_error() or\next4_warning(), since these functions add their own newline.\n\nSigned-off-by: Nick Warne \u003cnick@ukfsn.org\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n\n" }, { "commit": "0390131ba84fd3f726f9e24fc4553828125700bb", "tree": "4c90afad4e8690e25aec0ce069fd450e92ab5f96", "parents": [ "ff7ef329b268b603ea4a2303241ef1c3829fd574" ], "author": { "name": "Frank Mayhar", "email": "fmayhar@google.com", "time": "Wed Jan 07 00:06:22 2009 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Jan 07 00:06:22 2009 -0500" }, "message": "ext4: Allow ext4 to run without a journal\n\nA few weeks ago I posted a patch for discussion that allowed ext4 to run\nwithout a journal. Since that time I\u0027ve integrated the excellent\ncomments from Andreas and fixed several serious bugs. We\u0027re currently\nrunning with this patch and generating some performance numbers against\nboth ext2 (with backported reservations code) and ext4 with and without\na journal. It just so happens that running without a journal is\nslightly faster for most everything.\n\nWe did\n\tiozone -T -t 4 s 2g -r 256k -T -I -i0 -i1 -i2\n\nwhich creates 4 threads, each of which create and do reads and writes on\na 2G file, with a buffer size of 256K, using O_DIRECT for all file opens\nto bypass the page cache. Results:\n\n ext2 ext4, default ext4, no journal\n initial writes 13.0 MB/s 15.4 MB/s 15.7 MB/s\n rewrites 13.1 MB/s 15.6 MB/s 15.9 MB/s\n reads 15.2 MB/s 16.9 MB/s 17.2 MB/s\n re-reads 15.3 MB/s 16.9 MB/s 17.2 MB/s\n random readers 5.6 MB/s 5.6 MB/s 5.7 MB/s\n random writers 5.1 MB/s 5.3 MB/s 5.4 MB/s \n\nSo it seems that, so far, this was a useful exercise.\n\nSigned-off-by: Frank Mayhar \u003cfmayhar@google.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "23475e264c4f5c8b635a31924851287ead1ebe32", "tree": "9fd63f363dbea794235eac51b75402d3d0baa46b", "parents": [ "171bbfbeab7730031eec8025341401fabe540bd5" ], "author": { "name": "Roel Kluin", "email": "roel.kluin@gmail.com", "time": "Wed Nov 26 02:23:19 2008 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Wed Nov 26 02:23:19 2008 -0500" }, "message": "ext4: Use simple_strtol() instead of simple_strtoul() in ext4_ui_proc_open\n\nSigned-off-by: Roel Kluin \u003croel.kluin@gmail.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "565a9617b2151e21b22700e97a8b04e70e103153", "tree": "d40db2a54cb27db9dda80b0a47405a6ae19d0fc1", "parents": [ "791b7f08954869d7b8ff438f3dac3cfb39778297" ], "author": { "name": "Aneesh Kumar K.V", "email": "aneesh.kumar@linux.vnet.ibm.com", "time": "Mon Jan 05 21:51:07 2009 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Jan 05 21:51:07 2009 -0500" }, "message": "ext4: avoid ext4_error when mounting a fs with a single bg\n\nRemove some completely unneeded code which which caused an ext4_error\nto be generated when mounting a file system with only a single block\ngroup.\n\nSigned-off-by: Aneesh Kumar K.V \u003caneesh.kumar@linux.vnet.ibm.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nCc: stable@kernel.org\n" }, { "commit": "14ce0cb411c88681ab8f3a4c9caa7f42e97a3184", "tree": "d441a71e13e68cb7651888ced97dbaf90b45b9b5", "parents": [ "d94e99a64c3beece22dbfb2b335771a59184eb0a" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Nov 03 18:10:55 2008 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Nov 03 18:10:55 2008 -0500" }, "message": "ext4: wait on all pending commits in ext4_sync_fs()\n\nIn ext4_sync_fs, we only wait for a commit to finish if we started it,\nbut there may be one already in progress which will not be synced.\n\nIn the case of a data\u003dordered umount with pending long symlinks which\nare delayed due to a long list of other I/O on the backing block\ndevice, this causes the buffer associated with the long symlinks to\nnot be moved to the inode dirty list in the second phase of\nfsync_super. Then, before they can be dirtied again, kjournald exits,\nseeing the UMOUNT flag and the dirty pages are never written to the\nbacking block device, causing long symlink corruption and exposing new\nor previously freed block data to userspace.\n\nTo ensure all commits are synced, we flush all journal commits now\nwhen sync_fs\u0027ing ext4.\n\nSigned-off-by: Arthur Jones \u003cajones@riverbed.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\nCc: Eric Sandeen \u003csandeen@redhat.com\u003e\nCc: \u003clinux-ext4@vger.kernel.org\u003e\n" }, { "commit": "d94e99a64c3beece22dbfb2b335771a59184eb0a", "tree": "cac2a623703f51818c51481f47272e35d0b43215", "parents": [ "ae2d9fb18e575ed37ffc241ece4bf68f0be4ae32" ], "author": { "name": "Aneesh Kumar K.V", "email": "aneesh.kumar@linux.vnet.ibm.com", "time": "Tue Nov 04 09:11:26 2008 -0500" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Nov 04 09:11:26 2008 -0500" }, "message": "ext4: Convert to host order before using the values.\n\nUse le16_to_cpu to read the s_reserved_gdt_blocks values\nfrom super block.\n\nSigned-off-by: Aneesh Kumar K.V \u003caneesh.kumar@linux.vnet.ibm.com\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "f99b25897a86fcfff9140396a97261ae65fed872", "tree": "2191505f190d09ff31896487c73b8187cb475596", "parents": [ "5e1f8c9e20a92743eefc9a82c2db835213905e26" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Oct 28 13:21:44 2008 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Tue Oct 28 13:21:44 2008 -0400" }, "message": "ext4: Add support for non-native signed/unsigned htree hash algorithms\n\nThe original ext3 hash algorithms assumed that variables of type char\nwere signed, as God and K\u0026R intended. Unfortunately, this assumption\nis not true on some architectures. Userspace support for marking\nfilesystems with non-native signed/unsigned chars was added two years\nago, but the kernel-side support was never added (until now).\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "ef2cabf7c6d838eb0ee2b4fb8ef84f7c06ce16d9", "tree": "64c3c14ae4a3717c6c193773d87e31f5facc569e", "parents": [ "44d6f78756560e95903de239e10f8a40a6eae444" ], "author": { "name": "Hidehiro Kawai", "email": "hidehiro.kawai.ez@hitachi.com", "time": "Mon Oct 27 22:53:05 2008 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Mon Oct 27 22:53:05 2008 -0400" }, "message": "ext4: fix a bug accessing freed memory in ext4_abort\n\nVegard Nossum reported a bug which accesses freed memory (found via\nkmemcheck). When journal has been aborted, ext4_put_super() calls\next4_abort() after freeing the journal_t object, and then ext4_abort()\naccesses it. This patch fix it.\n\nSigned-off-by: Hidehiro Kawai \u003chidehiro.kawai.ez@hitachi.com\u003e\nAcked-by: Jan Kara \u003cjack@suse.cz\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "22484856402bfa1ff3defe47f6029ab0418240d9", "tree": "140c67bf59674da350a7b51765d6ff7eb101b597", "parents": [ "5ed487bc2c44ca4e9668ef9cb54c830e2a9fac47", "56b26add02b4bdea81d5e0ebda60db1fe3311ad4" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Oct 23 10:23:07 2008 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Oct 23 10:23:07 2008 -0700" }, "message": "Merge git://git.kernel.org/pub/scm/linux/kernel/git/viro/bdev\n\n* git://git.kernel.org/pub/scm/linux/kernel/git/viro/bdev: (66 commits)\n [PATCH] kill the rest of struct file propagation in block ioctls\n [PATCH] get rid of struct file use in blkdev_ioctl() BLKBSZSET\n [PATCH] get rid of blkdev_locked_ioctl()\n [PATCH] get rid of blkdev_driver_ioctl()\n [PATCH] sanitize blkdev_get() and friends\n [PATCH] remember mode of reiserfs journal\n [PATCH] propagate mode through swsusp_close()\n [PATCH] propagate mode through open_bdev_excl/close_bdev_excl\n [PATCH] pass fmode_t to blkdev_put()\n [PATCH] kill the unused bsize on the send side of /dev/loop\n [PATCH] trim file propagation in block/compat_ioctl.c\n [PATCH] end of methods switch: remove the old ones\n [PATCH] switch sr\n [PATCH] switch sd\n [PATCH] switch ide-scsi\n [PATCH] switch tape_block\n [PATCH] switch dcssblk\n [PATCH] switch dasd\n [PATCH] switch mtd_blkdevs\n [PATCH] switch mmc\n ...\n" }, { "commit": "8264613def2e5c4f12bc3167713090fd172e6055", "tree": "00a8655bce02f97acf559580bdd9ba65919af2bf", "parents": [ "0a0d8a46757e2063433c8cd52b7d654e02b4682b" ], "author": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Sat Aug 02 00:57:06 2008 -0400" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Thu Oct 23 05:12:44 2008 -0400" }, "message": "[PATCH] switch quota_on-related stuff to kern_path()\n\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "9a1c3542768b5a58e45a9216921cd10a3bae1205", "tree": "c20ffda950db868ec7e1e35aed532962de2ecfd9", "parents": [ "511de73ff09034fb89c8d54bed201a10d057328c" ], "author": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Fri Feb 22 20:40:24 2008 -0500" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Tue Oct 21 07:48:58 2008 -0400" }, "message": "[PATCH] pass fmode_t to blkdev_put()\n\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "f287a1a56130be5fdb96a4a62d1290bd064f308e", "tree": "992ac8f5fef83cafae53b8fe00844f2ad3e79d07", "parents": [ "3e624fc72fba09b6f999a9fbb87b64efccd38036" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Thu Oct 16 22:50:48 2008 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Thu Oct 16 22:50:48 2008 -0400" }, "message": "ext4: Remove automatic enabling of the HUGE_FILE feature flag\n\nIf the HUGE_FILE feature flag is not set, don\u0027t allow the creation of\nlarge files, instead of automatically enabling the feature flag.\nRecent versions of mke2fs will set the HUGE_FILE flag automatically\nanyway for ext4 filesystems.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n\n" }, { "commit": "01436ef2e4710317f826c4893b31c07b2d8df88c", "tree": "e8c6a561e3f4803f6ee9ad7851623cd3e369bee9", "parents": [ "0b09923eabd92f11a8b272dd3fd0347332d0e1e2" ], "author": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Oct 17 07:22:35 2008 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Oct 17 07:22:35 2008 -0400" }, "message": "ext4: Remove unused mount options: nomballoc, mballoc, nocheck\n\nThese mount options don\u0027t actually do anything any more, so remove\nthem.\n\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "5128273a326679970b9196a27ff812670927c1c4", "tree": "f2acecf3bed1af523ca385589579235dd1277995", "parents": [ "22208dedbd7626e5fc4339c417f8d24cc21f79d7" ], "author": { "name": "Eric Sesterhenn", "email": "snakebyte@gmx.de", "time": "Fri Oct 17 09:16:19 2008 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Oct 17 09:16:19 2008 -0400" }, "message": "ext4: Add missing newlines to printk messages\n\nThere are some newlines missing in ext4_check_descriptors, which\ncause the printk level to be printed out when the next printk call\nis made:\n\n[ 778.847265] EXT4-fs: ext4_check_descriptors: Block bitmap for group 0\nnot in group (block 1509949442)!\u003c3\u003eEXT4-fs: group descriptors corrupted!\n[ 802.646630] EXT4-fs: ext4_check_descriptors: Inode bitmap for group 0\nnot in group (block 9043971)!\u003c3\u003eEXT4-fs: group descriptors corrupted!\n\nSigned-off-by: Eric Sesterhenn \u003csnakebyte@gmx.de\u003e\nSigned-off-by: \"Theodore Ts\u0027o\" \u003ctytso@mit.edu\u003e\n" }, { "commit": "c2774d84fd6cab2bfa2a2fae0b1ca8d8ebde48a2", "tree": "1319b98e55968e3223d8f2fb6cd7807cdfd80fe1", "parents": [ "688f05a01983711a4e715b1d6e15a89a89c96a66" ], "author": { "name": "Aneesh Kumar K.V", "email": "aneesh.kumar@linux.vnet.ibm.com", "time": "Fri Oct 10 20:07:20 2008 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Oct 10 20:07:20 2008 -0400" }, "message": "ext4: Do mballoc init before doing filesystem recovery\n\nDuring filesystem recovery we may be doing a truncate\nwhich expects some of the mballoc data structures to\nbe initialized. So do ext4_mb_init before recovery.\n\nSigned-off-by: Aneesh Kumar K.V \u003caneesh.kumar@linux.vnet.ibm.com\u003e\nSigned-off-by: Theodore Ts\u0027o \u003ctytso@mit.edu\u003e\n\n" }, { "commit": "a447c0932445f92ce6f4c1bd020f62c5097a7842", "tree": "bacf05bc7f9764515cdd6f7dc5e2254776b4f160", "parents": [ "54cebc68c81eacac41a21bdfe99dc889d3882c60" ], "author": { "name": "Steven Whitehouse", "email": "swhiteho@redhat.com", "time": "Mon Oct 13 10:46:57 2008 +0100" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Oct 13 10:10:37 2008 -0700" }, "message": "vfs: Use const for kernel parser table\n\nThis is a much better version of a previous patch to make the parser\ntables constant. Rather than changing the typedef, we put the \"const\" in\nall the various places where its required, allowing the __initconst\nexception for nfsroot which was the cause of the previous trouble.\n\nThis was posted for review some time ago and I believe its been in -mm\nsince then.\n\nSigned-off-by: Steven Whitehouse \u003cswhiteho@redhat.com\u003e\nCc: Alexander Viro \u003caviro@redhat.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "3244fcb1ae03362e4aa8cb1a9039fbfd61661859", "tree": "fa46eff0dff3a9a046917bdb0c8ec3b2fef807f4", "parents": [ "5bf5683a33f3584da6eced480967c4f7e11515a8" ], "author": { "name": "Alexander Beregalov", "email": "a.beregalov@gmail.com", "time": "Sun Oct 12 17:27:49 2008 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Sun Oct 12 17:27:49 2008 -0400" }, "message": "ext4: fix build failure without procfs\n\nfs/ext4/super.c: In function \u0027ext4_fill_super\u0027:\nfs/ext4/super.c:2226: error: \u0027ext4_ui_proc_fops\u0027 undeclared (first use\nin this function)\nfs/ext4/super.c:2226: error: (Each undeclared identifier is reported\nonly once\nfs/ext4/super.c:2226: error: for each function it appears in.)\n\nSigned-off-by: Alexander Beregalov \u003ca.beregalov@gmail.com\u003e\nSigned-off-by: Theodore Ts\u0027o \u003ctytso@mit.edu\u003e\n\n" }, { "commit": "5bf5683a33f3584da6eced480967c4f7e11515a8", "tree": "4986ba3932d9f259fa1bc674deff3e35f689b243", "parents": [ "7ad7445f60fe4d46c4c9d2a9463db180d2a3b270" ], "author": { "name": "Hidehiro Kawai", "email": "hidehiro.kawai.ez@hitachi.com", "time": "Fri Oct 10 22:12:43 2008 -0400" }, "committer": { "name": "Theodore Ts\u0027o", "email": "tytso@mit.edu", "time": "Fri Oct 10 22:12:43 2008 -0400" }, "message": "ext4: add an option to control error handling on file data\n\nIf the journal doesn\u0027t abort when it gets an IO error in file data\nblocks, the file data corruption will spread silently. Because\nmost of applications and commands do buffered writes without fsync(),\nthey don\u0027t notice the IO error. It\u0027s scary for mission critical\nsystems. On the other hand, if the journal aborts whenever it gets\nan IO error in file data blocks, the system will easily become\ninoperable. So this patch introduces a filesystem option to\ndetermine whether it aborts the journal or just call printk() when\nit gets an IO error in file data.\n\nIf you mount an ext4 fs with data_err\u003dabort option, it aborts on file\ndata write error. If you mount it with data_err\u003dignore, it doesn\u0027t\nabort, just call printk(). data_err\u003dignore is the default.\n\nHere is the corresponding patch of the ext3 version:\nhttp://kerneltrap.org/mailarchive/linux-kernel/2008/9/9/3239374\n\nSigned-off-by: Hidehiro Kawai \u003chidehiro.kawai.ez@hitachi.com\u003e\nSigned-off-by: Theodore Ts\u0027o \u003ctytso@mit.edu\u003e\n\n" } ], "next": "7ffe1ea8949c75ecffb7a4d988bb881a9fa62fbe" }