)]}' { "log": [ { "commit": "ef286f6fa673cd7fb367e1b145069d8dbfcc6081", "tree": "957760503c1b1a417850db3204d6c010d1ce1a67", "parents": [ "9eb07c259207d048e3ee8be2a77b2a4680b1edd4" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Feb 09 16:34:14 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Feb 10 11:26:09 2010 +1100" }, "message": "md: fix some lockdep issues between md and sysfs.\n\n\u003d\u003d\u003d\u003d\u003d\u003d\nThis fix is related to\n http://bugzilla.kernel.org/show_bug.cgi?id\u003d15142\nbut does not address that exact issue.\n\u003d\u003d\u003d\u003d\u003d\u003d\n\nsysfs does like attributes being removed while they are being accessed\n(i.e. read or written) and waits for the access to complete.\n\nAs accessing some md attributes takes the same lock that is held while\nremoving those attributes a deadlock can occur.\n\nThis patch addresses 3 issues in md that could lead to this deadlock.\n\nTwo relate to calling flush_scheduled_work while the lock is held.\nThis is probably a bad idea in general and as we use schedule_work to\ndelete various sysfs objects it is particularly bad.\n\nIn one case flush_scheduled_work is called from md_alloc (called by\nmd_probe) called from do_md_run which holds the lock. This call is\nonly present to ensure that -\u003egendisk is set. However we can be sure\nthat gendisk is always set (though possibly we couldn\u0027t when that code\nwas originally written. This is because do_md_run is called in three\ndifferent contexts:\n 1/ from md_ioctl. This requires that md_open has succeeded, and it\n fails if -\u003egendisk is not set.\n 2/ from writing a sysfs attribute. This can only happen if the\n mddev has been registered in sysfs which happens in md_alloc\n after -\u003egendisk has been set.\n 3/ from autorun_array which is only called by autorun_devices, which\n checks for -\u003egendisk to be set before calling autorun_array.\nSo the call to md_probe in do_md_run can be removed, and the check on\n-\u003egendisk can also go.\n\n\nIn the other case flush_scheduled_work is being called in do_md_stop,\npurportedly to wait for all md_delayed_delete calls (which delete the\ncomponent rdevs) to complete. However there really isn\u0027t any need to\nwait for them - they have already been disconnected in all important\nways.\n\nThe third issue is that raid5-\u003estop() removes some attribute names\nwhile the lock is held. There is already some infrastructure in place\nto delay attribute removal until after the lock is released (using\nschedule_work). So extend that infrastructure to remove the\nraid5_attrs_group.\n\nThis does not address all lockdep issues related to the sysfs\n\"s_active\" lock. The rest can be address by splitting that lockdep\ncontext between symlinks and non-symlinks which hopefully will happen.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "404e4b43fdd6daa7b4a9f81bc7e4358281d763fa", "tree": "7a013e233db56b7c90cf0857d6c3bc74c19cf07f", "parents": [ "7fb9dadc91948ddd16d1d32e414b5e71ec63b97b" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Dec 30 15:25:23 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Dec 30 15:25:23 2009 +1100" }, "message": "md: allow a resync that is waiting for other resync to complete, to be aborted.\n\nIf two arrays share a device, then they will not both resync at the\nsame time. One will wait for the other to complete.\nWhile waiting, the MD_RECOVERY_INTR flag is not checked so a device\nfailure, which would make the resync pointless, does not cause the\nresync to abort, so the failed device cannot be removed (as it cannot\nbe remove while a resync is happening).\n\nSo add a test for MD_RECOVERY_INTR.\n\nReported-by: Brett Russ \u003cbruss@netezza.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "7fb9dadc91948ddd16d1d32e414b5e71ec63b97b", "tree": "d64379c9b336a2792f1877383bdcdd92e837070b", "parents": [ "a2d79c324ac0c26ae9995a312a7731067a7f01fc" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Dec 30 15:19:08 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Dec 30 15:20:43 2009 +1100" }, "message": "md: remove unnecessary code from do_md_run\n\nSince commit dfc7064500061677720fa26352963c772d3ebe6b,\n-\u003ehot_remove_disks has not removed non-failed devices from\nan array until recovery is no longer possible.\nSo the code in do_md_run to get around the fact that\nmd_check_recovery (which calls -\u003ehot_remove_disks) would\nremove partially-in-sync devices is no longer needed.\n\nSo remove it.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "a2d79c324ac0c26ae9995a312a7731067a7f01fc", "tree": "bf9418f4fe8ab86eaf5519be6f1beb363dc64bda", "parents": [ "0f9552b5dc4fe10da37fa3f4a4ca185d90fa41c9" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Mon Dec 21 18:18:36 2009 -0700" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Dec 30 15:20:31 2009 +1100" }, "message": "md: make recovery started by do_md_run() visible via sync_action\n\nBy default md_do_sync() will perform recovery if no other actions are\nspecified. However, action_show() relies on MD_RECOVERY_RECOVER to be\nset otherwise it returns \u0027idle\u0027. So, add a missing set\nMD_RECOVERY_RECOVER when starting recovery.\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "0f9552b5dc4fe10da37fa3f4a4ca185d90fa41c9", "tree": "14f29af551fc226dc4451f1089d4f08dc2611c0d", "parents": [ "cbd1998377504df005302ac90d49db72a48552a6" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Dec 30 12:08:50 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Dec 30 15:20:12 2009 +1100" }, "message": "md: fix small irregularity with start_ro module parameter\n\nThe start_ro modules parameter can be used to force arrays to be\nstarted in \u0027auto-readonly\u0027 in which they are read-only until the first\nwrite. This ensures that no resync/recovery happens until something\nelse writes to the device. This is important for resume-from-disk\noff an md array.\n\nHowever if an array is started \u0027readonly\u0027 (by writing \u0027readonly\u0027 to\nthe \u0027array_state\u0027 sysfs attribute) we want it to be really \u0027readonly\u0027,\nnot \u0027auto-readonly\u0027.\n\nSo strengthen the condition to only set auto-readonly if the\narray is not already read-only.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "cbd1998377504df005302ac90d49db72a48552a6", "tree": "f5c0d83ebe8534477bd252204da804640fd5413b", "parents": [ "6b7b284958d47b77d06745b36bc7f36dab769d9b" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Dec 30 12:08:49 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Dec 30 12:08:49 2009 +1100" }, "message": "md: Fix unfortunate interaction with evms\n\nevms configures md arrays by:\n open device\n send ioctl\n close device\n\nfor each different ioctl needed.\nSince 2.6.29, the device can disappear after the \u0027close\u0027\nunless a significant configuration has happened to the device.\nThe change made by \"SET_ARRAY_INFO\" can too minor to stop the device\nfrom disappearing, but important enough that losing the change is bad.\n\nSo: make sure SET_ARRAY_INFO sets mddev-\u003ectime, and keep the device\nactive as long as ctime is non-zero (it gets zeroed with lots of other\nthings when the array is stopped).\n\nThis is suitable for -stable kernels since 2.6.29.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nCc: stable@kernel.org" }, { "commit": "7b75c2f8cf6d938b571d3bc3f566f883ab7472c4", "tree": "480a924c730a56dfb06a0bec92b63e9086aa8287", "parents": [ "bc058f65e8c7d83c139692e1c26513d3187dd744" ], "author": { "name": "Joe Perches", "email": "joe@perches.com", "time": "Mon Dec 14 18:01:12 2009 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Dec 15 08:53:33 2009 -0800" }, "message": "drivers/md/md.c: use %pU to print UUIDs\n\nSigned-off-by: Joe Perches \u003cjoe@perches.com\u003e\nCc: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "e7d2860b690d4f3bed6824757c540579638e3d1e", "tree": "84268ee28893256fd6a6a7e1d4474f61dbee74e7", "parents": [ "84c95c9acf088c99d8793d78036b67faa5d0b851" ], "author": { "name": "André Goddard Rosa", "email": "andre.goddard@gmail.com", "time": "Mon Dec 14 18:01:06 2009 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Dec 15 08:53:32 2009 -0800" }, "message": "tree-wide: convert open calls to remove spaces to skip_spaces() lib function\n\nMakes use of skip_spaces() defined in lib/string.c for removing leading\nspaces from strings all over the tree.\n\nIt decreases lib.a code size by 47 bytes and reuses the function tree-wide:\n text data bss dec hex filename\n 64688 584 592 65864 10148 (TOTALS-BEFORE)\n 64641 584 592 65817 10119 (TOTALS-AFTER)\n\nAlso, while at it, if we see (*str \u0026\u0026 isspace(*str)), we can be sure to\nremove the first condition (*str) as the second one (isspace(*str)) also\nevaluates to 0 whenever *str \u003d\u003d 0, making it redundant. In other words,\n\"a char equals zero is never a space\".\n\nJulia Lawall tried the semantic patch (http://coccinelle.lip6.fr) below,\nand found occurrences of this pattern on 3 more files:\n drivers/leds/led-class.c\n drivers/leds/ledtrig-timer.c\n drivers/video/output.c\n\n@@\nexpression str;\n@@\n\n( // ignore skip_spaces cases\nwhile (*str \u0026\u0026 isspace(*str)) { \\(str++;\\|++str;\\) }\n|\n- *str \u0026\u0026\nisspace(*str)\n)\n\nSigned-off-by: André Goddard Rosa \u003candre.goddard@gmail.com\u003e\nCc: Julia Lawall \u003cjulia@diku.dk\u003e\nCc: Martin Schwidefsky \u003cschwidefsky@de.ibm.com\u003e\nCc: Jeff Dike \u003cjdike@addtoit.com\u003e\nCc: Ingo Molnar \u003cmingo@elte.hu\u003e\nCc: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: \"H. Peter Anvin\" \u003chpa@zytor.com\u003e\nCc: Richard Purdie \u003crpurdie@rpsys.net\u003e\nCc: Neil Brown \u003cneilb@suse.de\u003e\nCc: Kyle McMartin \u003ckyle@mcmartin.ca\u003e\nCc: Henrique de Moraes Holschuh \u003chmh@hmh.eng.br\u003e\nCc: David Howells \u003cdhowells@redhat.com\u003e\nCc: \u003clinux-ext4@vger.kernel.org\u003e\nCc: Samuel Ortiz \u003csamuel@sortiz.org\u003e\nCc: Patrick McHardy \u003ckaber@trash.net\u003e\nCc: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "06e3c817b750c131a20e82eed57a17841ea88ed2", "tree": "55da529f662c29da5b5fd202b5ece9fb907aa431", "parents": [ "4e59ca7da05f0d5d3ad40365c502c8b0fd24c7e3" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Sat Dec 12 21:17:12 2009 -0700" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:58:57 2009 +1100" }, "message": "md: add \u0027recovery_start\u0027 per-device sysfs attribute\n\nEnable external metadata arrays to manage rebuild checkpointing via a\nmd/dev-XXX/recovery_start attribute which reflects rdev-\u003erecovery_offset\n\nAlso update resync_start_store to allow \u0027none\u0027 to be written, for\nconsistency.\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e" }, { "commit": "4e59ca7da05f0d5d3ad40365c502c8b0fd24c7e3", "tree": "d5ddc749ec13db16c1ed7a054546c2ea482c0e1e", "parents": [ "93be75ffde6dfd1ad17cc3ff1dbd135bd711baf4" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Sat Dec 12 21:17:06 2009 -0700" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:57:43 2009 +1100" }, "message": "md: rcu_read_lock() walk of mddev-\u003edisks in md_do_sync()\n\nOther walks of this list are either under rcu_read_lock() or the list\nmutation lock (mddev_lock()). This protects against the improbable case of a\ndisk being removed from the array at the start of md_do_sync().\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\n" }, { "commit": "93be75ffde6dfd1ad17cc3ff1dbd135bd711baf4", "tree": "56006efccad176da1b806978faf60d77c817e6ac", "parents": [ "aa98aa31987ad9831711ae71ea2270228ab62532" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:50:06 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:51:41 2009 +1100" }, "message": "md: integrate spares into array at earliest opportunity.\n\nAs v1.x metadata can record that a member of the array is\nnot completely recovered, it make sense to record that a\nspare has become a regular member of the array at the earliest\nopportunity.\nSo remove the tests on \"recovery_offset \u003e 0\" in super_1_sync\nas they really aren\u0027t needed, and schedule a metadata update\nimmediately after adding spares to a degraded array.\n\nThis means that if a crash happens immediately after a recovery\nstarts, the new device will be included in the array and recovery will\ncontinue from wherever it was up to. Previously this didn\u0027t happen\nunless recovery was at least 1/16 of the way through.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "aa98aa31987ad9831711ae71ea2270228ab62532", "tree": "736036691f07fe4b7d18064aaa0ace5d76b73cf6", "parents": [ "93bd89a6d5f268acbdb8d775e40d3a280b07b5bd" ], "author": { "name": "Arnd Bergmann", "email": "arnd@arndb.de", "time": "Mon Dec 14 12:50:05 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:51:41 2009 +1100" }, "message": "md: move compat_ioctl handling into md.c\n\nThe RAID ioctls are only implemented in md.c, so the\nhandling for them should also be moved there from\nfs/compat_ioctl.c.\n\nSigned-off-by: Arnd Bergmann \u003carnd@arndb.de\u003e\nCc: Neil Brown \u003cneilb@suse.de\u003e\nCc: Andre Noll \u003cmaan@systemlinux.org\u003e\nCc: linux-raid@vger.kernel.org\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "0efb9e6191e1d3d34c1db90b829b742bc36d532e", "tree": "5960d97df87a7eeea56d7dbe801259fc43398d5e", "parents": [ "1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:58 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:51:41 2009 +1100" }, "message": "md: add MODULE_DESCRIPTION for all md related modules.\n\nSuggested by Oren Held \u003corenhe@il.ibm.com\u003e\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d", "tree": "7a722ad6f56c61a6173493f1cd44d809c8b1bd8d", "parents": [ "67b8dc4b06b0e97df55fd76e209f34f9a52e820e" ], "author": { "name": "Robert Becker", "email": "Rob.Becker@riverbed.com", "time": "Mon Dec 14 12:49:58 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:51:41 2009 +1100" }, "message": "raid: improve MD/raid10 handling of correctable read errors.\n\nWe\u0027ve noticed severe lasting performance degradation of our raid\narrays when we have drives that yield large amounts of media errors.\nThe raid10 module will queue each failed read for retry, and also\nwill attempt call fix_read_error() to perform the read recovery.\nRead recovery is performed while the array is frozen, so repeated\nrecovery attempts can degrade the performance of the array for\nextended periods of time.\n\nWith this patch I propose adding a per md device max number of\ncorrected read attempts. Each rdev will maintain a count of\nread correction attempts in the rdev-\u003eread_errors field (not\nused currently for raid10). When we enter fix_read_error()\nwe\u0027ll check to see when the last read error occurred, and\ndivide the read error count by 2 for every hour since the\nlast read error. If at that point our read error count\nexceeds the read error threshold, we\u0027ll fail the raid device.\n\nIn addition in this patch I add sysfs nodes (get/set) for\nthe per md max_read_errors attribute, the rdev-\u003eread_errors\nattribute, and added some printk\u0027s to indicate when\nfix_read_error fails to repair an rdev.\n\nFor testing I used debugfs-\u003efail_make_request to inject\nIO errors to the rdev while doing IO to the raid array.\n\nSigned-off-by: Robert Becker \u003cRob.Becker@riverbed.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "43a705076e51c5af21ec4260a35699775ea298f5", "tree": "ff8e161d841c41992dbbcca2a844816411941c3c", "parents": [ "72e02075a33f739e21430262f71da8e82db9dbb3" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:55 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:51:41 2009 +1100" }, "message": "md: support updating bitmap parameters via sysfs.\n\nA new attribute directory \u0027bitmap\u0027 in \u0027md\u0027 is created which\ncontains files for configuring the bitmap.\n\u0027location\u0027 identifies where the bitmap is, either \u0027none\u0027,\nor \u0027file\u0027 or \u0027sector offset from metadata\u0027.\nWriting \u0027location\u0027 can create or remove a bitmap.\nAdding a \u0027file\u0027 bitmap this way is not yet supported.\n\u0027chunksize\u0027 and \u0027time_base\u0027 must be set before \u0027location\u0027\ncan be set.\n\n\u0027chunksize\u0027 can be set before creating a bitmap, but is\ncurrently always over-ridden by the bitmap superblock.\n\n\u0027time_base\u0027 and \u0027backlog\u0027 can be updated at any time.\n\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nReviewed-by: Andre Noll \u003cmaan@systemlinux.org\u003e\n" }, { "commit": "72e02075a33f739e21430262f71da8e82db9dbb3", "tree": "04a87a16751b714fe0fb41f28ccc54af9f820de1", "parents": [ "f6af949c5672115313cc3c976d85b0533f607d7e" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:55 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:51:41 2009 +1100" }, "message": "md: factor out parsing of fixed-point numbers\n\nsafe_delay_store can parse fixed point numbers (for fractions\nof a second). We will want to do that for another sysfs\nfile soon, so factor out the code.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "42a04b5078ce73a32f85762551d5703c5bd646a1", "tree": "3ef384933cd33d000516c292712da9a99e273360", "parents": [ "c3d9714e88c8685cf9bc837c3241fc005f95fb82" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:53 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:51:41 2009 +1100" }, "message": "md: move offset, daemon_sleep and chunksize out of bitmap structure\n\n... and into bitmap_info. These are all configuration parameters\nthat need to be set before the bitmap is created.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "c3d9714e88c8685cf9bc837c3241fc005f95fb82", "tree": "dd11e16ec911983bb7452bb4fb092769ba612e3b", "parents": [ "709ae4879ae33628ded276ce7da8cd5acfec476b" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:52 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:51:41 2009 +1100" }, "message": "md: collect bitmap-specific fields into one structure.\n\nIn preparation for making bitmap fields configurable via sysfs,\nstart tidying up by making a single structure to contain the\nconfiguration fields.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "a2826aa92e2e14db372eda01d333267258944033", "tree": "9cdd3329205bf480a4782705a3db1738e3faae44", "parents": [ "efa593390e70b0e3c39f6b2dca8876b6b1461e41" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:49 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:49 2009 +1100" }, "message": "md: support barrier requests on all personalities.\n\nPreviously barriers were only supported on RAID1. This is because\nother levels requires synchronisation across all devices and so needed\na different approach.\nHere is that approach.\n\nWhen a barrier arrives, we send a zero-length barrier to every active\ndevice. When that completes - and if the original request was not\nempty - we submit the barrier request itself (with the barrier flag\ncleared) and then submit a fresh load of zero length barriers.\n\nThe barrier request itself is asynchronous, but any subsequent\nrequest will block until the barrier completes.\n\nThe reason for clearing the barrier flag is that a barrier request is\nallowed to fail. If we pass a non-empty barrier through a striping\nraid level it is conceivable that part of it could succeed and part\ncould fail. That would be way too hard to deal with.\nSo if the first run of zero length barriers succeed, we assume all is\nsufficiently well that we send the request and ignore errors in the\nsecond run of barriers.\n\nRAID5 needs extra care as write requests may not have been submitted\nto the underlying devices yet. So we flush the stripe cache before\nproceeding with the barrier.\n\nNote that the second set of zero-length barriers are submitted\nimmediately after the original request is submitted. Thus when\na personality finds mddev-\u003ebarrier to be set during make_request,\nit should not return from make_request until the corresponding\nper-device request(s) have been queued.\n\nThat will be done in later patches.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nReviewed-by: Andre Noll \u003cmaan@systemlinux.org\u003e\n" }, { "commit": "efa593390e70b0e3c39f6b2dca8876b6b1461e41", "tree": "99c6071381f14f5ff59130779d988672aa78ee67", "parents": [ "c07b70ad32ed0a5ec9735cafb1aa10b3a2298b7d" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:49 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:49 2009 +1100" }, "message": "md: don\u0027t reset curr_resync_completed after an interrupted resync\n\nIf a resync/recovery/check/repair is interrupted for some reason, it\ncan be useful to know exactly where it got up to.\nSo in that case, do not clear curr_resync_completed.\nInitialise it when starting a resync/recovery/... instead.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "c07b70ad32ed0a5ec9735cafb1aa10b3a2298b7d", "tree": "451d88cd7e44ee8217a294335a04594bd573b828", "parents": [ "7820f9e1dddcfebae2698fb2a245d04ce3aa6e74" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:48 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:48 2009 +1100" }, "message": "md: adjust resync_min usefully when resync aborts.\n\nWhen a \u0027check\u0027 or \u0027repair\u0027 finished we should clear resync_min\nso that a future check/repair will cover the whole array (by default).\nHowever if it is interrupted, we should update resync_min to\nwhere we got up to, so that when the check/repair continues it\njust does the remainder of the array.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "aa5cbd103887011b4830355f88fb055f9ad2d556", "tree": "92ef7c80999c6d0bfc6fef9a9cd3e4a75ee16c06", "parents": [ "f40542532e96dda5506eb76badea322f2ae4731c" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:46 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:46 2009 +1100" }, "message": "md/bitmap: protect against bitmap removal while being updated.\n\nA write intent bitmap can be removed from an array while the\narray is active.\nWhen this happens, all IO is suspended and flushed before the\nbitmap is removed.\nHowever it is possible that bitmap_daemon_work is still running to\nclear old bits from the bitmap. If it is, it can dereference the\nbitmap after it has been freed.\n\nSo introduce a new mutex to protect bitmap_daemon_work and get it\nbefore destroying a bitmap.\n\nThis is suitable for any current -stable kernel.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nCc: stable@kernel.org\n" }, { "commit": "1557d33007f63dd96e5d15f33af389378e5f2e54", "tree": "06d05722b2ba5d2a67532f779fa8a88efe3c88f1", "parents": [ "6ec22f9b037fc0c2e00ddb7023fad279c365324d", "c656ae95d1c5c8ed5763356263ace2d03087efec" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Dec 08 07:38:50 2009 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Dec 08 07:38:50 2009 -0800" }, "message": "Merge git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/sysctl-2.6\n\n* git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/sysctl-2.6: (43 commits)\n security/tomoyo: Remove now unnecessary handling of security_sysctl.\n security/tomoyo: Add a special case to handle accesses through the internal proc mount.\n sysctl: Drop \u0026 in front of every proc_handler.\n sysctl: Remove CTL_NONE and CTL_UNNUMBERED\n sysctl: kill dead ctl_handler definitions.\n sysctl: Remove the last of the generic binary sysctl support\n sysctl net: Remove unused binary sysctl code\n sysctl security/tomoyo: Don\u0027t look at ctl_name\n sysctl arm: Remove binary sysctl support\n sysctl x86: Remove dead binary sysctl support\n sysctl sh: Remove dead binary sysctl support\n sysctl powerpc: Remove dead binary sysctl support\n sysctl ia64: Remove dead binary sysctl support\n sysctl s390: Remove dead sysctl binary support\n sysctl frv: Remove dead binary sysctl support\n sysctl mips/lasat: Remove dead binary sysctl support\n sysctl drivers: Remove dead binary sysctl support\n sysctl crypto: Remove dead binary sysctl support\n sysctl security/keys: Remove dead binary sysctl support\n sysctl kernel: Remove binary sysctl logic\n ...\n" }, { "commit": "6d4561110a3e9fa742aeec6717248a491dfb1878", "tree": "689e2abf19940416ce597ba56ed31026ff59bd21", "parents": [ "86926d0096279b9739ceeff40f68d3c33b9119a9" ], "author": { "name": "Eric W. Biederman", "email": "ebiederm@xmission.com", "time": "Mon Nov 16 03:11:48 2009 -0800" }, "committer": { "name": "Eric W. Biederman", "email": "ebiederm@xmission.com", "time": "Wed Nov 18 08:37:40 2009 -0800" }, "message": "sysctl: Drop \u0026 in front of every proc_handler.\n\nFor consistency drop \u0026 in front of every proc_handler. Explicity\ntaking the address is unnecessary and it prevents optimizations\nlike stubbing the proc_handlers to NULL.\n\nCc: Alexey Dobriyan \u003cadobriyan@gmail.com\u003e\nCc: Ingo Molnar \u003cmingo@elte.hu\u003e\nCc: Joe Perches \u003cjoe@perches.com\u003e\nSigned-off-by: Eric W. Biederman \u003cebiederm@xmission.com\u003e\n" }, { "commit": "bb9074ff58fe745e4f244f76209241909c82ec9c", "tree": "cf6be00ab88b1e315f6b74a896a370440f677599", "parents": [ "4739a9748e1bd7459f22f7e94e7d85710ca83954", "156171c71a0dc4bce12b4408bb1591f8fe32dc1a" ], "author": { "name": "Eric W. Biederman", "email": "ebiederm@xmission.com", "time": "Tue Nov 17 01:01:34 2009 -0800" }, "committer": { "name": "Eric W. Biederman", "email": "ebiederm@xmission.com", "time": "Tue Nov 17 01:01:34 2009 -0800" }, "message": "Merge commit \u0027v2.6.32-rc7\u0027\n\nResolve the conflict between v2.6.32-rc7 where dn_def_dev_handler\ngets a small bug fix and the sysctl tree where I am removing all\nsysctl strategy routines.\n" }, { "commit": "0261cd9f1cb42fa44ece314d27868d83742bdf03", "tree": "95954fb2e1a10ee1b20198b8fbefd7a8392dc896", "parents": [ "5e8651060cea6b44844521ddcac665e2c021f5d8" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Nov 13 17:40:48 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Nov 13 17:40:48 2009 +1100" }, "message": "md: allow v0.91 metadata to record devices as being active but not in-sync.\n\nThis is a combination that didn\u0027t really make sense before.\nHowever when a reshape is converting e.g. raid5 -\u003e raid6, the extra\ndevice is not fully in-sync, but is certainly active and contains\nimportant data.\nSo allow that start to be meaningful and in particular get\nthe \u0027recovery_offset\u0027 value (which is needed for any non-in-sync\nactive device) from the reshape_position.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "894d2491153a9f8270dbed21175d06fde4eba6c7", "tree": "e49698028c4a953f4b31363a0225c7fab28cffc0", "parents": [ "c2a86a67fadd9dddc58f55ce6323c04dde59ebed" ], "author": { "name": "Eric W. Biederman", "email": "ebiederm@xmission.com", "time": "Thu Nov 05 14:34:02 2009 -0800" }, "committer": { "name": "Eric W. Biederman", "email": "ebiederm@xmission.com", "time": "Thu Nov 12 02:04:58 2009 -0800" }, "message": "sysctl drivers: Remove dead binary sysctl support\n\nNow that sys_sysctl is a wrapper around /proc/sys all of\nthe binary sysctl support elsewhere in the tree is\ndead code.\n\nCc: Jens Axboe \u003caxboe@kernel.dk\u003e\nCc: Corey Minyard \u003cminyard@acm.org\u003e\nCc: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\nCc: Matt Mackall \u003cmpm@selenic.com\u003e\nCc: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\nCc: Neil Brown \u003cneilb@suse.de\u003e\nCc: \"James E.J. Bottomley\" \u003cJames.Bottomley@suse.de\u003e\nAcked-by: Clemens Ladisch \u003cclemens@ladisch.de\u003e for drivers/char/hpet.c\nSigned-off-by: Eric W. Biederman \u003cebiederm@xmission.com\u003e\n" }, { "commit": "5e8651060cea6b44844521ddcac665e2c021f5d8", "tree": "56a2a3de85fae3f7e210c54a9cda305b0341c334", "parents": [ "8dee7211467a56b7eb4e4359efb0aa4a72e1b6f3" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Nov 12 12:08:04 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Nov 12 12:08:04 2009 +1100" }, "message": "md: factor out updating of \u0027recovery_offset\u0027.\n\nEach device has its own \u0027recovery_offset\u0027 showing how far\nrecovery has progressed on the device.\nAs the only real significance of this is that fact that it can\nbe stored in the metadata and recovered at restart, and as\nonly 1.x metadata can do this, we were only updating\n\u0027recovery_offset\u0027 to \u0027curr_resync_completed\u0027 when updating\nv1.x metadata.\nBut this is wrong, and we will shortly make limited use of this\nfield in v0.90 metadata.\n\nSo move the update into common code.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "24395a85d8efe6eee477ea35c73d045a8dd7a3a1", "tree": "eeb32daee4f1d44eaae636cfd19cc2c8e8af686a", "parents": [ "b6727b12dd2ffb4a890eb5b13a298230c29ba45d" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Nov 06 14:59:27 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Nov 06 14:59:27 2009 +1100" }, "message": "md: don\u0027t clear endpoint for resync when resync is interrupted.\n\nIf a \u0027sync_max\u0027 has been set (via sysfs), it is wrong to clear it\nuntil a resync (or reshape or recovery ...) actually reached that\npoint.\nSo if a resync is interrupted (e.g. by device failure),\nleave \u0027resync_max\u0027 unchanged.\n\nThis is particularly important for \u0027reshape\u0027 operations that do not\nchange the size of the array. For such operations mdadm needs to\nmonitor the reshape taking rolling backups of the section being\nreshaped. If resync_max gets cleared, the reshape can get ahead of\nmdadm and then the backups that mdadm creates are useless.\n\nThis is suitable for 2.6.31.y stable kernels.\nCc: stable@kernel.org\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "5e5e3e78ed9038b8f7112835d07084eefb9daa47", "tree": "afcefac7c0dbafb71f09d90812eecb2c6e4bc766", "parents": [ "e4424fee1815f996dccd36be44d68ca160ec3e1b" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Oct 16 16:35:30 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Oct 16 16:35:30 2009 +1100" }, "message": "md: Fix handling of raid5 array which is being reshaped to fewer devices.\n\nWhen a raid5 (or raid6) array is being reshaped to have fewer devices,\nconf-\u003eraid_disks is the latter and hence smaller number of devices.\nHowever sometimes we want to use a number which is the total number of\ncurrently required devices - the larger of the \u0027old\u0027 and \u0027new\u0027 sizes.\nBefore we implemented reducing the number of devices, this was always\n\u0027new\u0027 i.e. -\u003eraid_disks.\nNow we need max(raid_disks, previous_raid_disks) in those places.\n\nThis particularly affects assembling an array that was shutdown while\nin the middle of a reshape to fewer devices.\n\nmd.c needs a similar fix when interpreting the md metadata.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "3fa841d7e7266f6fcc1b3885b905f5153ba897d8", "tree": "7afa971a10eddcf52787340ea43fa1e910b5805b", "parents": [ "0da3c6194ec2f32617b272df4505a1cf022faea5" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Sep 23 18:10:29 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Sep 23 18:10:29 2009 +1000" }, "message": "md: report device as congested when suspended\n\nThis should writeback from coming when the device is temporarily\nsuspended.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "0da3c6194ec2f32617b272df4505a1cf022faea5", "tree": "5864b61b8fac2e7477668bdb9a493d2a64d0b3dd", "parents": [ "ee305acef5c7841dc25cc32e84bb94f744e1e9b9" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Sep 23 18:09:45 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Sep 23 18:09:45 2009 +1000" }, "message": "md: Improve name of threads created by md_register_thread\n\nThe management thread for raid4,5,6 arrays are all called\nmdX_raid5, independent of the actual raid level, which is wrong and\ncan be confusion.\n\nSo change md_register_thread to use the name from the personality\nunless no alternate name (like \u0027resync\u0027 or \u0027reshape\u0027) is given.\n\nThis is simpler and more correct.\n\nCc: Jinzc \u003czhenchengjin@gmail.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "a9f326ebf22a0de776815240fb76dabe139397ea", "tree": "4402ba08931cd0663aca077be4d26e66c91869bd", "parents": [ "7fa07729e439a6184bd824746d06a49cca553f15" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Sep 23 18:06:41 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Sep 23 18:06:41 2009 +1000" }, "message": "md: remove sparse waring \"symbol xxx shadows an earlier one\"\n\nRename some variable and remove some duplicate definitions\nto avoid there warnings. None of them are actual errors.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "83d5cde47dedf01b6a4a4331882cbc0a7eea3c2e", "tree": "f8ba5e263717d35cd444fcc65898d2ed352af1ae", "parents": [ "7b021967c5e1463936042c8da72b550d3cabe9ac" ], "author": { "name": "Alexey Dobriyan", "email": "adobriyan@gmail.com", "time": "Mon Sep 21 17:01:13 2009 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Sep 22 07:17:25 2009 -0700" }, "message": "const: make block_device_operations 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": "80ffb3cceaefa405f2ecd46d66500ed8d53efe74", "tree": "867d6ec951663255076ea42fab29a31eac4e51c0", "parents": [ "4d484a4a7a5126410eed5f8dd329a33f6eeed068" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Aug 18 10:35:26 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Aug 18 10:35:26 2009 +1000" }, "message": "Fix new incorrect error return from do_md_stop.\n\nRecent commit c8c00a6915a2e3d10416e8bdd3138429beb96210\nchanged the exit paths in do_md_stop and was not quite\ncareful enough. There is one path were \u0027err\u0027 now needs\nto be cleared but it isn\u0027t.\nSo setting an array to readonly (with mdadm --readonly) will\nwork, but will incorrectly report and error: ENXIO.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "4d484a4a7a5126410eed5f8dd329a33f6eeed068", "tree": "9fe49a23117adc2d475711f39a16c1718bab4b7f", "parents": [ "1a67dde0abba36421a1257d01ba9de2f6d1c160a" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Aug 13 10:41:50 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Aug 13 10:41:50 2009 +1000" }, "message": "md: allow upper limit for resync/reshape to be set when array is read-only\n\nNormally we only allow the upper limit for a reshape to be decreased\nwhen the array not performing a sync/recovery/reshape, otherwise there\ncould be races. But if an array is part-way through a reshape when it\nis assembled the reshape is started immediately leaving no window\nto set an upper bound.\n\nIf the array is started read-only, the reshape will be suspended until\nthe array becomes writable, so that provides a window during which it\nis perfectly safe to reduce the upper limit of a reshape.\n\nSo: allow the upper limit (sync_max) to be reduced even if the reshape\nthread is running, as long as the array is still read-only.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "51d5668cb2e3fd1827a55184e48606fff054c5be", "tree": "117824cc3a25c04c939856578105c6c93af6ac8b", "parents": [ "c8c00a6915a2e3d10416e8bdd3138429beb96210" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Aug 13 09:54:02 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Aug 13 09:54:02 2009 +1000" }, "message": "md: never advance \u0027events\u0027 counter by more than 1.\n\nWhen assembling arrays, md allows two devices to have different event\ncounts as long as the difference is only \u00271\u0027. This is to cope with\na system failure between updating the metadata on two difference\ndevices.\n\nHowever there are currently times when we update the event count by\n2. This was done to keep the event count even when the array is clean\nand odd when it is dirty, which allows us to avoid writing common\nupdate to spare devices and so allow those spares to go to sleep.\n\nThis is bad for the above reason. So change it to never increase by\ntwo. This means that the alignment between \u0027odd/even\u0027 and\n\u0027clean/dirty\u0027 might take a little longer to attain, but that is only a\nsmall cost. The spares will get a few more updates but that will\nstill be spared (;-) most updates and can still go to sleep.\n\nPrior to this patch there was a small chance that after a crash an\narray would fail to assemble due to the overly large event count\nmismatch.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "c8c00a6915a2e3d10416e8bdd3138429beb96210", "tree": "ecf06a9e2b08edefe707da450b52a69f818ec7d6", "parents": [ "7b2aa037e878c939676675969983284a02958ae3" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Aug 10 12:50:52 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Aug 10 12:50:52 2009 +1000" }, "message": "Remove deadlock potential in md_open\n\nA recent commit:\n commit 449aad3e25358812c43afc60918c5ad3819488e7\n\nintroduced the possibility of an A-B/B-A deadlock between\nbd_mutex and reconfig_mutex.\n\n__blkdev_get holds bd_mutex while calling md_open which takes\n reconfig_mutex,\ndo_md_run is always called with reconfig_mutex held, and it now\n takes bd_mutex in the call the revalidate_disk.\n\nThis potential deadlock was not caught by lockdep due to the\nuse of mutex_lock_interruptible_nexted which was introduced\nby\n commit d63a5a74dee87883fda6b7d170244acaac5b05e8\ndo avoid a warning of an impossible deadlock.\n\nIt is quite possible to split reconfig_mutex in to two locks.\nOne protects the array data structures while it is being\nreconfigured, the other ensures that an array is never even partially\nopen while it is being deactivated.\nIn particular, the second lock prevents an open from completing\nbetween the time when do_md_stop checks if there are any active opens,\nand the time when the array is either set read-only, or when -\u003epers is\nset to NULL. So we can be certain that no IO is in flight as the\narray is being destroyed.\n\nSo create a new lock, open_mutex, just to ensure exclusion between\n\u0027open\u0027 and \u0027stop\u0027.\n\nThis avoids the deadlock and also avoids the lockdep warning mentioned\nin commit d63a5a74d\n\nReported-by: \"Mike Snitzer\" \u003csnitzer@gmail.com\u003e\nReported-by: \"H. Peter Anvin\" \u003chpa@zytor.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "449aad3e25358812c43afc60918c5ad3819488e7", "tree": "45fab3b82fc1ed06959537a0801319045cf4c102", "parents": [ "64bd660b51b2da92e99a5e97349f6558349f11c5" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Aug 03 10:59:58 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Aug 03 10:59:58 2009 +1000" }, "message": "md: Use revalidate_disk to effect changes in size of device.\n\nAs revalidate_disk calls check_disk_size_change, it will cause\nany capacity change of a gendisk to be propagated to the blockdev\ninode. So use that instead of mucking about with locks and\ni_size_write.\n\nAlso add a call to revalidate_disk in do_md_run and a few other places\nwhere the gendisk capacity is changed.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "70471dafe3390243c598a3165dfb86b8b8b3f4fe", "tree": "febb8dfdbbb981370e1ea046714628bf6b790e5a", "parents": [ "3673f305faf1bc66ead751344f8262ace851ff44" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Aug 03 10:59:57 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Aug 03 10:59:57 2009 +1000" }, "message": "md: Handle growth of v1.x metadata correctly.\n\nThe v1.x metadata does not have a fixed size and can grow\nwhen devices are added.\nIf it grows enough to require an extra sector of storage,\nwe need to update the \u0027sb_size\u0027 to match.\n\nWithout this, md can write out an incomplete superblock with a\nbad checksum, which will be rejected when trying to re-assemble\nthe array.\n\nCc: stable@kernel.org\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "3673f305faf1bc66ead751344f8262ace851ff44", "tree": "4cbdd23d9af20632678e95b3e8f02ede241a3917", "parents": [ "3a981b03f38dc3b8a69b77cbc679e66c1318a44a" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Aug 03 10:59:56 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Aug 03 10:59:56 2009 +1000" }, "message": "md: avoid array overflow with bad v1.x metadata\n\nWe trust the \u0027desc_nr\u0027 field in v1.x metadata enough to use it\nas an index in an array. This isn\u0027t really safe.\nSo range-check the value first.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "3a981b03f38dc3b8a69b77cbc679e66c1318a44a", "tree": "7f8b0747385a02c793edd7df30d34c4c9c95b1a5", "parents": [ "ac5e7113e74872928844d00085bd47c988f12728" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Aug 03 10:59:55 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Aug 03 10:59:55 2009 +1000" }, "message": "md: when a level change reduces the number of devices, remove the excess.\n\nWhen an array is changed from RAID6 to RAID5, fewer drives are\nneeded. So any device that is made superfluous by the level\nconversion must be marked as not-active.\nFor the RAID6-\u003eRAID5 conversion, this will be a drive which only\nhas \u0027Q\u0027 blocks on it.\n\nCc: stable@kernel.org\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "ac5e7113e74872928844d00085bd47c988f12728", "tree": "dabce6a99c2af9f00b33660f6b2d906cce836764", "parents": [ "95fc17aac45300f45968aacd97a536ddd8db8101" ], "author": { "name": "Andre Noll", "email": "maan@systemlinux.org", "time": "Mon Aug 03 10:59:47 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Aug 03 10:59:47 2009 +1000" }, "message": "md: Push down data integrity code to personalities.\n\nThis patch replaces md_integrity_check() by two new public functions:\nmd_integrity_register() and md_integrity_add_rdev() which are both\npersonality-independent.\n\nmd_integrity_register() is called from the -\u003erun and -\u003ehot_remove\nmethods of all personalities that support data integrity. The\nfunction iterates over the component devices of the array and\ndetermines if all active devices are integrity capable and if their\nprofiles match. If this is the case, the common profile is registered\nfor the mddev via blk_integrity_register().\n\nThe second new function, md_integrity_add_rdev() is called from the\n-\u003ehot_add_disk methods, i.e. whenever a new device is being added\nto a raid array. If the new device does not support data integrity,\nor has a profile different from the one already registered, data\nintegrity for the mddev is disabled.\n\nFor raid0 and linear, only the call to md_integrity_register() from\nthe -\u003erun method is necessary.\n\nSigned-off-by: Andre Noll \u003cmaan@systemlinux.org\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "ad361c9884e809340f6daca80d56a9e9c871690a", "tree": "7ec02c9934964fecdc791a0df0fc722d3bda5c53", "parents": [ "e3288775ff63900fbb7db505f2b9a1bee98f07df" ], "author": { "name": "Joe Perches", "email": "joe@perches.com", "time": "Mon Jul 06 13:05:40 2009 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Wed Jul 08 10:30:03 2009 -0700" }, "message": "Remove multiple KERN_ prefixes from printk formats\n\nCommit 5fd29d6ccbc98884569d6f3105aeca70858b3e0f (\"printk: clean up\nhandling of log-levels and newlines\") changed printk semantics. printk\nlines with multiple KERN_\u003clevel\u003e prefixes are no longer emitted as\nbefore the patch.\n\n\u003clevel\u003e is now included in the output on each additional use.\n\nRemove all uses of multiple KERN_\u003clevel\u003es in formats.\n\nSigned-off-by: Joe Perches \u003cjoe@perches.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "e62e58a5ffdc98ac28d8dbd070c857620d541f99", "tree": "0ec3471f4e66e3a376ac8cb2da79d6123e7aa2cf", "parents": [ "a5c308d4d1659b1f4833b863394e3e24cdbdfc6e" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Jul 01 13:15:35 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Jul 01 13:15:35 2009 +1000" }, "message": "md: use interruptible wait when duration is controlled by userspace.\n\nUser space can set various limits on an md array so that resync waits\nwhen it gets to a certain point, or so that I/O is blocked for a short\nwhile.\nWhen md is waiting against one of these limit, it should use an\ninterruptible wait so as not to add to the load average, and so are\nnot to trigger a warning if the wait goes on for too long.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "0909dc448c98ed5021c87ffdfc09fb473aa464ab", "tree": "17c48d146c0f9eb7367a0d0feafea29838eae8eb", "parents": [ "1ec22eb2b4a2e1a763106bce36b11c02eaa84e61" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Jul 01 12:27:21 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Jul 01 12:27:21 2009 +1000" }, "message": "md: tidy up error paths in md_alloc\n\nAs the recent bug in md_alloc showed, having a single exit path for\nunlocking and putting is a good idea. So restructure md_alloc to have\na single mutex_unlock and mddev_put, and use gotos where necessary.\n\nFound-by: Jiri Slaby \u003cjirislaby@gmail.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "1ec22eb2b4a2e1a763106bce36b11c02eaa84e61", "tree": "2aa6e6539342a28263417f6a2f2551d541e9ead9", "parents": [ "b8d966efd9a46a9a35beac50cbff6e30565125ef" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Jul 01 12:27:21 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Jul 01 12:27:21 2009 +1000" }, "message": "md: fix error path when duplicate name is found on md device creation.\n\nWhen an md device is created by name (rather than number) we need to\ncheck that the name is not already in use. If this check finds a\nduplicate, we return an error without dropping the lock or freeing\nthe newly create mddev.\nThis patch fixes that.\n\nCc: stable@kernel.org\nFound-by: Jiri Slaby \u003cjirislaby@gmail.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "b8d966efd9a46a9a35beac50cbff6e30565125ef", "tree": "d1c59125e8ee9677e8594bdc4ab223e692a87e50", "parents": [ "8f6c2e4b325a8e9f8f47febb2fd0ed4fae7d45a9" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Jul 01 11:14:04 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Jul 01 11:14:04 2009 +1000" }, "message": "md: avoid dereferencing NULL pointer when accessing suspend_* sysfs attributes.\n\nIf we try to modify one of the md/ sysfs files\n suspend_lo or suspend_hi\nwhen the array is not active, we dereference a NULL.\nProtect against that.\n\nCc: stable@kernel.org\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "0894cc3066aaa3e75a99383c0d25feebf9b688ac", "tree": "651664e6b288e36dc9553443e334e650139851c8", "parents": [ "8190e754e0723de7cecb80bdd9eb93911dfa04a1" ], "author": { "name": "Andre Noll", "email": "maan@systemlinux.org", "time": "Thu Jun 18 08:49:23 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Jun 18 08:49:23 2009 +1000" }, "message": "md: Move check for bitmap presence to personality code.\n\nIf the superblock of a component device indicates the presence of a\nbitmap but the corresponding raid personality does not support bitmaps\n(raid0, linear, multipath, faulty), then something is seriously wrong\nand we\u0027d better refuse to run such an array.\n\nCurrently, this check is performed while the superblocks are examined,\ni.e. before entering personality code. Therefore the generic md layer\nmust know which raid levels support bitmaps and which do not.\n\nThis patch avoids this layer violation without adding identical code\nto various personalities. This is accomplished by introducing a new\npublic function to md.c, md_check_no_bitmap(), which replaces the\nhard-coded checks in the superblock loading functions.\n\nA call to md_check_no_bitmap() is added to the -\u003erun method of each\npersonality which does not support bitmaps and assembly is aborted\nif at least one component device contains a bitmap.\n\nSigned-off-by: Andre Noll \u003cmaan@systemlinux.org\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "8190e754e0723de7cecb80bdd9eb93911dfa04a1", "tree": "6fbd0edd64cb767b9421103301e198804c3aa40b", "parents": [ "13f2682b7216ebebd72b3d5868fe7fccec91a92d" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Jun 18 08:48:58 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Jun 18 08:48:58 2009 +1000" }, "message": "md: remove chunksize rounding from common code.\n\nIt is easiest to round sizes to multiples of chunk size in\nthe personality code for those personalities which care.\nThose personalities now do the rounding, so we can\nremove that function from common code.\n\nAlso remove the upper bound on the size of a chunk, and the lower\nbound on the size of a device (1 chunk), neither of which really buy\nus anything.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "1b57f132231593923cb4ab99943ddd777e8745bc", "tree": "b76f936d08e5ef72430c6fbcf9352f53721481ec", "parents": [ "8c6ac868b107ed50a46204f6d14e2ad9443ff146" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Jun 18 08:48:19 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Jun 18 08:48:19 2009 +1000" }, "message": "md: move assignment of -\u003eutime so that it never gets skipped.\n\nCurrently the assignment to utime gets skipped for \u0027external\u0027\nmetadata. So move it to the top of the function so that it\nalways gets effected.\nThis is of largely cosmetic interest. Nothing actually depends\non -\u003eutime being right for external arrays.\n\"mdadm --monitor\" does use it for 0.90 and 1.x arrays, but with\nmdadm-3.0, this is not important for external metadata.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "8c6ac868b107ed50a46204f6d14e2ad9443ff146", "tree": "a0690ce92ed1993cc3211448948f3964c389c082", "parents": [ "50ac168a6e0a061bf5346d53aa9e7beb94c97527" ], "author": { "name": "Andre Noll", "email": "maan@systemlinux.org", "time": "Thu Jun 18 08:48:06 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Jun 18 08:48:06 2009 +1000" }, "message": "md: Push down reconstruction log message to personality code.\n\nCurrently, the md layer checks in analyze_sbs() if the raid level\nsupports reconstruction (mddev-\u003elevel \u003e\u003d 1) and if reconstruction is\nin progress (mddev-\u003erecovery_cp !\u003d MaxSector).\n\nMove that printk into the personality code of those raid levels that\ncare (levels 1, 4, 5, 6, 10).\n\nSigned-off-by: Andre Noll \u003cmaan@systemlinux.org\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "50ac168a6e0a061bf5346d53aa9e7beb94c97527", "tree": "4f1eff67793bd8349a1995c921a63e9512be7818", "parents": [ "597a711b69cfff95c4b8f6069037e7ad3fc71f56" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Jun 18 08:47:55 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Jun 18 08:47:55 2009 +1000" }, "message": "md: merge reconfig and check_reshape methods.\n\nThe difference between these two methods is artificial.\nBoth check that a pending reshape is valid, and perform any\naspect of it that can be done immediately.\n\u0027reconfig\u0027 handles chunk size and layout.\n\u0027check_reshape\u0027 handles raid_disks.\n\nSo make them just one method.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "597a711b69cfff95c4b8f6069037e7ad3fc71f56", "tree": "8c2cfa4c1223827a560de2f14da426d4822151c4", "parents": [ "01ee22b496c41384eaa6dcae983c86d8bc32fbb8" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Jun 18 08:47:42 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Jun 18 08:47:42 2009 +1000" }, "message": "md: remove unnecessary arguments from -\u003ereconfig method.\n\nPassing the new layout and chunksize as args is not necessary as\nthe mddev has fields for new_check and new_layout.\n\nThis is preparation for combining the check_reshape and reconfig\nmethods\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "664e7c413f1e90eceb0b2596dd73a0832faec058", "tree": "72ea827a0f2a493766d3ea1fd14909c756aa4496", "parents": [ "9d8f0363623b3da12c43007cf77f5e1a4e8a5964" ], "author": { "name": "Andre Noll", "email": "maan@systemlinux.org", "time": "Thu Jun 18 08:45:27 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Jun 18 08:45:27 2009 +1000" }, "message": "md: Convert mddev-\u003enew_chunk to sectors.\n\nA straight-forward conversion which gets rid of some\nmultiplications/divisions/shifts. The patch also introduces a couple\nof new ones, most of which are due to conf-\u003echunk_size still being\nrepresented in bytes. This will be cleaned up in subsequent patches.\n\nSigned-off-by: Andre Noll \u003cmaan@systemlinux.org\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "9d8f0363623b3da12c43007cf77f5e1a4e8a5964", "tree": "0fee53971a397ade209dd36c4f1ed50db6450faf", "parents": [ "fbb704efb784e2c8418e34dc3013af76bdd58101" ], "author": { "name": "Andre Noll", "email": "maan@systemlinux.org", "time": "Thu Jun 18 08:45:01 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Jun 18 08:45:01 2009 +1000" }, "message": "md: Make mddev-\u003echunk_size sector-based.\n\nThis patch renames the chunk_size field to chunk_sectors with the\nimplied change of semantics. Since\n\n\tis_power_of_2(chunk_size) \u003d is_power_of_2(chunk_sectors \u003c\u003c 9)\n\t\t\t\t \u003d is_power_of_2(chunk_sectors)\n\nthese bits don\u0027t need an adjustment for the shift.\n\nSigned-off-by: Andre Noll \u003cmaan@systemlinux.org\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "2ac06c3332898103210b478c5a17c20e28929287", "tree": "6f34315bbdcc8a8300ab2ab5edcd4cb96150e583", "parents": [ "740da44918680a0c72411ae4ccdd1861069afcc4" ], "author": { "name": "raz ben yehuda", "email": "raziebe@gmail.com", "time": "Tue Jun 16 17:01:42 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Jun 16 17:01:42 2009 +1000" }, "message": "md: prepare for non-power-of-two chunk sizes\n\nRemove chunk size check from md as this is now performed in the run\nfunction in each personality.\n\nReplace chunk size power 2 code calculations by a regular division.\n\nSigned-off-by: raziebe@gmail.com\nSigned-off-by: NeilBrown \u003cneilb@suse.de\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": "b492b852cd8c99505708152c29a5e09a787af9de", "tree": "f26aa9676231a583e209a9397acfc4512061325e", "parents": [ "7a91ee1f628ef6bfe3f13067c0ddf9db520cb86b" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 26 12:57:36 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 26 12:57:36 2009 +1000" }, "message": "md: don\u0027t use locked_ioctl.\n\nmd has no need for the BKL - it does its own locking.\nSo md_ioctl doesn\u0027t need to be a locked_ioctl.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "7a91ee1f628ef6bfe3f13067c0ddf9db520cb86b", "tree": "b6b317a2dfb067784fccae113001cb3957e25337", "parents": [ "848b3182365fdf5a05bcd5ed949071cac2c894b3" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 26 12:57:21 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 26 12:57:21 2009 +1000" }, "message": "md: don\u0027t update curr_resync_completed without also updating reshape_position.\n\nIn order for the metadata to always be consistent, we mustn\u0027t updated\ncurr_resync_completed without also updating reshape_position.\n\nThe reshape code updates both at the same time. However since\ncommit 97e4f42d62badb0f9fbc27c013e89bc1336a03bc\nthe common md_do_sync will sometimes update curr_resync_completed\nbut is not in a position to update reshape_position.\nSo if MD_RECOVERY_RESHAPE is set (indicating that a reshape is\nhappening, so reshape_position might change), don\u0027t update\ncurr_resync_completed in md_do_sync, leave it to the per-personality\nreshape code.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "b6a9ce688f613e2ee5f15e6720e0bb8520efc36e", "tree": "7fc4c8ab5ea14df5e544e740ec3154b707766a08", "parents": [ "be512691036cc989c11d0f418187efbbf14468e6" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 26 09:41:17 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 26 09:41:17 2009 +1000" }, "message": "md: export \u0027frozen\u0027 resync state through sysfs\n\nThe md resync engine has a \u0027frozen\u0027 state which ensures that\nno resync/recovery. This is used to avoid races.\n\nExport this state through the \u0027sync_action\u0027 sysfs attribute\nso that user-space can benefit and also avoid some races.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "2b69c83924396ad1eda36fdd267c9d2f360f5555", "tree": "14c01b6dd6b596859835b3f0d176bf02129d2c45", "parents": [ "62e1e389f87a8839ad83b08c44691d1df8320846" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 26 09:41:17 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 26 09:41:17 2009 +1000" }, "message": "md: improve errno return when setting array_size\n\nInstead of always returns EINVAL if anything goes wrong\nwhen setting the array size, add the option of\n E2BIG\nif the size requested is too large. This makes it easier\nfor user-space to be sure what went wrong.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "62e1e389f87a8839ad83b08c44691d1df8320846", "tree": "d8915df95d7164188334052b31ffe7ac40aa4e94", "parents": [ "59a3759d0fe8d969888c741bb33f4946e4d3750d" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 26 09:40:59 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 26 09:40:59 2009 +1000" }, "message": "md: always update level / chunk_size / layout when writing v1.x metadata.\n\nWe previously didn\u0027t update these fields when writing the metadata\nbecause they could never change. They can now, so we better write\nthem.\nv0.90 metadata always updated these fields.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\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": "c4647292fda0833bebe45be27f04453b736981fa", "tree": "85c89a4161b06b1c591a76c2a68ff51fc02ff6f4", "parents": [ "5bf295975416f8e97117bbbcfb0191c00bc3e2b4" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu May 07 12:51:06 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu May 07 12:51:06 2009 +1000" }, "message": "md: remove rd%d links immediately after stopping an array.\n\nmd maintains link in sys/mdXX/md/ to identify which device has\nwhich role in the array. e.g.\n rd2 -\u003e dev-sda\n\nindicates that the device with role \u00272\u0027 in the array is sda.\n\nThese links are only present when the array is active. They are\ncreated immediately after -\u003erun is called, and so should be removed\nimmediately after -\u003estop is called.\nHowever they are currently removed a little bit later, and it is\npossible for -\u003erun to be called again, thus adding these links, before\nthey are removed.\n\nSo move the removal earlier so they are consistently only present when\nthe array is active.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "5bf295975416f8e97117bbbcfb0191c00bc3e2b4", "tree": "9d7ddfe9d4632c8d6cacb6c4dd7b9cb49f837432", "parents": [ "110518bccf076726cc93bf604527d8019aae50ba" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu May 07 12:50:57 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu May 07 12:50:57 2009 +1000" }, "message": "md: remove ability to explicit set an inactive array to \u0027clean\u0027.\n\nBeing able to write \u0027clean\u0027 to an \u0027array_state\u0027 of an inactive array\nto activate it in \u0027clean\u0027 mode is both unnecessary and inconvenient.\n\nIt is unnecessary because the same can be achieved by writing\n\u0027active\u0027. This activates and array, but it still remains \u0027clean\u0027\nuntil the first write.\n\nIt is inconvenient because writing \u0027clean\u0027 is more often used to\ncause an \u0027active\u0027 array to revert to \u0027clean\u0027 mode (thus blocking\nany writes until a \u0027write-pending\u0027 is promoted to \u0027active\u0027).\n\nAllowing \u0027clean\u0027 to both activate an array and mark an active array as\nclean can lead to races: One program writes \u0027clean\u0027 to mark the\nactive array as clean at the same time as another program writes\n\u0027inactive\u0027 to deactivate (stop) and active array. Depending on which\nwrites first, the array could be deactivated and immediately\nreactivated which isn\u0027t what was desired.\n\nSo just disable the use of \u0027clean\u0027 to activate an array.\n\nThis avoids a race that can be triggered with mdadm-3.0 and external\nmetadata, so it suitable for -stable.\n\nReported-by: Rafal Marszewski \u003crafal.marszewski@intel.com\u003e\nAcked-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nCc: \u003cstable@kernel.org\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "110518bccf076726cc93bf604527d8019aae50ba", "tree": "f2df7daf983640c64f66bcd76aea475b35f9f1d3", "parents": [ "dd71cf6b2773310b01c6fe6c773064c80fd2476b" ], "author": { "name": "Jan Engelhardt", "email": "jengelh@medozas.de", "time": "Thu May 07 12:49:37 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu May 07 12:49:37 2009 +1000" }, "message": "md: constify VFTs\n\n\nSigned-off-by: Jan Engelhardt \u003cjengelh@medozas.de\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "dd71cf6b2773310b01c6fe6c773064c80fd2476b", "tree": "33a4cc4fe4db45ec4f1a8f477bb294a0b685efa4", "parents": [ "db305e507d554430a69ede901a6308e6ecb72349" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu May 07 12:49:35 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu May 07 12:49:35 2009 +1000" }, "message": "md: tidy up status_resync to handle large arrays.\n\nTwo problems in status_resync.\n1/ It still used Kilobytes as the basic block unit, while most code\n now uses sectors uniformly.\n2/ It doesn\u0027t allow for the possibility that max_sectors exceeds\n the range of \"unsigned long\".\n\nSo\n - change \"max_blocks\" to \"max_sectors\", and store sector numbers\n in there and in \u0027resync\u0027\n - Make \u0027rt\u0027 a \u0027sector_t\u0027 so it can temporarily hold the number of\n remaining sectors.\n - use sector_div rather than normal division.\n - change the magic \u0027100\u0027 used to preserve precision to \u002732\u0027.\n + making it a power of 2 makes division easier\n + it doesn\u0027t need to be as large as it was chosen when we averaged\n speed over the entire run. Now we average speed over the last 30\n seconds or so.\n\nReported-by: \"Mario \u0027BitKoenig\u0027 Holbe\" \u003cMario.Holbe@TU-Ilmenau.DE\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "c03f6a19699fce4389888a45db8245969311d868", "tree": "2a3be3033d5fad42f25fe2678e98efcf6abb04bc", "parents": [ "acb180b0e335ad88acfed6c8a33e39c05b95dc49" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Apr 17 11:06:30 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Apr 17 11:06:30 2009 +1000" }, "message": "md: update sync_completed and reshape_position even more often.\n\nThere are circumstances when a user-space process might need to\n\"oversee\" a resync/reshape process. For example when doing an\nin-place reshape of a raid5, it is prudent to take a backup of each\nsection before reshaping it as this is the only way to provide\nsafety against an unplanned shutdown (i.e. crash/power failure).\n\nThe sync_max sysfs value can be used to stop the resync from\nadvancing beyond a particular point.\nSo user-space can:\n suspend IO to the first section and back it up\n set \u0027sync_max\u0027 to the end of the section\n wait for \u0027sync_completed\u0027 to reach that point\n resume IO on the first section and move on to the next section.\n\nHowever this process requires the kernel and user-space to run in\nlock-step which could introduce unnecessary delays.\n\nIt would be better if a \u0027double buffered\u0027 approach could be used with\nuserspace and kernel space working on different sections with the\n\u0027next\u0027 section always ready when the \u0027current\u0027 section is finished.\n\nOne problem with implementing this is that sync_completed is only\nguaranteed to be updated when the sync process reaches sync_max.\n(it is updated on a time basis at other times, but it is hard to rely\non that). This defeats some of the double buffering.\n\nWith this patch, sync_completed (and reshape_position) get updated as\nthe current position approaches sync_max, so there is room for\nuserspace to advance sync_max early without losing updates.\n\nTo be precise, sync_completed is updated when the current sync\nposition reaches half way between the current value of sync_completed\nand the value of sync_max. This will usually be a good time for user\nspace to update sync_max.\n\nIf sync_max does not get updated, the updates to sync_completed\n(together with associated metadata updates) will occur at an\nexponentially increasing frequency which will get unreasonably fast\n(one update every page) immediately before the process hits sync_max\nand stops. So the update rate will be unreasonably fast only for an\ninsignificant period of time.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "acb180b0e335ad88acfed6c8a33e39c05b95dc49", "tree": "fa980978bb66b178fd8c2f474194754139c0921d", "parents": [ "6d56e278444bc8323b1bcfcada126b8e4dbba0f4" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Apr 14 16:28:34 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Apr 14 16:28:34 2009 +1000" }, "message": "md: improve usefulness and accuracy of sysfs file md/sync_completed.\n\nThe sync_completed file reports how much of a resync (or recovery or\nreshape) has been completed.\nHowever due to the possibility of out-of-order completion of writes,\nit is not certain to be accurate.\n\nWe have an internal value - mddev-\u003ecurr_resync_completed - which is an\naccurate value (though it might not always be quite so uptodate).\n\nSo:\n - make curr_resync_completed be uptodate a little more often,\n particularly when raid5 reshape updates status in the metadata\n - report curr_resync_completed in the sysfs file\n - allow poll/select to report all updates to md/sync_completed.\n\nThis makes sync_completed completed usable by any external metadata\nhandler that wants to record this status information in its metadata.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "6d56e278444bc8323b1bcfcada126b8e4dbba0f4", "tree": "4a1e838b3bb46ce0650f08daa4cdf976eb49317e", "parents": [ "63fe08177f92ce21929df8af6361491b98ad12cd" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Apr 14 12:01:57 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Apr 14 12:01:57 2009 +1000" }, "message": "md: allow setting newly added device to \u0027in_sync\u0027 via sysfs.\n\nWhen adding devices to an active array via sysfs, there is currently\nno way to mark a device as \u0027in-sync\u0027 which is useful when\nincrementally assembling an array.\n\nSo add that option.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "223cdea4c4b5af5181b2da00ac85711d1e0c737c", "tree": "dfe7226c70ddabbf2e2e63924ba636345278e79c", "parents": [ "31e6e2dac575c9d21a6ec56ca52ae89086baa705", "c8f517c444e4f9f55b5b5ca202b8404691a35805" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Apr 03 09:08:19 2009 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Apr 03 09:08:19 2009 -0700" }, "message": "Merge branch \u0027for-linus\u0027 of git://neil.brown.name/md\n\n* \u0027for-linus\u0027 of git://neil.brown.name/md: (53 commits)\n md/raid5 revise rules for when to update metadata during reshape\n md/raid5: minor code cleanups in make_request.\n md: remove CONFIG_MD_RAID_RESHAPE config option.\n md/raid5: be more careful about write ordering when reshaping.\n md: don\u0027t display meaningless values in sysfs files resync_start and sync_speed\n md/raid5: allow layout and chunksize to be changed on active array.\n md/raid5: reshape using largest of old and new chunk size\n md/raid5: prepare for allowing reshape to change layout\n md/raid5: prepare for allowing reshape to change chunksize.\n md/raid5: clearly differentiate \u0027before\u0027 and \u0027after\u0027 stripes during reshape.\n Documentation/md.txt update\n md: allow number of drives in raid5 to be reduced\n md/raid5: change reshape-progress measurement to cope with reshaping backwards.\n md: add explicit method to signal the end of a reshape.\n md/raid5: enhance raid5_size to work correctly with negative delta_disks\n md/raid5: drop qd_idx from r6_state\n md/raid6: move raid6 data processing to raid6_pq.ko\n md: raid5 run(): Fix max_degraded for raid level 4.\n md: \u0027array_size\u0027 sysfs attribute\n md: centralize -\u003earray_sectors modifications\n ...\n" }, { "commit": "d1a7c50369835f9ecbd7752016cd9302ecfae678", "tree": "2c6bcc8c5cb4d045d555e0d030321cb887a4e05a", "parents": [ "88ce4930e2b80378d45506ce2c3bb5820e156e85" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 15:24:32 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 15:24:32 2009 +1100" }, "message": "md: don\u0027t display meaningless values in sysfs files resync_start and sync_speed\n\nWhen no resync if happening, both of these files currently have\nmeaningless values (is slightly different ways).\nChange them to \"none\" in that case.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "cea9c22800773cecb1d41f4a6139f9eb6a95368b", "tree": "d070d22390b86768fefb8ba04c64d74993ed28e9", "parents": [ "7ec0547838976d088dfb9cb0adb073e6e8a15aa3" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 15:15:05 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 15:15:05 2009 +1100" }, "message": "md: add explicit method to signal the end of a reshape.\n\nCurrently raid5 (the only module that supports restriping)\nnotices that the reshape has finished be sync_request being\ngiven a large value, and handles any cleanup them.\n\nThis patch changes it so md_check_recovery calls into an\nexplicit finish_reshape method as well.\n\nThe clean-up from sync_request can do things that need to be\ndone promptly, typically things local to the raid5_conf_t\nstructure.\n\nThe \"finish_reshape\" method is called under the mddev_lock\nso it can do things involving reconfiguring the device.\n\nThis allows us to get rid of md_set_array_sectors_locked, which\nwould have caused a deadlock if you tried to stop and array\nwhile a reshape was happening.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "b522adcde9c4d3fb7b579cfa9160d8bde7744be8", "tree": "4208e3dcec3ebdfa6ad9bc153f76129400532717", "parents": [ "1f403624bde3c678a166984b1e6a727a0ce06f2b" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Tue Mar 31 15:00:31 2009 +1100" }, "committer": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Tue Mar 31 15:00:31 2009 +1100" }, "message": "md: \u0027array_size\u0027 sysfs attribute\n\nAllow userspace to set the size of the array according to the following\nsemantics:\n\n1/ size must be \u003c\u003d to the size returned by mddev-\u003epers-\u003esize(mddev, 0, 0)\n a) If size is set before the array is running, do_md_run will fail\n if size is greater than the default size\n b) A reshape attempt that reduces the default size to less than the set\n array size should be blocked\n2/ once userspace sets the size the kernel will not change it\n3/ writing \u0027default\u0027 to this attribute returns control of the size to the\n kernel and reverts to the size reported by the personality\n\nAlso, convert locations that need to know the default size from directly\nreading -\u003earray_sectors to \u003cpers\u003e_size. Resync/reshape operations\nalways follow the default size.\n\nFinally, fixup other locations that read a number of 1k-blocks from\nuserspace to use strict_blocks_to_sectors() which checks for unsigned\nlong long to sector_t overflow and blocks to sectors overflow.\n\nReviewed-by: Andre Noll \u003cmaan@systemlinux.org\u003e\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\n" }, { "commit": "1f403624bde3c678a166984b1e6a727a0ce06f2b", "tree": "b66ed37091e825bcde1cd0d333d4ebba86772805", "parents": [ "80c3a6ce4ba4470379b9e6a4d9bcd9d2ee26ae03" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Tue Mar 31 14:59:03 2009 +1100" }, "committer": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Tue Mar 31 14:59:03 2009 +1100" }, "message": "md: centralize -\u003earray_sectors modifications\n\nGet personalities out of the business of directly modifying\n-\u003earray_sectors. Lays groundwork to introduce policy on when\n-\u003earray_sectors can be modified.\n\nReviewed-by: Andre Noll \u003cmaan@systemlinux.org\u003e\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\n" }, { "commit": "b3546035277847028df650b147469fc943cf5c71", "tree": "87966abc5456a62845326eb8d5a5cf0f88879b2d", "parents": [ "d562b0c4313e3ddea402a400371afa47ddf679f9" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:56:41 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:56:41 2009 +1100" }, "message": "md/raid5: allow layout/chunksize to be changed on an active 2-drive raid5.\n\n2-drive raid5\u0027s aren\u0027t very interesting. But if you are converting\na raid1 into a raid5, you will at least temporarily have one. And\nthat it a good time to set the layout/chunksize for the new RAID5\nif you aren\u0027t happy with the defaults.\n\nlayout and chunksize don\u0027t actually affect the placement of data\non a 2-drive raid5, so we just do some internal book-keeping.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "245f46c2c221ef09c7db892f0e3fc2149be42052", "tree": "be7e6f4b7b65b682c43e59ef17f7ed580bc8a82b", "parents": [ "409c57f3801701dfee27a28103dda4831306cb20" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:39:39 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:39:39 2009 +1100" }, "message": "md: add -\u003etakeover method to support changing the personality managing an array\n\nImplement this for RAID6 to be able to \u0027takeover\u0027 a RAID5 array. The\nnew RAID6 will use a layout which places Q on the last device, and\nthat device will be missing.\nIf there are any available spares, one will immediately have Q\nrecovered onto it.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "409c57f3801701dfee27a28103dda4831306cb20", "tree": "430c8e4ebe879b27250e061dc1a1171b12aaadf0", "parents": [ "e0cf8f045b2023b0b3f919ee93eb94345f648434" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:39:39 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:39:39 2009 +1100" }, "message": "md: enable suspend/resume of md devices.\n\nTo be able to change the \u0027level\u0027 of an md/raid array, we need to\nsuspend the device so that no requests are active - then move some\npointers around etc.\n\nThe code already keeps counts of active requests and the -\u003equiesce\nfunction can be used to wait until those counts hit zero.\nHowever the quiesce function blocks new requests once they are all\nready \u0027inside\u0027 the personality module, and that is too late if we want\nto replace the personality modules.\n\nSo make all md requests come in through a common md_make_request\nfunction that keeps track of how many requests have entered the\nmodules but may not yet be on the internal reference counts.\nAllow md_make_request to be blocked when we want to suspend the\ndevice, and make it possible to wait for all those in-transit requests\nto be added to internal lists so that -\u003equiesce can wait for them.\n\nThere is still a problem that when a request completes, we drop the\nref count inside the personality code so there is a short time between\nwhen the refcount hits zero, and when the personality code is no\nlonger being used.\nThe personality code never blocks (schedule or spinlock) between\ndropping the refcount and exiting the routine, so this should be safe\n(as put_module calls synchronize_sched() before unmapping the module\ncode).\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "e0cf8f045b2023b0b3f919ee93eb94345f648434", "tree": "21d8d0741a5ae4676fea5b53939cc806ae2b41bd", "parents": [ "91adb56473febeeb3ef657bb5147ddd355465700" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:39:39 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:39:39 2009 +1100" }, "message": "md: md_unregister_thread should cope with being passed NULL\n\nMostly md_unregister_thread is only called when we know that the\nthread is NULL, but sometimes we need to check first. It is safer\nto put the check inside md_unregister_thread itself.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "34817e8c3948ea20316dfa8fd8947d6d0ee82ba9", "tree": "f4d2e75473b46db94928e21e9fe54b029432418b", "parents": [ "67cc2b8165857ba019920d1f00d64bcc4140075d" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:39:38 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:39:38 2009 +1100" }, "message": "md: make sure new_level, new_chunksize, new_layout always have sensible values.\n\nWhen an md array is undergoing a change, we have new_* fields that\nshow the new values.\nWhen no change is happening, it is least confusing if these have\nthe same value as the normal fields.\nThis is true in most cases, but not when the values are set via sysfs.\n\nSo fix this up.\n\nA subsequent patch will BUG_ON if these things aren\u0027t consistent.\n\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "dd8ac336c13fd8afdb082ebacb1cddd5cf727889", "tree": "0baa8111d7406774525a1053be461135257d73d2", "parents": [ "58c0fed400603a802968b23ddf78f029c5a84e41" ], "author": { "name": "Andre Noll", "email": "maan@systemlinux.org", "time": "Tue Mar 31 14:33:13 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:33:13 2009 +1100" }, "message": "md: Represent raid device size in sectors.\n\nThis patch renames the \"size\" field of struct mdk_rdev_s to\n\"sectors\" and changes this field to store sectors instead of\nblocks.\n\nAll users of this field, linear.c, raid0.c and md.c, are fixed up\naccordingly which gets rid of many multiplications and divisions.\n\nSigned-off-by: Andre Noll \u003cmaan@systemlinux.org\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "58c0fed400603a802968b23ddf78f029c5a84e41", "tree": "474fcb9775bb07f39ebb7802fb9b51d69222dcbb", "parents": [ "575a80fa4f623141e9791e41879d87800fb6d862" ], "author": { "name": "Andre Noll", "email": "maan@systemlinux.org", "time": "Tue Mar 31 14:33:13 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:33:13 2009 +1100" }, "message": "md: Make mddev-\u003esize sector-based.\n\nThis patch renames the \"size\" field of struct mddev_s to \"dev_sectors\"\nand stores the number of 512-byte sectors instead of the number of\n1K-blocks in it.\n\nAll users of that field, including raid levels 1,4-6,10, are adjusted\naccordingly. This simplifies the code a bit because it allows to get\nrid of a couple of divisions/multiplications by two.\n\nIn order to make checkpatch happy, some minor coding style issues\nhave also been addressed. In particular, size_store() now uses\nstrict_strtoull() instead of simple_strtoull().\n\nSigned-off-by: Andre Noll \u003cmaan@systemlinux.org\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "575a80fa4f623141e9791e41879d87800fb6d862", "tree": "f316efc3ee33b2914d8b9f3a3041394560ee9e90", "parents": [ "97e4f42d62badb0f9fbc27c013e89bc1336a03bc" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:33:13 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:33:13 2009 +1100" }, "message": "md: be more consistent about setting WriteMostly flag when adding a drive to an array\n\nWhen a drive is added to an array using ADD_NEW_DISK, there are two\nplaces we can get certain flags from: the metadata on the disk or the\nflags passed through the IOCTL.\n\nFor the WriteMostly flag (aka MD_DISK_WRITEMOSTLY) we take the value\nfrom either of those sources depending on if it is set (i.e. we\neffectively \u0027or\u0027 the two sources together).\n\nThis makes it awkward to clear, and is at best inconsistent.\n\nAs documented code (in mdadm) requires that setting\nMD_DISK_WRITEMOSTLY in the ioctl will be effective, we resolve the\ninconsistency by always using the value for this flag from the ioctl,\nand ignoring the value on disk.\n\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "97e4f42d62badb0f9fbc27c013e89bc1336a03bc", "tree": "04cc809702a6b080c417c4ddf605642bbf7de521", "parents": [ "43b2e5d86d8bdd77386226db0bc961529492c043" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:33:13 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:33:13 2009 +1100" }, "message": "md: occasionally checkpoint drive recovery to reduce duplicate effort after a crash\n\nVersion 1.x metadata has the ability to record the status of a\npartially completed drive recovery.\nHowever we only update that record on a clean shutdown.\nIt would be nice to update it on unclean shutdowns too, particularly\nwhen using a bitmap that removes much to the \u0027sync\u0027 effort after an\nunclean shutdown.\n\nOne complication with checkpointing recovery is that we only know\nwhere we are up to in terms of IO requests started, not which ones\nhave completed. And we need to know what has completed to record\nhow much is recovered. So occasionally pause the recovery until all\nsubmitted requests are completed, then update the record of where\nwe are up to.\n\nWhen we have a bitmap, we already do that pause occasionally to keep\nthe bitmap up-to-date. So enhance that code to record the recovery\noffset and schedule a superblock update.\nAnd when there is no bitmap, just pause 16 times during the resync to\ndo a checkpoint.\n\u002716\u0027 is a fairly arbitrary number. But we don\u0027t really have any good\nway to judge how often is acceptable, and it seems like a reasonable\nnumber for now.\n\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "43b2e5d86d8bdd77386226db0bc961529492c043", "tree": "601a885b1410324678cf319eee77cc54a02f2cf3", "parents": [ "bff61975b3d6c18ee31457cc5b4d73042f44915f" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:33:13 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:33:13 2009 +1100" }, "message": "md: move md_k.h from include/linux/raid/ to drivers/md/\n\nIt really is nicer to keep related code together..\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "bff61975b3d6c18ee31457cc5b4d73042f44915f", "tree": "3aff48088b35172e74f56ae54f0b53e76a0c2150", "parents": [ "92022950c6b1bb3da90b2976b20271cdfd98b8a3" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:33:13 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:33:13 2009 +1100" }, "message": "md: move lots of #include lines out of .h files and into .c\n\nThis makes the includes more explicit, and is preparation for moving\nmd_k.h to drivers/md/md.h\n\nRemove include/raid/md.h as its only remaining use was to #include\nother files.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "8b2b5c217c20b5460218ab8731295f2e46c7dd29", "tree": "f5da8b06b3d2a53e80c31e0c0aa386e381b3a841", "parents": [ "ef740c372dfd80e706dbf955d4e4aedda6c0c148" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:27:03 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:27:03 2009 +1100" }, "message": "md: move LEVEL_* definition from md_k.h to md_u.h\n\n.. as they are part of the user-space interface.\nAlso move MdpMinorShift into there so we can remove duplication.\n\nLastly move mdp_major in. It is less obviously part of the user-space\ninterface, but do_mounts_md.c uses it, and it is acting a bit like\nuser-space.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "ef740c372dfd80e706dbf955d4e4aedda6c0c148", "tree": "8d9ef9db346ee1ba319a125c9de83cdde049510d", "parents": [ "2a40a8aed083d988df6822bb9b1b08fb7ce21e1d" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Tue Mar 31 14:27:03 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:27:03 2009 +1100" }, "message": "md: move headers out of include/linux/raid/\n\nMove the headers with the local structures for the disciplines and\nbitmap.h into drivers/md/ so that they are more easily grepable for\nhacking and not far away. md.h is left where it is for now as there\nare some uses from the outside.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "3dbd8c2e3ff0185585e068f190289d2a267a3e83", "tree": "f49dfbb19fc57e7888a53e763449c36e692367c4", "parents": [ "3f9d99c12a533809342b475c95452e82761bcc1c" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Tue Mar 31 14:27:02 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:27:02 2009 +1100" }, "message": "md: stop defining MAJOR_NR\n\nMAJOR_NR was only required for magic in linux/blk.h in 2.4 or earlier\nkernels, so no need to keep it around.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "3f9d99c12a533809342b475c95452e82761bcc1c", "tree": "8e8bcc72dce1b69e958317f77c351bc0bd4e1c28", "parents": [ "355a43e641b948a7b755cb4c2466ec548d5b495f" ], "author": { "name": "Martin K. Petersen", "email": "martin.petersen@oracle.com", "time": "Tue Mar 31 14:27:02 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:27:02 2009 +1100" }, "message": "MD data integrity support\n\nmd: Add support for data integrity to MD\n\nIf all subdevices support the same protection format the MD device is\nflagged as integrity capable.\n\nSigned-off-by: Martin K. Petersen \u003cmartin.petersen@oracle.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "eea1bf384e05b5ab747f8530c4fba9e9e6907fff", "tree": "ed4c05f8bd7e5805092e9c6a2c257ca71dc0fe2d", "parents": [ "99adcd9d67aaf04e28f5ae96df280f236bde4b66" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:27:02 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:27:02 2009 +1100" }, "message": "md: Fix is_mddev_idle test (again).\n\nThere are two problems with is_mddev_idle.\n\n1/ sync_io is \u0027atomic_t\u0027 and hence \u0027int\u0027. curr_events and all the\n rest are \u0027long\u0027.\n So if sync_io were to wrap on a 64bit host, the value of\n curr_events would go very negative suddenly, and take a very\n long time to return to positive.\n\n So do all calculations as \u0027int\u0027. That gives us plenty of precision\n for what we need.\n\n2/ To initialise rdev-\u003elast_events we simply call is_mddev_idle, on\n the assumption that it will make sure that last_events is in a\n suitable range. It used to do this, but now it does not.\n So now we need to be more explicit about initialisation.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "5fd3a17ed456637a224cf4ca82b9ad9d005bc8d4", "tree": "24906c956159349cddecc43b3479d2a9add364df", "parents": [ "fec6c6fec3e20637bee5d276fb61dd8b49a3f9cc" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Wed Mar 04 00:57:25 2009 -0700" }, "committer": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Wed Mar 04 00:57:25 2009 -0700" }, "message": "md: fix deadlock when stopping arrays\n\nResolve a deadlock when stopping redundant arrays, i.e. ones that\nrequire a call to sysfs_remove_group when shutdown. The deadlock is\nsummarized below:\n\nThread1 Thread2\n------- -------\nread sysfs attribute stop array\n take mddev lock\n sysfs_remove_group\nsysfs_get_active\nwait for mddev lock\n wait for active\n\nSysrq-w:\n--------\nmdmon S 00000017 2212 4163 1\n f1982ea8 00000046 2dcf6b85 00000017 c0b23100 f2f83ed0 c0b23100 f2f8413c\n c0b23100 c0b23100 c0b1fb98 f2f8413c 00000000 f2f8413c c0b23100 f2291ecc\n 00000002 c0b23100 00000000 00000017 f2f83ed0 f1982eac 00000046 c044d9dd\nCall Trace:\n [\u003cc044d9dd\u003e] ? debug_mutex_add_waiter+0x1d/0x58\n [\u003cc06ef451\u003e] __mutex_lock_common+0x1d9/0x338\n [\u003cc06ef451\u003e] ? __mutex_lock_common+0x1d9/0x338\n [\u003cc06ef5e3\u003e] mutex_lock_interruptible_nested+0x33/0x3a\n [\u003cc0634553\u003e] ? mddev_lock+0x14/0x16\n [\u003cc0634553\u003e] mddev_lock+0x14/0x16\n [\u003cc0634eda\u003e] md_attr_show+0x2a/0x49\n [\u003cc04e9997\u003e] sysfs_read_file+0x93/0xf9\nmdadm D 00000017 2812 4177 1\n f0401d78 00000046 430456f8 00000017 f0401d58 f0401d20 c0b23100 f2da2c4c\n c0b23100 c0b23100 c0b1fb98 f2da2c4c 0a10fc36 00000000 c0b23100 f0401d70\n 00000003 c0b23100 00000000 00000017 f2da29e0 00000001 00000002 00000000\nCall Trace:\n [\u003cc06eed1b\u003e] schedule_timeout+0x1b/0x95\n [\u003cc06eed1b\u003e] ? schedule_timeout+0x1b/0x95\n [\u003cc06eeb97\u003e] ? wait_for_common+0x34/0xdc\n [\u003cc044fa8a\u003e] ? trace_hardirqs_on_caller+0x18/0x145\n [\u003cc044fbc2\u003e] ? trace_hardirqs_on+0xb/0xd\n [\u003cc06eec03\u003e] wait_for_common+0xa0/0xdc\n [\u003cc0428c7c\u003e] ? default_wake_function+0x0/0x12\n [\u003cc06eeccc\u003e] wait_for_completion+0x17/0x19\n [\u003cc04ea620\u003e] sysfs_addrm_finish+0x19f/0x1d1\n [\u003cc04e920e\u003e] sysfs_hash_and_remove+0x42/0x55\n [\u003cc04eb4db\u003e] sysfs_remove_group+0x57/0x86\n [\u003cc0638086\u003e] do_md_stop+0x13a/0x499\n\nThis has been there for a while, but is easier to trigger now that mdmon\nis closely watching sysfs.\n\nCc: \u003cstable@kernel.org\u003e\nReported-by: Jacek Danecki \u003cjacek.danecki@intel.com\u003e\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\n" }, { "commit": "93dbb393503d53cd226e5e1f0088fe8f4dbaa2b8", "tree": "790365e207951cf6810e8995f3141ddc0b74519b", "parents": [ "c1c201200a359cf3b6e2e36a4236cdca77a3cd8e" ], "author": { "name": "Jens Axboe", "email": "jens.axboe@oracle.com", "time": "Mon Feb 16 10:25:40 2009 +0100" }, "committer": { "name": "Jens Axboe", "email": "jens.axboe@oracle.com", "time": "Wed Feb 18 10:32:00 2009 +0100" }, "message": "block: fix bad definition of BIO_RW_SYNC\n\nWe can\u0027t OR shift values, so get rid of BIO_RW_SYNC and use BIO_RW_SYNCIO\nand BIO_RW_UNPLUG explicitly. This brings back the behaviour from before\n213d9417fec62ef4c3675621b9364a667954d4dd.\n\nSigned-off-by: Jens Axboe \u003cjens.axboe@oracle.com\u003e\n" }, { "commit": "de01dfadf25bf83cfe3d85c163005c4320532658", "tree": "dc1cca5a6aa10ecc0fea2fb9f13534685ba8ff61", "parents": [ "852c8bf484a0e17ee27f413ef26e87f522af5607" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Feb 06 18:02:46 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Feb 06 18:02:46 2009 +1100" }, "message": "md: Ensure an md array never has too many devices.\n\nEach different metadata format supported by md supports a\ndifferent maximum number of devices.\nWe really should be enforcing this maximum in the kernel, but\nwe aren\u0027t quite doing that properly.\n\nWe currently only enforce it at the \u0027hot_add\u0027 point, which is an\nolder interface which is not used by current userspace.\n\nWe need to also enforce it at \u0027add_new_disk\u0027 time for active arrays\nand at \u0027do_md_run\u0027 time when starting a new array.\n\nSo move the test from \u0027hot_add\u0027 into \u0027bind_rdev_to_array\u0027 which is\ncalled from both \u0027hot_add\u0027 and \u0027add_new_disk, and add a new\ntest in \u0027analyse_sbs\u0027 which is called from \u0027do_md_run\u0027.\n\nThis bug (or missing feature) has been around \"forever\" and so\nthe patch is suitable for any -stable that is currently maintained.\n\nCc: stable@kernel.org\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "4044ba58dd15cb01797c4fd034f39ef4a75f7cc3", "tree": "e1bea8143538fc3eaeeb8578c2f9231e32809a25", "parents": [ "efeb53c0e57213e843b7ef3cc6ebcdea7d6186ac" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:11 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:11 2009 +1100" }, "message": "md: don\u0027t retry recovery of raid1 that fails due to error on source drive.\n\nIf a raid1 has only one working drive and it has a sector which\ngives an error on read, then an attempt to recover onto a spare will\nfail, but as the single remaining drive is not removed from the\narray, the recovery will be immediately re-attempted, resulting\nin an infinite recovery loop.\n\nSo detect this situation and don\u0027t retry recovery once an error\non the lone remaining drive is detected.\n\nAllow recovery to be retried once every time a spare is added\nin case the problem wasn\u0027t actually a media error.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "efeb53c0e57213e843b7ef3cc6ebcdea7d6186ac", "tree": "ef580effd8809fb0bc5d6ffa6f3b8abaa9180539", "parents": [ "d3374825ce57ba2214d375023979f6197ccc1385" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:10 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:10 2009 +1100" }, "message": "md: Allow md devices to be created by name.\n\nUsing sequential numbers to identify md devices is somewhat artificial.\nUsing names can be a lot more user-friendly.\n\nAlso, creating md devices by opening the device special file is a bit\nawkward.\n\nSo this patch provides a new option for creating and naming devices.\n\nWriting a name such as \"md_home\" to\n /sys/modules/md_mod/parameters/new_array\nwill cause an array with that name to be created. It will appear in\n/sys/block/ /proc/partitions and /proc/mdstat as \u0027md_home\u0027.\nIt will have an arbitrary minor number allocated.\n\nmd devices that a created by an open are destroyed on the last\nclose when the device is inactive.\nFor named md devices, they will not be destroyed until the array\nis explicitly stopped, either with the STOP_ARRAY ioctl or by\nwriting \u0027clear\u0027 to /sys/block/md_XXXX/md/array_state.\n\nThe name of the array must start \u0027md_\u0027 to avoid conflict with\nother devices.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "d3374825ce57ba2214d375023979f6197ccc1385", "tree": "441ea927a7c702e4eadeafbac8be97d664bfb83b", "parents": [ "a21d15042d8cd736caf82c2bac564f3f93f3d017" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:10 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:10 2009 +1100" }, "message": "md: make devices disappear when they are no longer needed.\n\nCurrently md devices, once created, never disappear until the module\nis unloaded. This is essentially because the gendisk holds a\nreference to the mddev, and the mddev holds a reference to the\ngendisk, this a circular reference.\n\nIf we drop the reference from mddev to gendisk, then we need to ensure\nthat the mddev is destroyed when the gendisk is destroyed. However it\nis not possible to hook into the gendisk destruction process to enable\nthis.\n\nSo we drop the reference from the gendisk to the mddev and destroy the\ngendisk when the mddev gets destroyed. However this has a\ncomplication.\nBetween the call\n __blkdev_get-\u003eget_gendisk-\u003ekobj_lookup-\u003emd_probe\nand the call\n __blkdev_get-\u003emd_open\n\nthere is no obvious way to hold a reference on the mddev any more, so\nunless something is done, it will disappear and gendisk will be\ndestroyed prematurely.\n\nAlso, once we decide to destroy the mddev, there will be an unlockable\nmoment before the gendisk is unlinked (blk_unregister_region) during\nwhich a new reference to the gendisk can be created. We need to\nensure that this reference can not be used. i.e. the -\u003eopen must\nfail.\n\nSo:\n 1/ in md_probe we set a flag in the mddev (hold_active) which\n indicates that the array should be treated as active, even\n though there are no references, and no appearance of activity.\n This is cleared by md_release when the device is closed if it\n is no longer needed.\n This ensures that the gendisk will survive between md_probe and\n md_open.\n\n 2/ In md_open we check if the mddev we expect to open matches\n the gendisk that we did open.\n If there is a mismatch we return -ERESTARTSYS and modify\n __blkdev_get to retry from the top in that case.\n In the -ERESTARTSYS sys case we make sure to wait until\n the old gendisk (that we succeeded in opening) is really gone so\n we loop at most once.\n\nSome udev configurations will always open an md device when it first\nappears. If we allow an md device that was just created by an open\nto disappear on an immediate close, then this can race with such udev\nconfigurations and result in an infinite loop the device being opened\nand closed, then re-open due to the \u0027ADD\u0027 even from the first open,\nand then close and so on.\nSo we make sure an md device, once created by an open, remains active\nat least until some md \u0027ioctl\u0027 has been made on it. This means that\nall normal usage of md devices will allow them to disappear promptly\nwhen not needed, but the worst that an incorrect usage will do it\ncause an inactive md device to be left in existence (it can easily be\nremoved).\n\nAs an array can be stopped by writing to a sysfs attribute\n echo clear \u003e /sys/block/mdXXX/md/array_state\nwe need to use scheduled work for deleting the gendisk and other\nkobjects. This allows us to wait for any pending gendisk deletion to\ncomplete by simply calling flush_scheduled_work().\n\n\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "a21d15042d8cd736caf82c2bac564f3f93f3d017", "tree": "d430b6ae126e9bc8139d1c491b80a18cc86b27f1", "parents": [ "8b76539823d71576927e3eb08b395eb6620f628d" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:09 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:09 2009 +1100" }, "message": "md: centralise all freeing of an \u0027mddev\u0027 in \u0027md_free\u0027\n\nmd_free is the .release handler for the md kobj_type.\nSo it makes sense to release all the objects referenced by\nthe mddev in there, rather than just prior to calling kobject_put\nfor what we think is the last time.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "8b76539823d71576927e3eb08b395eb6620f628d", "tree": "37f9c4da6c861a69b4695ea7818eab2cf6ce95f4", "parents": [ "cd2ac9321c26dc7a76455cd2a4df89123fa2b73e" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:08 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:08 2009 +1100" }, "message": "md: move allocation of -\u003equeue from mddev_find to md_probe\n\nIt is more balanced to just do simple initialisation in mddev_find,\nwhich allocates and links a new md device, and leave all the\nmore sophisticated allocation to md_probe (which calls mddev_find).\nmd_probe already allocated the gendisk. It should allocate the\nqueue too.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" } ], "next": "cd2ac9321c26dc7a76455cd2a4df89123fa2b73e" }