)]}' { "log": [ { "commit": "267d7b23dd62f6ec55e0fba777e456495c308fc7", "tree": "5c9fe0f07d5b87029b9c07eb003596c05d161a8f", "parents": [ "28f23d1f3b6a6078312b6e9585e583cc7326fe22", "ecb178bb2b154a40cfae9fa4c42e62ccfa81ac6b" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Mar 22 12:29:50 2012 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Mar 22 12:29:50 2012 -0700" }, "message": "Merge tag \u0027md-3.4\u0027 of git://neil.brown.name/md\n\nPull md updates for 3.4 from Neil Brown:\n \"Mostly tidying up code in preparation for some bigger changes next\n time.\n\n A few bug fixes tagged for -stable.\n\n Main functionality change is that some RAID10 arrays can now grow to\n use extra space that may have been made available on the individual\n devices.\"\n\nFixed up trivial conflicts with the k[un]map_atomic() cleanups in\ndrivers/md/bitmap.c.\n\n* tag \u0027md-3.4\u0027 of git://neil.brown.name/md: (22 commits)\n md: Add judgement bb-\u003eunacked_exist in function md_ack_all_badblocks().\n md: fix clearing of the \u0027changed\u0027 flags for the bad blocks list.\n md/bitmap: discard CHUNK_BLOCK_SHIFT macro\n md/bitmap: remove unnecessary indirection when allocating.\n md/bitmap: remove some pointless locking.\n md/bitmap: change a \u0027goto\u0027 to a normal \u0027if\u0027 construct.\n md/bitmap: move printing of bitmap status to bitmap.c\n md/bitmap: remove some unused noise from bitmap.h\n md/raid10 - support resizing some RAID10 arrays.\n md/raid1: handle merge_bvec_fn in member devices.\n md/raid10: handle merge_bvec_fn in member devices.\n md: add proper merge_bvec handling to RAID0 and Linear.\n md: tidy up rdev_for_each usage.\n md/raid1,raid10: avoid deadlock during resync/recovery.\n md/bitmap: ensure to load bitmap when creating via sysfs.\n md: don\u0027t set md arrays to readonly on shutdown.\n md: allow re-add to failed arrays.\n md/raid5: use atomic_dec_return() instead of atomic_dec() and atomic_read().\n md: Use existed macros instead of numbers\n md/raid5: removed unused \u0027added_devices\u0027 variable.\n ...\n" }, { "commit": "9f3938346a5c1fa504647670edb5fea5756cfb00", "tree": "7cf6d24d6b076c8db8571494984924cac03703a2", "parents": [ "69a7aebcf019ab3ff5764525ad6858fbe23bb86d", "317b6e128247f75976b0fc2b9fd8d2c20ef13b3a" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Wed Mar 21 09:40:26 2012 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Wed Mar 21 09:40:26 2012 -0700" }, "message": "Merge branch \u0027kmap_atomic\u0027 of git://github.com/congwang/linux\n\nPull kmap_atomic cleanup from Cong Wang.\n\nIt\u0027s been in -next for a long time, and it gets rid of the (no longer\nused) second argument to k[un]map_atomic().\n\nFix up a few trivial conflicts in various drivers, and do an \"evil\nmerge\" to catch some new uses that have come in since Cong\u0027s tree.\n\n* \u0027kmap_atomic\u0027 of git://github.com/congwang/linux: (59 commits)\n feature-removal-schedule.txt: schedule the deprecated form of kmap_atomic() for removal\n highmem: kill all __kmap_atomic() [swarren@nvidia.com: highmem: Fix ARM build break due to __kmap_atomic rename]\n drbd: remove the second argument of k[un]map_atomic()\n zcache: remove the second argument of k[un]map_atomic()\n gma500: remove the second argument of k[un]map_atomic()\n dm: remove the second argument of k[un]map_atomic()\n tomoyo: remove the second argument of k[un]map_atomic()\n sunrpc: remove the second argument of k[un]map_atomic()\n rds: remove the second argument of k[un]map_atomic()\n net: remove the second argument of k[un]map_atomic()\n mm: remove the second argument of k[un]map_atomic()\n lib: remove the second argument of k[un]map_atomic()\n power: remove the second argument of k[un]map_atomic()\n kdb: remove the second argument of k[un]map_atomic()\n udf: remove the second argument of k[un]map_atomic()\n ubifs: remove the second argument of k[un]map_atomic()\n squashfs: remove the second argument of k[un]map_atomic()\n reiserfs: remove the second argument of k[un]map_atomic()\n ocfs2: remove the second argument of k[un]map_atomic()\n ntfs: remove the second argument of k[un]map_atomic()\n ...\n" }, { "commit": "69a7aebcf019ab3ff5764525ad6858fbe23bb86d", "tree": "7211df5704b743a7667159748c670a9744164482", "parents": [ "d464c92b5234227c1698862a1906827e2e398ae0", "f1f996b66cc3908a8f5ffccc2ff41840e92f3b10" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Mar 20 21:12:50 2012 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Mar 20 21:12:50 2012 -0700" }, "message": "Merge branch \u0027for-linus\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial\n\nPull trivial tree from Jiri Kosina:\n \"It\u0027s indeed trivial -- mostly documentation updates and a bunch of\n typo fixes from Masanari.\n\n There are also several linux/version.h include removals from Jesper.\"\n\n* \u0027for-linus\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial: (101 commits)\n kcore: fix spelling in read_kcore() comment\n constify struct pci_dev * in obvious cases\n Revert \"char: Fix typo in viotape.c\"\n init: fix wording error in mm_init comment\n usb: gadget: Kconfig: fix typo for \u0027different\u0027\n Revert \"power, max8998: Include linux/module.h just once in drivers/power/max8998_charger.c\"\n writeback: fix fn name in writeback_inodes_sb_nr_if_idle() comment header\n writeback: fix typo in the writeback_control comment\n Documentation: Fix multiple typo in Documentation\n tpm_tis: fix tis_lock with respect to RCU\n Revert \"media: Fix typo in mixer_drv.c and hdmi_drv.c\"\n Doc: Update numastat.txt\n qla4xxx: Add missing spaces to error messages\n compiler.h: Fix typo\n security: struct security_operations kerneldoc fix\n Documentation: broken URL in libata.tmpl\n Documentation: broken URL in filesystems.tmpl\n mtd: simplify return logic in do_map_probe()\n mm: fix comment typo of truncate_inode_pages_range\n power: bq27x00: Fix typos in comment\n ...\n" }, { "commit": "c2e022cb654fa6595238dc52311a85e6444da1f7", "tree": "f3dba0008bb940e3b8c6fcd81b0f29004de06c1c", "parents": [ "c58e0377d61e209600def7d4d9ae535ea94bc210" ], "author": { "name": "Cong Wang", "email": "amwang@redhat.com", "time": "Mon Nov 28 13:26:02 2011 +0800" }, "committer": { "name": "Cong Wang", "email": "xiyou.wangcong@gmail.com", "time": "Tue Mar 20 21:48:28 2012 +0800" }, "message": "dm: remove the second argument of k[un]map_atomic()\n\nAcked-by: Milan Broz \u003cmbroz@redhat.com\u003e\nSigned-off-by: Cong Wang \u003camwang@redhat.com\u003e\n" }, { "commit": "b2f46e6882564897f6ea3ad904f0a65dc1c6cb3b", "tree": "e7c664de2956945c0c37b4895b134253196d006a", "parents": [ "2a156d094d590e1cb946d1c353f1c1a89013f822" ], "author": { "name": "Cong Wang", "email": "amwang@redhat.com", "time": "Mon Nov 28 13:25:44 2011 +0800" }, "committer": { "name": "Cong Wang", "email": "xiyou.wangcong@gmail.com", "time": "Tue Mar 20 21:48:18 2012 +0800" }, "message": "md: remove the second argument of k[un]map_atomic()\n\nAcked-by: NeilBrown \u003cneilb@suse.de\u003e\nSigned-off-by: Cong Wang \u003camwang@redhat.com\u003e\n" }, { "commit": "ecb178bb2b154a40cfae9fa4c42e62ccfa81ac6b", "tree": "a3a6ff71d28069f6eef78a4f24f7f9c385a086a7", "parents": [ "d0962936bff659d20522555b517582a2715fd23f" ], "author": { "name": "majianpeng", "email": "majianpeng@gmail.com", "time": "Mon Mar 19 12:46:42 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:42 2012 +1100" }, "message": "md: Add judgement bb-\u003eunacked_exist in function md_ack_all_badblocks().\n\nIf there are no unacked bad blocks, then there is no point searching\nfor them to acknowledge them.\n\n\nSigned-off-by: majianpeng \u003cmajianpeng@gmail.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "d0962936bff659d20522555b517582a2715fd23f", "tree": "dc9654b2e2c7b7db2b8f2a14f829d5f807c7342e", "parents": [ "61a0d80ce4ab5b4fb9ecb38f1fb19654778b71ed" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:41 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:41 2012 +1100" }, "message": "md: fix clearing of the \u0027changed\u0027 flags for the bad blocks list.\n\nIn super_1_sync (the first hunk) we need to clear \u0027changed\u0027 before\nchecking read_seqretry(), otherwise we might race with other code\nadding a bad block and so won\u0027t retry later.\n\nIn md_update_sb (the second hunk), in the case where there is no\nmetadata (neither persistent nor external), we treat any bad blocks as\nan error. However we need to clear the \u0027changed\u0027 flag before calling\nmd_ack_all_badblocks, else it won\u0027t do anything.\n\nThis patch is suitable for -stable release 3.0 and later.\n\nCc: stable@vger.kernel.org\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "61a0d80ce4ab5b4fb9ecb38f1fb19654778b71ed", "tree": "21631162d46575db6645636d1c18b8797247d0c9", "parents": [ "792a1d4bbf960000f066358f0a8c6e769c8c72bc" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:41 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:41 2012 +1100" }, "message": "md/bitmap: discard CHUNK_BLOCK_SHIFT macro\n\nBe redefining -\u003echunkshift as the shift from sectors to chunks rather\nthan bytes to chunks, we can just use \"bitmap-\u003echunkshift\" which is\nshorter than the macro call, and less indirect.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "792a1d4bbf960000f066358f0a8c6e769c8c72bc", "tree": "97e9a5c0854551c3fa80e88851ad3317af24ca13", "parents": [ "5a6c824ebb7c9f8dbbc92ffd3528e6366cad1a54" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:41 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:41 2012 +1100" }, "message": "md/bitmap: remove unnecessary indirection when allocating.\n\nThese funcitons don\u0027t add anything useful except possibly the trace\npoints, and I don\u0027t think they are worth the extra indirection.\nSo remove them.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "5a6c824ebb7c9f8dbbc92ffd3528e6366cad1a54", "tree": "e78d8527ae9e7be05001ed12f1cad01f8719bde0", "parents": [ "278c1ca2f254d0695d2eba79793d20ce785323ea" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:40 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:40 2012 +1100" }, "message": "md/bitmap: remove some pointless locking.\n\nThere is nothing gained by holding a lock while we check if a pointer\nis NULL or not. If there could be a race, then it could become NULL\nimmediately after the unlock - but there is no race here.\n\nSo just remove the locking.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "278c1ca2f254d0695d2eba79793d20ce785323ea", "tree": "42be282251b17c16e030d7083eef4bbeefe60b41", "parents": [ "57148964d946614ffc6621539096ded1e7d896ab" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:40 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:40 2012 +1100" }, "message": "md/bitmap: change a \u0027goto\u0027 to a normal \u0027if\u0027 construct.\n\nThe use of a goto makes the control flow more obscure here.\n\nSo make it a normal:\n if (x) {\n Y;\n }\n\nNo functional change.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "57148964d946614ffc6621539096ded1e7d896ab", "tree": "d4bdadf58d740fcdb3c65063a5706cc3902f2b9b", "parents": [ "4ba97dff719b4cbeb7a4f6beddd2feb7404102d8" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:40 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:40 2012 +1100" }, "message": "md/bitmap: move printing of bitmap status to bitmap.c\n\nThe part of /proc/mdstat which describes the bitmap should really\nbe generated by code in bitmap.c. So move it there.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "4ba97dff719b4cbeb7a4f6beddd2feb7404102d8", "tree": "3d8e2afc4d20405a88fb70e7cd494452944b3a41", "parents": [ "006a09a0ae0a494473a8cd82c8d1d653e37e6663" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:40 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:40 2012 +1100" }, "message": "md/bitmap: remove some unused noise from bitmap.h\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "006a09a0ae0a494473a8cd82c8d1d653e37e6663", "tree": "169c59f77ef89e1c7cfb727249d60de88370fe79", "parents": [ "6b740b8d79252f13bcb7e5d3c1d43157e78a81e7" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:40 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:40 2012 +1100" }, "message": "md/raid10 - support resizing some RAID10 arrays.\n\n\u0027resizing\u0027 an array in this context means making use of extra\nspace that has become available in component devices, not adding new\ndevices.\nIt also includes shrinking the array to take up less space of\ncomponent devices.\n\nThis is not supported for array with a \u0027far\u0027 layout. However\nfor \u0027near\u0027 and \u0027offset\u0027 layout arrays, adding and removing space at\nthe end of the devices is easy to support, and this patch provides\nthat support.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "6b740b8d79252f13bcb7e5d3c1d43157e78a81e7", "tree": "4b99f8fb395e7a205a85766d1bd241dce39c4337", "parents": [ "050b66152f87c79e8d66aed0e7996f9336462d5f" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:39 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:39 2012 +1100" }, "message": "md/raid1: handle merge_bvec_fn in member devices.\n\nCurrently we don\u0027t honour merge_bvec_fn in member devices so if there\nis one, we force all requests to be single-page at most.\nThis is not ideal.\n\nSo create a raid1 merge_bvec_fn to check that function in children\nas well.\n\nThis introduces a small problem. There is no locking around calls\nthe -\u003emerge_bvec_fn and subsequent calls to -\u003emake_request. So a\ndevice added between these could end up getting a request which\nviolates its merge_bvec_fn.\n\nCurrently the best we can do is synchronize_sched(). This will work\nproviding no preemption happens. If there is is preemption, we just\nhave to hope that new devices are largely consistent with old devices.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "050b66152f87c79e8d66aed0e7996f9336462d5f", "tree": "44d100c2eadf2a56794e7b526abeb21d1019baa1", "parents": [ "ba13da47ffa202784355561f72160a41350e95cc" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:39 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:39 2012 +1100" }, "message": "md/raid10: handle merge_bvec_fn in member devices.\n\nCurrently we don\u0027t honour merge_bvec_fn in member devices so if there\nis one, we force all requests to be single-page at most.\nThis is not ideal.\n\nSo enhance the raid10 merge_bvec_fn to check that function in children\nas well.\n\nThis introduces a small problem. There is no locking around calls\nthe -\u003emerge_bvec_fn and subsequent calls to -\u003emake_request. So a\ndevice added between these could end up getting a request which\nviolates its merge_bvec_fn.\n\nCurrently the best we can do is synchronize_sched(). This will work\nproviding no preemption happens. If there is preemption, we just\nhave to hope that new devices are largely consistent with old devices.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "ba13da47ffa202784355561f72160a41350e95cc", "tree": "9b60f27ab89e4036df65d0dc3bf52b7420f83a50", "parents": [ "dafb20fa34320a472deb7442f25a0c086e0feb33" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:39 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:39 2012 +1100" }, "message": "md: add proper merge_bvec handling to RAID0 and Linear.\n\nThese personalities currently set a max request size of one page\nwhen any member device has a merge_bvec_fn because they don\u0027t\nbother to call that function.\n\nThis causes extra works in splitting and combining requests.\n\nSo make the extra effort to call the merge_bvec_fn when it exists\nso that we end up with larger requests out the bottom.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "dafb20fa34320a472deb7442f25a0c086e0feb33", "tree": "2ff501805f8a6d08119f1f1a7248f579d52e491b", "parents": [ "d6b42dcb995e6acd7cc276774e751ffc9f0ef4bf" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:39 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:39 2012 +1100" }, "message": "md: tidy up rdev_for_each usage.\n\nmd.h has an \u0027rdev_for_each()\u0027 macro for iterating the rdevs in an\nmddev. However it uses the \u0027safe\u0027 version of list_for_each_entry,\nand so requires the extra variable, but doesn\u0027t include \u0027safe\u0027 in the\nname, which is useful documentation.\n\nConsequently some places use this safe version without needing it, and\nmany use an explicity list_for_each entry.\n\nSo:\n - rename rdev_for_each to rdev_for_each_safe\n - create a new rdev_for_each which uses the plain\n list_for_each_entry,\n - use the \u0027safe\u0027 version only where needed, and convert all other\n list_for_each_entry calls to use rdev_for_each.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "d6b42dcb995e6acd7cc276774e751ffc9f0ef4bf", "tree": "a9112351e8ddd2866afd8687b645a1c5bf574ee7", "parents": [ "4474ca42e2577563a919fd3ed782e2ec55bf11a2" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:38 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:38 2012 +1100" }, "message": "md/raid1,raid10: avoid deadlock during resync/recovery.\n\nIf RAID1 or RAID10 is used under LVM or some other stacking\nblock device, it is possible to enter a deadlock during\nresync or recovery.\nThis can happen if the upper level block device creates\ntwo requests to the RAID1 or RAID10. The first request gets\nprocessed, blocks recovery and queue requests for underlying\nrequests in current-\u003ebio_list. A resync request then starts\nwhich will wait for those requests and block new IO.\n\nBut then the second request to the RAID1/10 will be attempted\nand it cannot progress until the resync request completes,\nwhich cannot progress until the underlying device requests complete,\nwhich are on a queue behind that second request.\n\nSo allow that second request to proceed even though there is\na resync request about to start.\n\nThis is suitable for any -stable kernel.\n\nCc: stable@vger.kernel.org\nReported-by: Ray Morris \u003csupport@bettercgi.com\u003e\nTested-by: Ray Morris \u003csupport@bettercgi.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "4474ca42e2577563a919fd3ed782e2ec55bf11a2", "tree": "db451c8fad37b281ddbf1d00a779257537cc61ff", "parents": [ "c744a65c1e2d59acc54333ce80a5b0702a98010b" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:37 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:37 2012 +1100" }, "message": "md/bitmap: ensure to load bitmap when creating via sysfs.\n\nWhen commit 69e51b449d383e (md/bitmap: separate out loading a bitmap...)\ncreated bitmap_load, it missed calling it after bitmap_create when a\nbitmap is created through the sysfs interface.\nSo if a bitmap is added this way, we don\u0027t allocate memory properly\nand can crash.\n\nThis is suitable for any -stable release since 2.6.35.\nCc: stable@vger.kernel.org\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "c744a65c1e2d59acc54333ce80a5b0702a98010b", "tree": "c76ff42e8f799030636d07c82879cc2bef7798db", "parents": [ "dc10c643e8a8d008fd16dd6706e9e0018eadf8d2" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:37 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:37 2012 +1100" }, "message": "md: don\u0027t set md arrays to readonly on shutdown.\n\nIt seems that with recent kernel, writeback can still be happening\nwhile shutdown is happening, and consequently data can be written\nafter the md reboot notifier switches all arrays to read-only.\nThis causes a BUG.\n\nSo don\u0027t switch them to read-only - just mark them clean and\nset \u0027safemode\u0027 to \u00272\u0027 which mean that immediately after any\nwrite the array will be switch back to \u0027clean\u0027.\n\nThis could result in the shutdown happening when array is marked\ndirty, thus forcing a resync on reboot. However if you reboot\nwithout performing a \"sync\" first, you get to keep both halves.\n\nThis is suitable for any stable kernel (though there might be some\nconflicts with obvious fixes in earlier kernels).\n\nCc: stable@vger.kernel.org\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "dc10c643e8a8d008fd16dd6706e9e0018eadf8d2", "tree": "6a0efe323cfaca9d180c0429c74697598c6d9a05", "parents": [ "41fe75f60bcd4d698daed3e54bb099227358ce58" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:37 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 19 12:46:37 2012 +1100" }, "message": "md: allow re-add to failed arrays.\n\nWhen an array is failed (some data inaccessible) then there is no\npoint attempting to add a spare as it could not possibly be recovered.\n\nHowever that may be value in re-adding a recently removed device.\ne.g. if there is a write-intent-bitmap and it is clear, then access\nto the data could be restored by this action.\n\nSo don\u0027t reject a re-add to a failed array for RAID10 and RAID5 (the\nonly arrays types that check for a failed array).\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "41fe75f60bcd4d698daed3e54bb099227358ce58", "tree": "bbd15d0143d20c59f87c5e6d2e0afba57252929b", "parents": [ "43437ecd5adc8bd712b7140c8a70e2b4a80a89dd" ], "author": { "name": "majianpeng", "email": "majianpeng@gmail.com", "time": "Tue Mar 13 11:21:25 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 13 11:21:25 2012 +1100" }, "message": "md/raid5: use atomic_dec_return() instead of atomic_dec() and atomic_read().\n\nSigned-off-by: majianpeng \u003cmajianpeng@gmail.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "9d4c7d8799c418816342e263479fa010b182183e", "tree": "e1450bda6809a36d5bdb666ae0ab88ef1492b580", "parents": [ "547414d19fd72376ff2ecc42aac8d7a051f03d26" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 13 11:21:21 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 13 11:21:21 2012 +1100" }, "message": "md/raid5: removed unused \u0027added_devices\u0027 variable.\n\ncommit 908f4fbd265733 removed the last user of this variable,\nso we should discard it completely.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "547414d19fd72376ff2ecc42aac8d7a051f03d26", "tree": "d46f4726e9bc397a182b9c36665a941e70692281", "parents": [ "1e3fa9bd5061778fb5cf4648e4e8321e8cbbb95b" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 13 11:21:20 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 13 11:21:20 2012 +1100" }, "message": "md/raid10: remove unnecessary smp_mb() from end_sync_write\n\nRecent commit 4ca40c2ce099e4f1ce3 (md/raid10: Allow replacement device ...)\nadded an smp_mb in end_sync_write.\nThis was to close a possible race with raid10_remove_disk.\nHowever there is no such race as it is never attempted to remove a\ndisk while resync (or recovery) is happening.\nso the smp_mb is just noise.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "1e3fa9bd5061778fb5cf4648e4e8321e8cbbb95b", "tree": "de51166f0369e17cc2cb20566b61b7b3c873d7fc", "parents": [ "fde7d9049e55ab85a390be7f415d74c9f62dd0f9" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 13 11:21:18 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 13 11:21:18 2012 +1100" }, "message": "md/raid5: make sure reshape_position is cleared on error path.\n\nLeaving a valid reshape_position value in place could be confusing.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "5d0edf29151bb5ba372784b7e369f42cf23a94eb", "tree": "847eee159ac3387fd6ad1c385341d70fc45ea13b", "parents": [ "4f262acfde22b63498b5e4f165e53d3bb4e96400", "0ca93de9b789e0eb05e103f0c04de72df13da73a" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Mar 08 17:21:51 2012 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Thu Mar 08 17:21:51 2012 -0800" }, "message": "Merge tag \u0027dm-3.3-fixes\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/agk/linux-dm\n\nPull device-mapper fixes for 3.3 from Alasdair Kergon\n\nEight small device-mapper bug fixes.\n\n* tag \u0027dm-3.3-fixes\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/agk/linux-dm:\n dm raid: fix flush support\n dm raid: set MD_CHANGE_DEVS when rebuilding\n dm thin metadata: decrement counter after removing mapped block\n dm thin metadata: unlock superblock in init_pmd error path\n dm thin metadata: remove incorrect close_device on creation error paths\n dm flakey: fix crash on read when corrupt_bio_byte not set\n dm io: fix discard support\n dm ioctl: do not leak argv if target message only contains whitespace\n" }, { "commit": "0ca93de9b789e0eb05e103f0c04de72df13da73a", "tree": "3a7bd34140d69a9c7bc5eb1874de773511770197", "parents": [ "3aa3b2b2b1edb813dc5342d0108befc39541542d" ], "author": { "name": "Jonathan E Brassow", "email": "jbrassow@redhat.com", "time": "Wed Mar 07 19:09:48 2012 +0000" }, "committer": { "name": "Alasdair G Kergon", "email": "agk@redhat.com", "time": "Wed Mar 07 19:09:48 2012 +0000" }, "message": "dm raid: fix flush support\n\nFix dm-raid flush support.\n\nBoth md and dm have support for flush, but the dm-raid target\nforgot to set the flag to indicate that flushes should be\npassed on. (Important for data integrity e.g. with writeback cache\nenabled.)\n\nSigned-off-by: Jonathan Brassow \u003cjbrassow@redhat.com\u003e\nAcked-by: Mike Snitzer \u003csnitzer@redhat.com\u003e\nCc: stable@kernel.org\nSigned-off-by: Alasdair G Kergon \u003cagk@redhat.com\u003e\n" }, { "commit": "3aa3b2b2b1edb813dc5342d0108befc39541542d", "tree": "151000a59d089231fcefbf44539c89ee56436c84", "parents": [ "af63bcb817cf708f53bcae6edc2e3fb7dd7d8051" ], "author": { "name": "Jonathan E Brassow", "email": "jbrassow@redhat.com", "time": "Wed Mar 07 19:09:47 2012 +0000" }, "committer": { "name": "Alasdair G Kergon", "email": "agk@redhat.com", "time": "Wed Mar 07 19:09:47 2012 +0000" }, "message": "dm raid: set MD_CHANGE_DEVS when rebuilding\n\nThe \u0027rebuild\u0027 parameter is used to rebuild individual devices in an\narray (e.g. resynchronize a RAID1 device or recalculate a parity device\nin higher RAID). The MD_CHANGE_DEVS flag must be set when this\nparameter is given in order to write out the superblocks and make the\nchange take immediate effect. The code that handles new devices in\nsuper_load already sets MD_CHANGE_DEVS and \u0027FirstUse\u0027. (The \u0027FirstUse\u0027\nflag was being set as a special case for rebuilds in\nsuper_init_validation.)\n\nAdd a condition for rebuilds in super_load to take care of both flags\nwithout the special case in \u0027super_init_validation\u0027.\n\nSigned-off-by: Jonathan Brassow \u003cjbrassow@redhat.com\u003e\nCc: stable@kernel.org\nSigned-off-by: Alasdair G Kergon \u003cagk@redhat.com\u003e\n" }, { "commit": "af63bcb817cf708f53bcae6edc2e3fb7dd7d8051", "tree": "9c38899465b9bc3b8ae613b41a70ab0ff02030d1", "parents": [ "4469a5f387fdde956894137751a41473618a4a52" ], "author": { "name": "Joe Thornber", "email": "ejt@redhat.com", "time": "Wed Mar 07 19:09:44 2012 +0000" }, "committer": { "name": "Alasdair G Kergon", "email": "agk@redhat.com", "time": "Wed Mar 07 19:09:44 2012 +0000" }, "message": "dm thin metadata: decrement counter after removing mapped block\n\nCorrect the number of mapped sectors shown on a thin device\u0027s\nstatus line by decrementing td-\u003emapped_blocks in __remove() each time\na block is removed.\n\nSigned-off-by: Joe Thornber \u003cejt@redhat.com\u003e\nAcked-by: Mike Snitzer \u003csnitzer@redhat.com\u003e\nCc: stable@kernel.org\nSigned-off-by: Alasdair G Kergon \u003cagk@redhat.com\u003e\n" }, { "commit": "4469a5f387fdde956894137751a41473618a4a52", "tree": "f191a4eeabe0af42d8025b15286257f6a4bf9b1a", "parents": [ "1f3db25d8be4ac50b897b39609802183ea68a514" ], "author": { "name": "Joe Thornber", "email": "ejt@redhat.com", "time": "Wed Mar 07 19:09:43 2012 +0000" }, "committer": { "name": "Alasdair G Kergon", "email": "agk@redhat.com", "time": "Wed Mar 07 19:09:43 2012 +0000" }, "message": "dm thin metadata: unlock superblock in init_pmd error path\n\nIf dm_sm_disk_create() fails the superblock must be unlocked.\n\nSigned-off-by: Joe Thornber \u003cejt@redhat.com\u003e\nAcked-by: Mike Snitzer \u003csnitzer@redhat.com\u003e\nCc: stable@kernel.org\nSigned-off-by: Alasdair G Kergon \u003cagk@redhat.com\u003e\n" }, { "commit": "1f3db25d8be4ac50b897b39609802183ea68a514", "tree": "b8e140111ba62062d309ae0dec90543f35e28172", "parents": [ "1212268fd9816e3b8801e57b896fceaec71969ad" ], "author": { "name": "Mike Snitzer", "email": "snitzer@redhat.com", "time": "Wed Mar 07 19:09:41 2012 +0000" }, "committer": { "name": "Alasdair G Kergon", "email": "agk@redhat.com", "time": "Wed Mar 07 19:09:41 2012 +0000" }, "message": "dm thin metadata: remove incorrect close_device on creation error paths\n\nThe __open_device() error paths in __create_thin() and __create_snap()\nincorrectly call __close_device() even if td was not initialized by\n__open_device(). Remove this.\n\nAlso document __open_device() return values, remove a redundant\ntd-\u003echanged \u003d 1 in __create_thin(), and insert an additional\nsafeguard against creating an already-existing device.\n\nSigned-off-by: Mike Snitzer \u003csnitzer@redhat.com\u003e\nCc: stable@kernel.org\nSigned-off-by: Alasdair G Kergon \u003cagk@redhat.com\u003e\n" }, { "commit": "1212268fd9816e3b8801e57b896fceaec71969ad", "tree": "d0172aa71a3454faf2feb0c34e28690a6d027758", "parents": [ "0c535e0d6f463365c29623350dbd91642363c39b" ], "author": { "name": "Mike Snitzer", "email": "snitzer@redhat.com", "time": "Wed Mar 07 19:09:39 2012 +0000" }, "committer": { "name": "Alasdair G Kergon", "email": "agk@redhat.com", "time": "Wed Mar 07 19:09:39 2012 +0000" }, "message": "dm flakey: fix crash on read when corrupt_bio_byte not set\n\nThe following BUG is hit on the first read that is submitted to a dm\nflakey test device while the device is \"down\" if the corrupt_bio_byte\nfeature wasn\u0027t requested when the device\u0027s table was loaded.\n\nExample DM table that will hit this BUG:\n0 2097152 flakey 8:0 2048 0 30\n\nThis bug was introduced by commit a3998799fb4df0b0af8271a7d50c4269032397aa\n(dm flakey: add corrupt_bio_byte feature) in v3.1-rc1.\n\nBUG: unable to handle kernel paging request at ffff8801cfce3fff\nIP: [\u003cffffffffa008c233\u003e] corrupt_bio_data+0x6e/0xae [dm_flakey]\nPGD 1606063 PUD 0\nOops: 0002 [#1] SMP\n...\nCall Trace:\n \u003cIRQ\u003e\n [\u003cffffffffa008c2b5\u003e] flakey_end_io+0x42/0x48 [dm_flakey]\n [\u003cffffffffa00dca98\u003e] clone_endio+0x54/0xb6 [dm_mod]\n [\u003cffffffff81130587\u003e] bio_endio+0x2d/0x2f\n [\u003cffffffff811c819a\u003e] req_bio_endio+0x96/0x9f\n [\u003cffffffff811c94b9\u003e] blk_update_request+0x1dc/0x3a9\n [\u003cffffffff812f5ee2\u003e] ? rcu_read_unlock+0x21/0x23\n [\u003cffffffff811c96a6\u003e] blk_update_bidi_request+0x20/0x6e\n [\u003cffffffff811c9713\u003e] blk_end_bidi_request+0x1f/0x5d\n [\u003cffffffff811c978d\u003e] blk_end_request+0x10/0x12\n [\u003cffffffff8128f450\u003e] scsi_io_completion+0x1e5/0x4b1\n [\u003cffffffff812882a9\u003e] scsi_finish_command+0xec/0xf5\n [\u003cffffffff8128f830\u003e] scsi_softirq_done+0xff/0x108\n [\u003cffffffff811ce284\u003e] blk_done_softirq+0x84/0x98\n [\u003cffffffff81048d19\u003e] __do_softirq+0xe3/0x1d5\n [\u003cffffffff8138f83f\u003e] ? _raw_spin_lock+0x62/0x69\n [\u003cffffffff810997cf\u003e] ? handle_irq_event+0x4c/0x61\n [\u003cffffffff8139833c\u003e] call_softirq+0x1c/0x30\n [\u003cffffffff81003b37\u003e] do_softirq+0x4b/0xa3\n [\u003cffffffff81048a39\u003e] irq_exit+0x53/0xca\n [\u003cffffffff81398acd\u003e] do_IRQ+0x9d/0xb4\n [\u003cffffffff81390333\u003e] common_interrupt+0x73/0x73\n...\n\nSigned-off-by: Mike Snitzer \u003csnitzer@redhat.com\u003e\nCc: stable@vger.kernel.org # 3.1+\nSigned-off-by: Alasdair G Kergon \u003cagk@redhat.com\u003e\n" }, { "commit": "0c535e0d6f463365c29623350dbd91642363c39b", "tree": "33217f386886b01e5a033ac8c0cf5fb46f5c3464", "parents": [ "902c6a96a7cb9c50d2a8aed1788efad0a5d8f04c" ], "author": { "name": "Milan Broz", "email": "mbroz@redhat.com", "time": "Wed Mar 07 19:09:37 2012 +0000" }, "committer": { "name": "Alasdair G Kergon", "email": "agk@redhat.com", "time": "Wed Mar 07 19:09:37 2012 +0000" }, "message": "dm io: fix discard support\n\nThis patch fixes a crash by recognising discards in dm_io.\n\nCurrently dm_mirror can send REQ_DISCARD bios if running over a\ndiscard-enabled device and without support in dm_io the system\ncrashes badly.\n\nBUG: unable to handle kernel paging request at 00800000\nIP: __bio_add_page.part.17+0xf5/0x1e0\n...\n bio_add_page+0x56/0x70\n dispatch_io+0x1cf/0x240 [dm_mod]\n ? km_get_page+0x50/0x50 [dm_mod]\n ? vm_next_page+0x20/0x20 [dm_mod]\n ? mirror_flush+0x130/0x130 [dm_mirror]\n dm_io+0xdc/0x2b0 [dm_mod]\n...\n\nIntroduced in 2.6.38-rc1 by commit 5fc2ffeabb9ee0fc0e71ff16b49f34f0ed3d05b4\n(dm raid1: support discard).\n\nSigned-off-by: Milan Broz \u003cmbroz@redhat.com\u003e\nCc: stable@kernel.org\nAcked-by: Mike Snitzer \u003csnitzer@redhat.com\u003e\nSigned-off-by: Alasdair G Kergon \u003cagk@redhat.com\u003e\n" }, { "commit": "902c6a96a7cb9c50d2a8aed1788efad0a5d8f04c", "tree": "4f6f797bbaf2d5708d3e01269c1019bd9fb205b5", "parents": [ "192cfd58774b4d17b2fe8bdc77d89c2ef4e0591d" ], "author": { "name": "Jesper Juhl", "email": "jj@chaosbits.net", "time": "Wed Mar 07 19:09:34 2012 +0000" }, "committer": { "name": "Alasdair G Kergon", "email": "agk@redhat.com", "time": "Wed Mar 07 19:09:34 2012 +0000" }, "message": "dm ioctl: do not leak argv if target message only contains whitespace\n\nIf \u0027argc\u0027 is zero we jump to the \u0027out:\u0027 label, but this leaks the\n(unused) memory that \u0027dm_split_args()\u0027 allocated for \u0027argv\u0027 if the\nstring being split consisted entirely of whitespace. Jump to the\n\u0027out_argv:\u0027 label instead to free up that memory.\n\nSigned-off-by: Jesper Juhl \u003cjj@chaosbits.net\u003e\nCc: stable@kernel.org\nSigned-off-by: Alasdair G Kergon \u003cagk@redhat.com\u003e\n" }, { "commit": "a2e5f13ce806e79b5a234f9653a2a245424e29fa", "tree": "06ec6d22ccfa157195565c1777467a3677d6818b", "parents": [ "3e85fb9cd4f711d70c5d26baa86e438390731eab", "7a90484825680e7831856105f5fef654e6c02701" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Mar 05 16:01:25 2012 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Mar 05 16:01:25 2012 -0800" }, "message": "Merge tag \u0027md-3.3-fixes\u0027 of git://neil.brown.name/md\n\nPull md fixes from Neil Brown:\n \"Three fixes for md in 3.3-rc: Two relate to the recently added drive\n replacement. One fixes the problem where a read error in RAID10 would\n sometimes be retried indefinitely.\"\n\n* tag \u0027md-3.3-fixes\u0027 of git://neil.brown.name/md:\n md/raid10: fix assembling of arrays with replacement devices.\n md/raid10: fix handling of error on last working device in array.\n md/raid1: fix buglet in md_raid1_contested.\n" }, { "commit": "7a90484825680e7831856105f5fef654e6c02701", "tree": "24eacf1558541076767b59c0cbcc6b6835e35204", "parents": [ "fae8cc5ed0714953b1ad7cf86f030d2177278424" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 05 17:48:12 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 06 10:12:45 2012 +1100" }, "message": "md/raid10: fix assembling of arrays with replacement devices.\n\ncommit 56a2559bb654a (md/raid10: recognise replacements ...)\nchanged \u0027run\u0027 to set -\u003ereplacement or -\u003erdev depending on the\n\u0027Replacement\u0027 status if the device, but it didn\u0027t remove the\nold unconditional setting of \u0027rdev\u0027. So it was largely ineffective.\n\nSo remove that now.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "fae8cc5ed0714953b1ad7cf86f030d2177278424", "tree": "f61f54aaff4122671153e63cad86914566bce389", "parents": [ "f53e29fc87b6fb76db0043202ec2c3450caa5ff3" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Feb 14 11:10:10 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Feb 14 11:10:10 2012 +1100" }, "message": "md/raid10: fix handling of error on last working device in array.\n\nIf we get a read error on the last working device in a RAID10 which\ncontains the target block, then we don\u0027t fail the device (which is\ngood) but we don\u0027t abort retries, which is wrong.\nWe end up in an infinite loop retrying the read on the one device.\n\nThis patch fixes the problem in two places:\n1/ in raid10_end_read_request we don\u0027t even ask for a retry if this\n was the last usable device. This is efficient but a little racy\n and will sometimes retry when it should not.\n\n2/ in handle_read_error we are careful to exclude any device from\n retry which we tried to mark as faulty (that might have failed if\n it was the last device). This is race-free but less efficient.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "f53e29fc87b6fb76db0043202ec2c3450caa5ff3", "tree": "b1f8705e420775a40ebb2f26132fe27184b82fbb", "parents": [ "db91ff55bdf06736b849afc1b1fce5763bbb8d5d" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Feb 13 14:24:05 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Feb 13 14:24:05 2012 +1100" }, "message": "md/raid1: fix buglet in md_raid1_contested.\n\nSince we added \u0027replacement\u0027 capability, RAID1 can have twice\nas many devices as -\u003eraid_disks indicates.\nSo md_raid1_congested needs to check that many possible devices,\nnot just -\u003eraid_disks many.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "4d39aa1b998fffd481517c1dd03d83c38e1706f9", "tree": "76c4e4cf52b148ae035f71c7c30692b6634cd343", "parents": [ "4a68d54c983514f123e99fc720951a4ee4d84270", "db91ff55bdf06736b849afc1b1fce5763bbb8d5d" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Wed Feb 08 19:06:30 2012 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Wed Feb 08 19:06:30 2012 -0800" }, "message": "Merge tag \u0027md-3.3-fixes\u0027 of git://neil.brown.name/md\n\nSome simple md-related fixes.\n\n1/ two small fixes to ensure we handle an interrupted resync properly.\n2/ avoid loading the bitmap multiple times in dm-raid\n\n* tag \u0027md-3.3-fixes\u0027 of git://neil.brown.name/md:\n md: two small fixes to handling interrupt resync.\n Prevent DM RAID from loading bitmap twice.\n" }, { "commit": "db91ff55bdf06736b849afc1b1fce5763bbb8d5d", "tree": "ade2010773b721e3d699e75a9348f200e7ad31c4", "parents": [ "34f8ac6d79e5446c6242e4bcb474f152c857c5c6" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Feb 07 12:01:51 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Feb 07 12:01:51 2012 +1100" }, "message": "md: two small fixes to handling interrupt resync.\n\n1/ If a resync is aborted we should record how far we got\n (recovery_cp) the last request that we know has completed\n (-\u003ecurr_resync_completed) rather than the last request that was\n submitted (-\u003ecurr_resync).\n\n2/ When a resync aborts we still want to update the metadata with\n any changes, so set MD_CHANGE_DEVS even if we \u0027skip\u0027.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "972c5ae961d6e5103e2b33d935cfa4145fd47140", "tree": "350b2a76b979ba8766c09838617df67ff330eca0", "parents": [ "5196d20305d5e30d871111d3a876cf067dd94255", "7c7ed8ec337bf5f62cc5287a6eb6b2f1b7504c2f" ], "author": { "name": "Jiri Kosina", "email": "jkosina@suse.cz", "time": "Fri Feb 03 23:12:42 2012 +0100" }, "committer": { "name": "Jiri Kosina", "email": "jkosina@suse.cz", "time": "Fri Feb 03 23:13:05 2012 +0100" }, "message": "Merge branch \u0027master\u0027 into for-next\n\nSync with Linus\u0027 tree to be able to apply patch to a newer\ncode (namely drivers/gpu/drm/gma500/psb_intel_lvds.c)\n" }, { "commit": "ad075370ba0dd92fdb92989d1019bfc57ea42e1d", "tree": "86ec93b0379939b54e8d46c196aab83040738593", "parents": [ "98793265b429a3f0b3f1750e74d67cd4d740d162" ], "author": { "name": "Jesper Juhl", "email": "jj@chaosbits.net", "time": "Sun Jan 15 21:12:23 2012 +0100" }, "committer": { "name": "Jiri Kosina", "email": "jkosina@suse.cz", "time": "Fri Feb 03 22:38:12 2012 +0100" }, "message": "dm-bufio.c: there\u0027s no need to include linux/version.h\n\nAs \u0027make versioncheck\u0027 points out, drivers/md/dm-bufio.c has no need to include\nlinux/version.h, so this patch removes the unneeded include.\n\nSigned-off-by: Jesper Juhl \u003cjj@chaosbits.net\u003e\nAcked-by: Mikulas Patocka \u003cmpatocka@redhat.com\u003e\nSigned-off-by: Jiri Kosina \u003cjkosina@suse.cz\u003e\n" }, { "commit": "34f8ac6d79e5446c6242e4bcb474f152c857c5c6", "tree": "5a0be3b7910428e52603304aa53e8da4476fb4b2", "parents": [ "307729c8bc5b5a41361af8af95906eee7552acb1" ], "author": { "name": "Jonathan Brassow", "email": "jbrassow@redhat.com", "time": "Fri Jan 27 14:53:53 2012 -0600" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Jan 31 09:43:41 2012 +1100" }, "message": "Prevent DM RAID from loading bitmap twice.\n\nThe life cycle of a device-mapper target is:\n1) create\n2) resume\n3) suspend\n*) possibly repeat from 2\n4) destroy\n\nThe dm-raid target is unconditionally calling MD\u0027s bitmap_load function upon\nevery resume. If steps 2 \u0026 3 above are repeated, bitmap_load is called\nmultiple times. It is only written to be called once; otherwise, it allocates\nnew memory for the bitmap (without freeing the old) and incrementing the number\nof pages it thinks it has without zeroing first. This ultimately leads to\naccess beyond allocated memory and lost memory.\n\nSimply avoiding the bitmap_load call upon resume is not sufficient. If the\ntarget was suspended while the initial recovery was only partially complete,\nit needs to be restarted when the target is resumed. This is why\n\u0027md_wakeup_thread\u0027 is called before issuing the \u0027mddev_resume\u0027.\n\nSigned-off-by: Jonathan Brassow \u003cjbrassow@redhat.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "b3c9dd182ed3bdcdaf0e42625a35924b0497afdc", "tree": "ad48ad4d923fee147c736318d0fad35b3755f4f5", "parents": [ "83c2f912b43c3a7babbb6cb7ae2a5276c1ed2a3e", "5d381efb3d1f1ef10535a31ca0dd9b22fe1e1922" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Jan 15 12:24:45 2012 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Jan 15 12:24:45 2012 -0800" }, "message": "Merge branch \u0027for-3.3/core\u0027 of git://git.kernel.dk/linux-block\n\n* \u0027for-3.3/core\u0027 of git://git.kernel.dk/linux-block: (37 commits)\n Revert \"block: recursive merge requests\"\n block: Stop using macro stubs for the bio data integrity calls\n blockdev: convert some macros to static inlines\n fs: remove unneeded plug in mpage_readpages()\n block: Add BLKROTATIONAL ioctl\n block: Introduce blk_set_stacking_limits function\n block: remove WARN_ON_ONCE() in exit_io_context()\n block: an exiting task should be allowed to create io_context\n block: ioc_cgroup_changed() needs to be exported\n block: recursive merge requests\n block, cfq: fix empty queue crash caused by request merge\n block, cfq: move icq creation and rq-\u003eelv.icq association to block core\n block, cfq: restructure io_cq creation path for io_context interface cleanup\n block, cfq: move io_cq exit/release to blk-ioc.c\n block, cfq: move icq cache management to block core\n block, cfq: move io_cq lookup to blk-ioc.c\n block, cfq: move cfqd-\u003eicq_list to request_queue and add request-\u003eelv.icq\n block, cfq: reorganize cfq_io_context into generic and cfq specific parts\n block: remove elevator_queue-\u003eops\n block: reorder elevator switch sequence\n ...\n\nFix up conflicts in:\n - block/blk-cgroup.c\n\tSwitch from can_attach_task to can_attach\n - block/cfq-iosched.c\n\tconflict with now removed cic index changes (we now use q-\u003eid instead)\n" }, { "commit": "ec8013beddd717d1740cfefb1a9b900deef85462", "tree": "7aa28de51cb2f375baf6fe943afd85e75ca7bcb9", "parents": [ "0bfc96cb77224736dfa35c3c555d37b3646ef35e" ], "author": { "name": "Paolo Bonzini", "email": "pbonzini@redhat.com", "time": "Thu Jan 12 16:01:29 2012 +0100" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat Jan 14 15:07:24 2012 -0800" }, "message": "dm: do not forward ioctls from logical volumes to the underlying device\n\nA logical volume can map to just part of underlying physical volume.\nIn this case, it must be treated like a partition.\n\nBased on a patch from Alasdair G Kergon.\n\nCc: Alasdair G Kergon \u003cagk@redhat.com\u003e\nCc: dm-devel@redhat.com\nSigned-off-by: Paolo Bonzini \u003cpbonzini@redhat.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "c086ae4ed94f9a1d283318e006813268c2dbf9fc", "tree": "dbabbb09ddafcb818f32af038831419702574917", "parents": [ "7b67e751479d50b7f84d1a3cc5216eed5e534b66", "307729c8bc5b5a41361af8af95906eee7552acb1" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Wed Jan 11 18:51:55 2012 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Wed Jan 11 18:51:55 2012 -0800" }, "message": "Merge tag \u0027md-3.3-fixes\u0027 of git://neil.brown.name/md\n\nTwo bugfixes for md.\n\nOne is a recently introduced regression that affects an unusual\nconfiguration with a guaranteed BUG_ON. Has been tagged for -stable.\nThe other is minor missing functionality.\n\n* tag \u0027md-3.3-fixes\u0027 of git://neil.brown.name/md:\n md/raid1: perform bad-block tests for WriteMostly devices too.\n md: notify the \u0027degraded\u0027 sysfs attribute on failure.\n" }, { "commit": "b1bd055d397e09f99dcef9b138ed104ff1812fcb", "tree": "e8e1d3d0b6a33859392bcba516933aff256dc4b4", "parents": [ "c98b2cc29af8e84e7364b53e9bb4cc7cfaf62555" ], "author": { "name": "Martin K. Petersen", "email": "martin.petersen@oracle.com", "time": "Wed Jan 11 16:27:11 2012 +0100" }, "committer": { "name": "Jens Axboe", "email": "axboe@kernel.dk", "time": "Wed Jan 11 16:27:11 2012 +0100" }, "message": "block: Introduce blk_set_stacking_limits function\n\nStacking driver queue limits are typically bounded exclusively by the\ncapabilities of the low level devices, not by the stacking driver\nitself.\n\nThis patch introduces blk_set_stacking_limits() which has more liberal\nmetrics than the default queue limits function. This allows us to\ninherit topology parameters from bottom devices without manually\ntweaking the default limits in each driver prior to calling the stacking\nfunction.\n\nSince there is now a clear distinction between stacking and low-level\ndevices, blk_set_default_limits() has been modified to carry the more\nconservative values that we used to manually set in\nblk_queue_make_request().\n\nSigned-off-by: Martin K. Petersen \u003cmartin.petersen@oracle.com\u003e\nAcked-by: Mike Snitzer \u003csnitzer@redhat.com\u003e\nSigned-off-by: Jens Axboe \u003caxboe@kernel.dk\u003e\n" }, { "commit": "307729c8bc5b5a41361af8af95906eee7552acb1", "tree": "9b20fe9c898ee4de85b64a8e41c92123dae0b093", "parents": [ "f2a371c5e74dd5685ab47effa4ac7b23b1fdaae5" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jan 09 01:41:51 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Jan 11 08:35:17 2012 +1100" }, "message": "md/raid1: perform bad-block tests for WriteMostly devices too.\n\nWe normally try to avoid reading from write-mostly devices, but when\nwe do we really have to check for bad blocks and be sure not to\ntry reading them.\n\nWith the current code, best_good_sectors might not get set and that\ncauses zero-length read requests to be send down which is very\nconfusing.\n\nThis bug was introduced in commit d2eb35acfdccbe2 and so the patch\nis suitable for 3.1.x and 3.2.x\n\nReported-and-tested-by: Michał Mirosław \u003cmirq-linux@rere.qmqm.pl\u003e\nReported-and-tested-by: Art -kwaak- van Breemen \u003card@telegraafnet.nl\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nCc: stable@vger.kernel.org\n" }, { "commit": "f2a371c5e74dd5685ab47effa4ac7b23b1fdaae5", "tree": "e1960be50588ef0a4461fa54609df7ebea95eac5", "parents": [ "19d671695e1931ebfd75b2b888778201aefe35ca" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jan 09 00:46:41 2012 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Jan 11 08:35:14 2012 +1100" }, "message": "md: notify the \u0027degraded\u0027 sysfs attribute on failure.\n\nWe currently only \u0027notify\u0027 changes to the \u0027degraded\u0027 attribute\nwhen it decreases, not when it increases.\n\nNotifying on failure is a little awkward as it happen in\ninterrupt context.\nSo instead, notify when we remove the failed device from the array,\nwhich is very soon afterwards.\n\nReported-and-tested-by: Mikhail Balabin \u003cmbalabin@gmail.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "2943c833222ef87c111ee0c6b7b8519ad2983e99", "tree": "0ef8cc4f72a63b325e7ae858ec68822ec4f3c64f", "parents": [ "98793265b429a3f0b3f1750e74d67cd4d740d162", "19d671695e1931ebfd75b2b888778201aefe35ca" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Jan 08 13:28:33 2012 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sun Jan 08 13:28:33 2012 -0800" }, "message": "Merge tag \u0027md-3.3\u0027 of git://neil.brown.name/md\n\nmd update for 3.3\n\nBig change is new hot-replacement.\nA slot in an array can hold 2 devices - one that\nwants-replacement and one that is the replacement.\nOnce the replacement is built - either from the\noriginal or (in the case of errors) from elsewhere,\nthe wants-replacement device will be removed.\n\n* tag \u0027md-3.3\u0027 of git://neil.brown.name/md: (36 commits)\n md/raid1: Mark device want_replacement when we see a write error.\n md/raid1: If there is a spare and a want_replacement device, start replacement.\n md/raid1: recognise replacements when assembling arrays.\n md/raid1: handle activation of replacement device when recovery completes.\n md/raid1: Allow a failed replacement device to be removed.\n md/raid1: Allocate spare to store replacement devices and their bios.\n md/raid1: Replace use of mddev-\u003eraid_disks with conf-\u003eraid_disks.\n md/raid10: If there is a spare and a want_replacement device, start replacement.\n md/raid10: recognise replacements when assembling array.\n md/raid10: Allow replacement device to be replace old drive.\n md/raid10: handle recovery of replacement devices.\n md/raid10: Handle replacement devices during resync.\n md/raid10: writes should get directed to replacement as well as original.\n md/raid10: allow removal of failed replacement devices.\n md/raid10: preferentially read from replacement device if possible.\n md/raid10: change read_balance to return an rdev\n md/raid10: prepare data structures for handling replacement.\n md/raid5: Mark device want_replacement when we see a write error.\n md/raid5: If there is a spare and a want_replacement device, start replacement.\n md/raid5: recognise replacements when assembling array.\n ...\n" }, { "commit": "ff01bb4832651c6d25ac509a06a10fcbd75c461c", "tree": "bbfdebd317db97d346df78293566f36e883b1be9", "parents": [ "94ea4158f1733e3b10cef067d535f504866e0c41" ], "author": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Fri Sep 16 02:31:11 2011 -0400" }, "committer": { "name": "Al Viro", "email": "viro@zeniv.linux.org.uk", "time": "Tue Jan 03 22:54:07 2012 -0500" }, "message": "fs: move code out of buffer.c\n\nMove invalidate_bdev, block_sync_page into fs/block_dev.c. Export\nkill_bdev as well, so brd doesn\u0027t have to open code it. Reduce\nbuffer_head.h requirement accordingly.\n\nRemoved a rather large comment from invalidate_bdev, as it looked a bit\nobsolete to bother moving. The small comment replacing it says enough.\n\nSigned-off-by: Nick Piggin \u003cnpiggin@suse.de\u003e\nCc: Al Viro \u003cviro@ZenIV.linux.org.uk\u003e\nCc: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n" }, { "commit": "19d671695e1931ebfd75b2b888778201aefe35ca", "tree": "b3c54cdb0812632f830453b6a6c9b8b966c9dcc4", "parents": [ "7ef449d1ec3668acbba6af6a500d0c84636b436f" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:57 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:57 2011 +1100" }, "message": "md/raid1: Mark device want_replacement when we see a write error.\n\nNow that WantReplacement drives are replaced cleanly, mark a drive\nas want_replacement when we see a write error. It might get failed soon so\nthe WantReplacement flag is irrelevant, but if the write error is recorded\nin the bad block log, we still want to activate any spare that might\nbe available.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "7ef449d1ec3668acbba6af6a500d0c84636b436f", "tree": "4a9e23c9b88f404e896ba8748bdc7bb2b18ec65c", "parents": [ "c19d57980b38a5bb613a898937a1cf85f422fb9b" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:57 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:57 2011 +1100" }, "message": "md/raid1: If there is a spare and a want_replacement device, start replacement.\n\nWhen attempting to add a spare to a RAID1 array, also consider\nadding it as a replacement for a want_replacement device.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "c19d57980b38a5bb613a898937a1cf85f422fb9b", "tree": "ddc9f7ae53a4cd0464240ec8c49c03d35823a103", "parents": [ "8c7a2c2bcfaf0ee29c74437a4814d1aa780d6a26" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:57 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:57 2011 +1100" }, "message": "md/raid1: recognise replacements when assembling arrays.\n\nIf a Replacement is seen, file it as such.\n\nIf we see two replacements (or two normal devices) for the one slot,\nabort.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "8c7a2c2bcfaf0ee29c74437a4814d1aa780d6a26", "tree": "74093a74ea43965f04502bc5d71b6976a74c7305", "parents": [ "b014f14c81bc5db4e40e2a4db10998fd79c1c64c" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:57 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:57 2011 +1100" }, "message": "md/raid1: handle activation of replacement device when recovery completes.\n\nWhen recovery completes -\u003espare_active is called.\nThis checks if the replacement is ready and if so it fails\nthe original.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "b014f14c81bc5db4e40e2a4db10998fd79c1c64c", "tree": "78c5499e8af9a3e850ca2f93d215c53d55c40003", "parents": [ "8f19ccb2fd70deb1f278be5e75076074cfddee46" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:56 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:56 2011 +1100" }, "message": "md/raid1: Allow a failed replacement device to be removed.\n\nReplacement devices are stored at a different offset, so look\nthere too.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "8f19ccb2fd70deb1f278be5e75076074cfddee46", "tree": "59419e814d4d02dfdefaf6f5ef152c3468c890e8", "parents": [ "301946364e0aa67c4cfaec82e94c389993c9f7c6" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:56 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:56 2011 +1100" }, "message": "md/raid1: Allocate spare to store replacement devices and their bios.\n\nIn RAID1, a replacement is much like a normal device, so we just\ndouble the size of the relevant arrays and look at all possible\ndevices for reads and writes.\n\nThis means that the array looks like it is now double the size in some\nway - we need to be careful about that.\nIn particular, we checking if the array is still degraded while\ncreating a recovery request we need to only consider the first \u0027half\u0027\n- i.e. the real (non-replacement) devices.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "301946364e0aa67c4cfaec82e94c389993c9f7c6", "tree": "fff6390d22ba68f6726700cd4979f0de4c205a6f", "parents": [ "b7044d41b5a09ce9082699f74c8f10e0fe59f704" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:56 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:56 2011 +1100" }, "message": "md/raid1: Replace use of mddev-\u003eraid_disks with conf-\u003eraid_disks.\n\nIn general mddev-\u003eraid_disks can change unexpectedly while\nconf-\u003eraid_disks will only change in a very controlled way. So change\nsome uses of one to the other.\n\nThe use of mddev-\u003eraid_disks will not cause actually problems but\nthis way is more consistent and safer in the long term.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "b7044d41b5a09ce9082699f74c8f10e0fe59f704", "tree": "6eccbaddb40861aeba8459cb4f0efe3c340fb936", "parents": [ "56a2559bb654ae2555b2ae3b29c837615d0c45c9" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:56 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:56 2011 +1100" }, "message": "md/raid10: If there is a spare and a want_replacement device, start replacement.\n\nWhen attempting to add a spare to a RAID10 array, also consider\nadding it as a replacement for a want_replacement device.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "56a2559bb654ae2555b2ae3b29c837615d0c45c9", "tree": "f90a0d605260f668ad13af654f7951bcb27dfe64", "parents": [ "4ca40c2ce099e4f1ce35445994f49836662596c8" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:55 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:55 2011 +1100" }, "message": "md/raid10: recognise replacements when assembling array.\n\nIf a Replacement is seen, file it as such.\n\nIf we see two replacements (or two normal devices) for the one slot,\nabort.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "4ca40c2ce099e4f1ce35445994f49836662596c8", "tree": "7d6f2187e8d6aaab0cdcf4924017aeb9725d87b0", "parents": [ "24afd80d99f80a79d8824d2805114b8b067e9823" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:55 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:55 2011 +1100" }, "message": "md/raid10: Allow replacement device to be replace old drive.\n\nWhen recovery finish and spare_active is called, check for a\nreplace that might have just become fully synced and mark it\nas such, marking the original as failed.\n\nThen when the original is removed, move the replacement into\nits position.\n\nThis means that \u0027replacement\u0027 and spontaneously become NULL in some\nsituations. Make sure we check for those.\nIt also means that \u0027rdev\u0027 and \u0027replacement\u0027 could appear to be\nidentical - check for that too.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "24afd80d99f80a79d8824d2805114b8b067e9823", "tree": "c4ba36331ee56c64ba74a69ec5d0b56b6e860832", "parents": [ "9ad1aefc8ae8d2e482b4cc4b7199e2354148bbdc" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:55 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:55 2011 +1100" }, "message": "md/raid10: handle recovery of replacement devices.\n\nIf there is a replacement device, then recover to it,\nreading from any drives - maybe the one being replaced, maybe not.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "9ad1aefc8ae8d2e482b4cc4b7199e2354148bbdc", "tree": "c501f70c4726aade7eec3d743741f1568bba41df", "parents": [ "475b0321a4df381f64db10ddd750a8b7bb82d88b" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:55 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:55 2011 +1100" }, "message": "md/raid10: Handle replacement devices during resync.\n\nIf we need to resync an array which has replacement devices,\nwe always write any block checked to every replacement.\n\nIf the resync was bitmap-based resync we will then complete the\nreplacement normally.\nIf it was a full resync, we mark the replacements as fully recovered\nwhen the resync finishes so no further recovery is needed.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "475b0321a4df381f64db10ddd750a8b7bb82d88b", "tree": "c8433c702892962091e617c83ada4560a208e4de", "parents": [ "c8ab903ea9d7309044910c33dc087418be84f9b5" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:55 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:55 2011 +1100" }, "message": "md/raid10: writes should get directed to replacement as well as original.\n\nWhen writing, we need to submit two writes, one to the original,\nand one to the replacements - if there is a replacement.\n\nIf the write to the replacement results in a write error we just\nfail the device. We only try to record write errors to the\noriginal.\n\nThis only handles writing new data. Writing for resync/recovery\nwill come later.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "c8ab903ea9d7309044910c33dc087418be84f9b5", "tree": "1113f320a71e50bc5ed22b7f6ca0ec1800b37b08", "parents": [ "abbf098e6e1e23d5d247b9eaaf325e67f67b0328" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:54 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:54 2011 +1100" }, "message": "md/raid10: allow removal of failed replacement devices.\n\nEnhance raid10_remove_disk to be able to remove -\u003ereplacement\nas well as -\u003erdev\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "abbf098e6e1e23d5d247b9eaaf325e67f67b0328", "tree": "e2d8dc88c99ecc14d6d87596d95b3de9b9dc87c9", "parents": [ "96c3fd1f3802371610c620cff03f9d825707e80e" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:54 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:54 2011 +1100" }, "message": "md/raid10: preferentially read from replacement device if possible.\n\nWhen reading (for array reads, not for recovery etc) we read from the\nreplacement device if it has recovered far enough.\nThis requires storing the chosen rdev in the \u0027r10_bio\u0027 so we can make\nsure to drop the ref on the right device when the read finishes.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "96c3fd1f3802371610c620cff03f9d825707e80e", "tree": "822e95ed42ca9d1526964b3d06ef66ec4edd0ab9", "parents": [ "69335ef3bc5b766f34db2d688be1d35313138bca" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:54 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:54 2011 +1100" }, "message": "md/raid10: change read_balance to return an rdev\n\nIt makes more sense to return an rdev than just an index as\nread_balance() gets a reference to the rdev and so returning\nthe pointer make this more idiomatic.\n\nThis will be needed in a future patch when we might return\na \u0027replacement\u0027 rdev instead of the main rdev.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "69335ef3bc5b766f34db2d688be1d35313138bca", "tree": "dcd87ffc4c97540d374a20de7380368e3679ac3b", "parents": [ "3a6de2924af602f9c1b5a5154438c37f2d712dfa" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:54 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:54 2011 +1100" }, "message": "md/raid10: prepare data structures for handling replacement.\n\nAllow each slot in the RAID10 to have 2 devices, the want_replacement\nand the replacement.\n\nAlso an r10bio to have 2 bios, and for resync/recovery allocate the\nsecond bio if there are any replacement devices.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "3a6de2924af602f9c1b5a5154438c37f2d712dfa", "tree": "895462dfefd70827c5b6d860503d1244d003a56e", "parents": [ "7bfec5f35c68121e7b1849f3f4166dd96c8da5b3" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:54 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:54 2011 +1100" }, "message": "md/raid5: Mark device want_replacement when we see a write error.\n\nNow that WantReplacement drives are replaced cleanly, mark a drive\nas WantReplacement when we see a write error. It might get failed soon so\nthe WantReplacement flag is irrelevant, but if the write error is recorded\nin the bad block log, we still want to activate any spare that might\nbe available.\n\nReviewed-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "7bfec5f35c68121e7b1849f3f4166dd96c8da5b3", "tree": "14bab6480ccc14a6cdf9e5ee34662897e5e2e94a", "parents": [ "17045f52ac76d9cd1a120e52af5d83b570af4ba8" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:53 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:53 2011 +1100" }, "message": "md/raid5: If there is a spare and a want_replacement device, start replacement.\n\nWhen attempting to add a spare to a RAID[456] array, also consider\nadding it as a replacement for a want_replacement device.\n\nThis requires that common md code attempt hot_add even when the array\nis not formally degraded.\n\nReviewed-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "17045f52ac76d9cd1a120e52af5d83b570af4ba8", "tree": "2bbd692eaab68ffa60f3dcf6757752b9b89a7a9b", "parents": [ "dd054fce88d33da1aa81d018db75b91b102a6959" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:53 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:53 2011 +1100" }, "message": "md/raid5: recognise replacements when assembling array.\n\nIf a Replacement is seen, file it as such.\n\nIf we see two replacements (or two normal devices) for the one slot,\nabort.\n\nReviewed-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "dd054fce88d33da1aa81d018db75b91b102a6959", "tree": "9528caece6b444ebcdb41453b60a1bb4054a1a4d", "parents": [ "9a3e1101b827a59ac9036a672f5fa8d5279d0fe2" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:53 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:53 2011 +1100" }, "message": "md/raid5: handle activation of replacement device when recovery completes.\n\nWhen recovery completes - as reported by a call to -\u003espare_active,\nwe clear In_sync on the original and set it on the replacement.\n\nThen when the original gets removed we move the replacement from\n\u0027replacement\u0027 to \u0027rdev\u0027.\n\nThis could race with other code that is looking at these pointers,\nso we use memory barriers and careful ordering to ensure that\na reader might see one device twice, but never no devices.\nThen the readers guard against using both devices, which could\nonly happen when writing.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "9a3e1101b827a59ac9036a672f5fa8d5279d0fe2", "tree": "9e629fbc1bab31b588c475181246bbe30778f67a", "parents": [ "977df36255ab0ea78b048cbc9055300c586dcc91" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:53 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:53 2011 +1100" }, "message": "md/raid5: detect and handle replacements during recovery.\n\nDuring recovery we want to write to the replacement but not\nthe original. So we have two new flags\n - R5_NeedReplace if this stripe has a replacement that needs to\n be written at some stage\n - R5_WantReplace if NeedReplace, and the data is available, and\n a \u0027sync\u0027 has been requested on this stripe.\n\nWe also distinguish between \u0027sync and replace\u0027 which need to read\nall other devices, and \u0027replace\u0027 which only needs to read the\ndevices being replaced.\n\nNote that during resync we always write to any replacement device.\nIt might not need to be written to, but as we don\u0027t read to compare,\nwe have to write to be sure.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "977df36255ab0ea78b048cbc9055300c586dcc91", "tree": "6d89e08ebe7702ccbb5e160b99ea2440ab08fcda", "parents": [ "657e3e4d88461a5ab660dd87f8f773f55e748da4" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:53 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:53 2011 +1100" }, "message": "md/raid5: writes should get directed to replacement as well as original.\n\nWhen writing, we need to submit two writes, one to the original, and\none to the replacement - if there is a replacement.\n\nIf the write to the replacement results in a write error, we just fail\nthe device. We only try to record write errors to the original.\n\nWhen writing for recovery, we shouldn\u0027t write to the original. This\nwill be addressed in a subsequent patch that generally addresses\nrecovery.\n\nReviewed-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "657e3e4d88461a5ab660dd87f8f773f55e748da4", "tree": "1eecf97f8e5eac95cf37b4f28e262a37dd3e116d", "parents": [ "14a75d3e07c784c004b4b44b34af996b8e4ac453" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:52 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:52 2011 +1100" }, "message": "md/raid5: allow removal for failed replacement devices.\n\nEnhance raid5_remove_disk to be able to remove -\u003ereplacement\nas well as -\u003erdev.\n\nReviewed-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "14a75d3e07c784c004b4b44b34af996b8e4ac453", "tree": "6009e1ccc1b766d4c55434e3b4c1d171b8a2c004", "parents": [ "995c4275a7e14b8752f301e4570831a108ae4303" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:52 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:52 2011 +1100" }, "message": "md/raid5: preferentially read from replacement device if possible.\n\nIf a replacement device is present and has been recovered far enough,\nthen use it for reading into the stripe cache.\n\nIf we get an error we don\u0027t try to repair it, we just fail the device.\nA replacement device that gives errors does not sound sensible.\n\nThis requires removing the setting of R5_ReadError when we get\na read error during a read that bypasses the cache. It was probably\na bad idea anyway as we don\u0027t know that every block in the read\ncaused an error, and it could cause ReadError to be set for the\nreplacement device, which is bad.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "995c4275a7e14b8752f301e4570831a108ae4303", "tree": "2bee4c8daf14b6453371bb348b18d37d7e3cdb07", "parents": [ "ede7ee8b4d007f308aa033be676b1a048f99e9db" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:52 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:52 2011 +1100" }, "message": "md/raid5: remove redundant bio initialisations.\n\nWe current initialise some fields of a bio when preparing a\nstripe_head, and again just before submitting the request.\n\nRemove the duplication by only setting the fields that lower level\ndevices don\u0027t touch in raid5_build_block, and only set the changeable\nfields in ops_run_io.\n\nReviewed-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "ede7ee8b4d007f308aa033be676b1a048f99e9db", "tree": "2ce0dad4009b0f05617976034686855883f382bd", "parents": [ "671488cc25f7c194c7c7a9f258bab1df17a6ff69" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:52 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:52 2011 +1100" }, "message": "md/raid5: raid5.h cleanup\n\nRemove some #defines that are no longer used, and replace some\nothers with an enum.\nAnd remove an unused field.\n\nReviewed-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "671488cc25f7c194c7c7a9f258bab1df17a6ff69", "tree": "00bec63c7789dbf7439418ee903490d6ee076a70", "parents": [ "2d78f8c451785f030ac1676a18691896b59c69d8" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:52 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:52 2011 +1100" }, "message": "md/raid5: allow each slot to have an extra replacement device\n\nJust enhance data structures to record a second device per slot to be\nused as a \u0027replacement\u0027 device, replacing the original.\nWe also have a second bio in each slot in each stripe_head. This will\nonly be used when writing to the array - we need to write to both the\noriginal and the replacement at the same time, so will need two bios.\n\nFor now, only try using the replacement drive for aligned-reads.\nIn this case, we prefer the replacement if it has been recovered far\nenough, otherwise use the original.\n\nThis includes a small enhancement. Previously we would only do\naligned reads if the target device was fully recovered. Now we also\ndo them if it has recovered far enough.\n\nReviewed-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "2d78f8c451785f030ac1676a18691896b59c69d8", "tree": "4dfe69115b2ca2fb8be2a671e7c8399c3925fcb9", "parents": [ "b8321b68d1445f308324517e45fb0a5c2b48e271" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:51 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:51 2011 +1100" }, "message": "md: create externally visible flags for supporting hot-replace.\n\nhot-replace is a feature being added to md which will allow a\ndevice to be replaced without removing it from the array first.\n\nWith hot-replace a spare can be activated and recovery can start while\nthe original device is still in place, thus allowing a transition from\nan unreliable device to a reliable device without leaving the array\ndegraded during the transition. It can also be use when the original\ndevice is still reliable but it not wanted for some reason.\n\nThis will eventually be supported in RAID4/5/6 and RAID10.\n\nThis patch adds a super-block flag to distinguish the replacement\ndevice. If an old kernel sees this flag it will reject the device.\n\nIt also adds two per-device flags which are viewable and settable via\nsysfs.\n \"want_replacement\" can be set to request that a device be replaced.\n \"replacement\" is set to show that this device is replacing another\n device.\n\nThe \"rd%d\" links in /sys/block/mdXx/md only apply to the original\ndevice, not the replacement. We currently don\u0027t make links for the\nreplacement - there doesn\u0027t seem to be a need.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "b8321b68d1445f308324517e45fb0a5c2b48e271", "tree": "3fc4c9b253435753d2154d9bd697a7869163c29a", "parents": [ "476a7abb9b00adfe6bf70e82800367319ab8078b" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:51 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:51 2011 +1100" }, "message": "md: change hot_remove_disk to take an rdev rather than a number.\n\nSoon an array will be able to have multiple devices with the\nsame raid_disk number (an original and a replacement). So removing\na device based on the number won\u0027t work. So pass the actual device\nhandle instead.\n\nReviewed-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "476a7abb9b00adfe6bf70e82800367319ab8078b", "tree": "92387465b8ded45abad9dbb7382136476a31e120", "parents": [ "915c420ddfa3eb22a0dbdb7a8e0ecf020c31961f" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:51 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:51 2011 +1100" }, "message": "md: remove test for duplicate device when setting slot number.\n\nWhen setting the slot number on a device in an active array we\ncurrently check that the number is not already in use.\nWe then call into the personality\u0027s hot_add_disk function\nwhich performs the same test and returns the same error.\n\nThus the common test is not needed.\n\nAs we will shortly be changing some personalities to allow duplicates\nin some cases (to support hot-replace), the common test will become\ninconvenient.\n\nSo remove the common test.\n\nReviewed-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "915c420ddfa3eb22a0dbdb7a8e0ecf020c31961f", "tree": "24915c8f3380e390130d1d437389b5cb805c28fd", "parents": [ "38059ec2bd2ce9e4709f49f34795aa0944287908" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:51 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:51 2011 +1100" }, "message": "md/bitmap: be more consistent when setting new bits in memory bitmap.\n\nFor each active region corresponding to a bit in the bitmap with have\na 14bit counter (and some flags).\nThis counts\n number of active writes + bit in the on-disk bitmap + delay-needed.\n\nThe \"delay-needed\" is because we always want a delay before clearing a\nbit. So the number here is normally number of active writes plus 2.\nIf there have been no writes for a while, we drop to 1.\nIf still no writes we clear the bit and drop to 0.\n\nSo for consistency, when setting bit from the on-disk bitmap or by\nrequest from user-space it is best to set the counter to \u00272\u0027 to start\nwith.\n\nIn particular we might also set the NEEDED_MASK flag at this time, and\nin all other cases NEEDED_MASK is only set when the counter is 2 or\nmore.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "908f4fbd265733310c17ecc906299846b5dac44a", "tree": "71e364c57887213431143e6fd1296e8433cc6293", "parents": [ "2e61ebbcc45438899235d7a39f17291cb24e746c" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:50 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:50 2011 +1100" }, "message": "md/raid5: be more thorough in calculating \u0027degraded\u0027 value.\n\nWhen an array is being reshaped to change the number of devices,\nthe two halves can be differently degraded. e.g. one could be\nmissing a device and the other not.\n\nSo we need to be more careful about calculating the \u0027degraded\u0027\nattribute.\n\nInstead of just inc/dec at appropriate times, perform a full\nre-calculation examining both possible cases. This doesn\u0027t happen\noften so it not a big cost, and we already have most of the code to\ndo it.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "2e61ebbcc45438899235d7a39f17291cb24e746c", "tree": "9d12a2a641c9980fb08f704449631d8012db0686", "parents": [ "506c9e44a85f6a79fc0643f2d2498ab6cda3d3f8" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:50 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:50 2011 +1100" }, "message": "md/bitmap: daemon_work cleanup.\n\nWe have a variable \u0027mddev\u0027 in this function, but repeatedly get the\nsame value by dereferencing bitmap-\u003emddev.\nThere is room for simplification here...\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "506c9e44a85f6a79fc0643f2d2498ab6cda3d3f8", "tree": "94dd7741a688b2c57494819ca3a22d228462ff98", "parents": [ "961902c0f8240175729274cd14198872f42072b7" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:26 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 10:17:26 2011 +1100" }, "message": "md: allow non-privileged uses to GET_*_INFO about raid arrays.\n\nThe info is already available in /proc/mdstat and /sys/block in\nan accessible form so there is no point in putting a road-block in\nthe ioctl for information gathering.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "961902c0f8240175729274cd14198872f42072b7", "tree": "808b47d32174e970465dc00cea9150ff978bfc95", "parents": [ "60fc13702a1b35118c1548e9c257fa038cecb658" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 09:57:48 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 09:57:48 2011 +1100" }, "message": "md/bitmap: It is OK to clear bits during recovery.\n\ncommit d0a4bb492772ce5c4bdfba3744a99ed6f6fb238f introduced a\nregression which is annoying but fairly harmless.\n\nWhen writing to an array that is undergoing recovery (a spare\nin being integrated into the array), writing to the array will\nset bits in the bitmap, but they will not be cleared when the\nwrite completes.\n\nFor bits covering areas that have not been recovered yet this is not a\nproblem as the recovery will clear the bits. However bits set in\nalready-recovered region will stay set and never be cleared.\nThis doesn\u0027t risk data integrity. The only negatives are:\n - next time there is a crash, more resyncing than necessary will\n be done.\n - the bitmap doesn\u0027t look clean, which is confusing.\n\nWhile an array is recovering we don\u0027t want to update the\n\u0027events_cleared\u0027 setting in the bitmap but we do still want to clear\nbits that have very recently been set - providing they were written to\nthe recovering device.\n\nSo split those two needs - which previously both depended on \u0027success\u0027\nand always clear the bit of the write went to all devices.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "60fc13702a1b35118c1548e9c257fa038cecb658", "tree": "163094eb4ae229f9263bfd05b788f29cc14e94f5", "parents": [ "30d7a4836847bdb10b32c78a4879d4aebe0f193b" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 09:57:19 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 09:57:19 2011 +1100" }, "message": "md: don\u0027t give up looking for spares on first failure-to-add\n\nBefore performing a recovery we try to remove any spares that\nmight not be working, then add any that might have become relevant.\n\nCurrently we abort on the first spare that cannot be added.\nThis is a false optimisation.\nIt is conceivable that - depending on rules in the personality - a\nsubsequent spare might be accepted.\nAlso the loop does other things like count the available spares and\nreset the \u0027recovery_offset\u0027 value.\n\nIf we abort early these might not happen properly.\n\nSo remove the early abort.\n\nIn particular if you have an array what is undergoing recovery and\nwhich has extra spares, then the recovery may not restart after as\nreboot as the could of \u0027spares\u0027 might end up as zero.\n\nReported-by: Anssi Hannula \u003canssi.hannula@iki.fi\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "30d7a4836847bdb10b32c78a4879d4aebe0f193b", "tree": "039d4eaec57d67cbfc49d92f12e592b46c251c01", "parents": [ "09cd9270ea52e0f9851528e8ed028073f96b3c34" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 09:57:00 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 09:57:00 2011 +1100" }, "message": "md/raid5: ensure correct assessment of drives during degraded reshape.\n\nWhile reshaping a degraded array (as when reshaping a RAID0 by first\nconverting it to a degraded RAID4) we currently get confused about\nwhich devices are in_sync. In most cases we get it right, but in the\nregion that is being reshaped we need to treat non-failed devices as\nin-sync when we have the data but haven\u0027t actually written it out yet.\n\nReported-by: Adam Kwolek \u003cadam.kwolek@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "09cd9270ea52e0f9851528e8ed028073f96b3c34", "tree": "8cfb20f05531dc1e83c7d295e6b59dd692bdf99d", "parents": [ "5d8c71f9e5fbdd95650be00294d238e27a363b5c" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 09:56:55 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 23 09:56:55 2011 +1100" }, "message": "md/linear: fix hot-add of devices to linear arrays.\n\ncommit d70ed2e4fafdbef0800e73942482bb075c21578b\nbroke hot-add to a linear array.\nAfter that commit, metadata if not written to devices until they\nhave been fully integrated into the array as determined by\nsaved_raid_disk. That patch arranged to clear that field after\na recovery completed.\n\nHowever for linear arrays, there is no recovery - the integration is\ninstantaneous. So we need to explicitly clear the saved_raid_disk\nfield.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "5d8c71f9e5fbdd95650be00294d238e27a363b5c", "tree": "51f7ae70b3a188f8376d7912493d346537fe516e", "parents": [ "9283d8c5af4cdcb809e655acdf4be368afec8b58" ], "author": { "name": "Adam Kwolek", "email": "adam.kwolek@intel.com", "time": "Fri Dec 09 14:26:11 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Dec 09 14:26:11 2011 +1100" }, "message": "md: raid5 crash during degradation\n\nNULL pointer access causes crash in raid5 module.\n\nSigned-off-by: Adam Kwolek \u003cadam.kwolek@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "9283d8c5af4cdcb809e655acdf4be368afec8b58", "tree": "d4baa86260792a10782808e51d5468e145358980", "parents": [ "8bd2f0a05b361e07d48bb34398593f5f523946b3" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Dec 08 16:27:57 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Dec 08 16:27:57 2011 +1100" }, "message": "md/raid5: never wait for bad-block acks on failed device.\n\nOnce a device is failed we really want to completely ignore it.\nIt should go away soon anyway.\n\nIn particular the presence of bad blocks on it should not cause us to\nblock as we won\u0027t be trying to write there anyway.\n\nSo as soon as we can check if a device is Faulty, do so and pretend\nthat it is already gone if it is Faulty.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "8bd2f0a05b361e07d48bb34398593f5f523946b3", "tree": "a87860b4b8821b40eb9e6bb5333f71dfa8c3fb39", "parents": [ "52c64152a935e63d9ff73ce823730c9a23dedbff" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Dec 08 16:26:08 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Dec 08 16:26:08 2011 +1100" }, "message": "md: ensure new badblocks are handled promptly.\n\nWhen we mark blocks as bad we need them to be acknowledged by the\nmetadata handler promptly.\n\nFor an in-kernel metadata handler that was already being done. But\nfor an external metadata handler we need to alert it of the change by\nsending a notification through the sysfs file. This adds that\nnotification.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "52c64152a935e63d9ff73ce823730c9a23dedbff", "tree": "03de10a1899d74b42d00740437140a032686d011", "parents": [ "af8a24347f966ab9fae6b0f127d1fbc9d6932d3a" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Dec 08 16:22:48 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Dec 08 16:22:48 2011 +1100" }, "message": "md: bad blocks shouldn\u0027t cause a Blocked status on a Faulty device.\n\nOnce a device is marked Faulty the badblocks - whether acknowledged or\nnot - become irrelevant. So they shouldn\u0027t cause the device to be\nmarked as Blocked.\n\nWithout this patch, a process might write \"-blocked\" to clear the\nBlocked status, but while that will correctly fail the device, it\nwon\u0027t remove the apparent \u0027blocked\u0027 status.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "af8a24347f966ab9fae6b0f127d1fbc9d6932d3a", "tree": "903afdae95dc11444707410d784ad857dfb887c9", "parents": [ "1d23f178d56ae1349b4fc5108ac8f4f8cdc92afc" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Dec 08 15:49:46 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Dec 08 15:49:46 2011 +1100" }, "message": "md: take a reference to mddev during sysfs access.\n\n\nWhen we are accessing an mddev via sysfs we know that the\nmddev cannot disappear because it has an embedded kobj which\nis refcounted by sysfs.\nAnd we also take the mddev_lock.\nHowever this is not enough.\n\nThe final mddev_put could have been called and the\nmddev_delayed_delete is waiting for sysfs to let go so it can destroy\nthe kobj and mddev.\nIn this state there are a lot of changes that should not be attempted.\n\nTo to guard against this we:\n - initialise mddev-\u003eall_mddevs in on last put so the state can be\n easily detected.\n - in md_attr_show and md_attr_store, check -\u003eall_mddevs under\n all_mddevs_lock and mddev_get the mddev if it still appears to\n be active.\n\nThis means that if we get to sysfs as the mddev is being deleted we\nwill get -EBUSY.\n\nrdev_attr_store and rdev_attr_show are similar but already have\nsufficient protection. They check that rdev-\u003emddev still points to\nmddev after taking mddev_lock. As this is cleared before delayed\nremoval which can only be requested under the mddev_lock, this\nensure the rdev and mddev are still alive.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "1d23f178d56ae1349b4fc5108ac8f4f8cdc92afc", "tree": "3be282873c611cab1e855e0991ee3620d4cb906b", "parents": [ "7c8f4247986bb5c5fb1d5b1fad35461989fe8310" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Dec 08 15:49:12 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Dec 08 15:49:12 2011 +1100" }, "message": "md: refine interpretation of \"hold_active \u003d\u003d UNTIL_IOCTL\".\n\nWe like md devices to disappear when they really are not needed.\nHowever it is not possible to tell from the current state whether it\nis needed or not. We can only tell from recent history of changes.\n\nIn particular immediately after we create an md device it looks very\nsimilar to immediately after we have finished with it.\n\nSo we always preserve a newly created md device until something\nsignificant happens. This state is stored in \u0027hold_active\u0027.\n\nThe normal case is to keep it until an ioctl happens, as that will\nnormally either activate it, or explicitly de-activate it. If it\ndoesn\u0027t then it was probably created by mistake and it is now time to\nget rid of it.\n\nWe can also modify an array via sysfs (instead of via ioctl) and we\ncurrently treat any change via sysfs like an ioctl as a sign that if\nit now isn\u0027t more active, it should be destroyed.\nHowever this is not appropriate as changes made via sysfs are more\ngradual so we should look for a more definitive change.\n\nSo this patch only clears \u0027hold_active\u0027 from UNTIL_IOCTL to clear when\nthe array_state is changed via sysfs. Other changes via sysfs\nare ignored.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "7c8f4247986bb5c5fb1d5b1fad35461989fe8310", "tree": "2c76f387184ac0cc587e66519536fc83e0f79553", "parents": [ "257a4b42af7586fab4eaec7f04e6896b86551843" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Nov 23 10:18:52 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Nov 23 10:18:52 2011 +1100" }, "message": "md/lock: ensure updates to page_attrs are properly locked.\n\nPage attributes are set using __set_bit rather than set_bit as\nit normally called under a spinlock so the extra atomicity is not\nneeded.\n\nHowever there are two places where we might set or clear page\nattributes without holding the spinlock.\nSo add the spinlock in those cases.\n\nThis might be the cause of occasional reports that bits a aren\u0027t\ngetting clear properly - theory is that BITMAP_PAGE_PENDING gets lost\nwhen BITMAP_PAGE_NEEDWRITE is set or cleared. This is an\ninconvenience, not a threat to data safety.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "257a4b42af7586fab4eaec7f04e6896b86551843", "tree": "ec65357b2320ba4e4341a2853245048889666f5c", "parents": [ "9a3f530f39f4490eaa18b02719fb74ce5f4d2d86" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Tue Nov 08 16:22:06 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Nov 08 16:22:06 2011 +1100" }, "message": "md/raid5: STRIPE_ACTIVE has lock semantics, add barriers\n\nAll updates that occur under STRIPE_ACTIVE should be globally visible\nwhen STRIPE_ACTIVE clears. test_and_set_bit() implies a barrier, but\nclear_bit() does not.\n\nThis is suitable for 3.1-stable.\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nCc: stable@kernel.org\n" }, { "commit": "9a3f530f39f4490eaa18b02719fb74ce5f4d2d86", "tree": "4bcff31bacd9b242360f48dad706d8b5231ffafe", "parents": [ "1ea6b8f48918282bdca0b32a34095504ee65bab5" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Nov 08 16:22:01 2011 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Nov 08 16:22:01 2011 +1100" }, "message": "md/raid5: abort any pending parity operations when array fails.\n\nWhen the number of failed devices exceeds the allowed number\nwe must abort any active parity operations (checks or updates) as they\nare no longer meaningful, and can lead to a BUG_ON in\nhandle_parity_checks6.\n\nThis bug was introduce by commit 6c0069c0ae9659e3a91b68eaed06a5c6c37f45c8\nin 2.6.29.\n\nReported-by: Manish Katiyar \u003cmkatiyar@gmail.com\u003e\nTested-by: Manish Katiyar \u003cmkatiyar@gmail.com\u003e\nAcked-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nCc: stable@kernel.org\n" } ], "next": "a84450604d0fe08b6a2335efbedede18d3d7cc75" }