)]}' { "log": [ { "commit": "7f8635cc9e66a26d7280ba680b044fa2f65104af", "tree": "0d8506e86d07e15c473aca1a09af7ad6ff7d8b49", "parents": [ "3cb50ddf97a0a1ca4c68bc12fa1e727a6b45fbf2", "0fc13c8995cd96f4123de400c71c223d80400ed9" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Dec 20 09:19:46 2010 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Dec 20 09:19:46 2010 -0800" }, "message": "Merge branch \u0027for-linus\u0027 of git://git.kernel.dk/linux-2.6-block\n\n* \u0027for-linus\u0027 of git://git.kernel.dk/linux-2.6-block:\n cciss: fix cciss_revalidate panic\n block: max hardware sectors limit wrapper\n block: Deprecate QUEUE_FLAG_CLUSTER and use queue_limits instead\n blk-throttle: Correct the placement of smp_rmb()\n blk-throttle: Trim/adjust slice_end once a bio has been dispatched\n block: check for proper length of iov entries earlier in blk_rq_map_user_iov()\n drbd: fix for spin_lock_irqsave in endio callback\n drbd: don\u0027t recvmsg with zero length\n" }, { "commit": "e692cb668fdd5a712c6ed2a2d6f2a36ee83997b4", "tree": "accf682fe5e1388f305b5fc364a931dfda5f3fb9", "parents": [ "04a6b516cdc6efc2500b52a540cf65be8c5aaf9e" ], "author": { "name": "Martin K. Petersen", "email": "martin.petersen@oracle.com", "time": "Wed Dec 01 19:41:49 2010 +0100" }, "committer": { "name": "Jens Axboe", "email": "jaxboe@fusionio.com", "time": "Fri Dec 17 08:35:53 2010 +0100" }, "message": "block: Deprecate QUEUE_FLAG_CLUSTER and use queue_limits instead\n\nWhen stacking devices, a request_queue is not always available. This\nforced us to have a no_cluster flag in the queue_limits that could be\nused as a carrier until the request_queue had been set up for a\nmetadevice.\n\nThere were several problems with that approach. First of all it was up\nto the stacking device to remember to set queue flag after stacking had\ncompleted. Also, the queue flag and the queue limits had to be kept in\nsync at all times. We got that wrong, which could lead to us issuing\ncommands that went beyond the max scatterlist limit set by the driver.\n\nThe proper fix is to avoid having two flags for tracking the same thing.\nWe deprecate QUEUE_FLAG_CLUSTER and use the queue limit directly in the\nblock layer merging functions. The queue_limit \u0027no_cluster\u0027 is turned\ninto \u0027cluster\u0027 to avoid double negatives and to ease stacking.\nClustering defaults to being enabled as before. The queue flag logic is\nremoved from the stacking function, and explicitly setting the cluster\nflag is no longer necessary in DM and MD.\n\nReported-by: Ed Lin \u003ced.lin@promise.com\u003e\nSigned-off-by: Martin K. Petersen \u003cmartin.petersen@oracle.com\u003e\nAcked-by: Mike Snitzer \u003csnitzer@redhat.com\u003e\nCc: stable@kernel.org\nSigned-off-by: Jens Axboe \u003cjaxboe@fusionio.com\u003e\n" }, { "commit": "589a594be1fb8815b3f18e517be696c48664f728", "tree": "9de6f6b4f9244802ccf77312f7fba8612dd13a75", "parents": [ "1a855a0606653d2d82506281e2c686bacb4b2f45" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Dec 09 17:02:14 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Dec 09 17:02:14 2010 +1100" }, "message": "md: protect against NULL reference when waiting to start a raid10.\n\nWhen we fail to start a raid10 for some reason, we call\nmd_unregister_thread to kill the thread that was created.\n\nUnfortunately md_thread() will then make one call into the handler\n(raid10d) even though md_wakeup_thread has not been called. This is\nnot safe and as md_unregister_thread is called after mddev-\u003eprivate\nhas been set to NULL, it will definitely cause a NULL dereference.\n\nSo fix this at both ends:\n - md_thread should only call the handler if THREAD_WAKEUP has been\n set.\n - raid10 should call md_unregister_thread before setting things\n to NULL just like all the other raid modules do.\n\nThis is applicable to 2.6.35 and later.\n\nCc: stable@kernel.org\nReported-by: \"Citizen\" \u003ccitizen_lee@thecus.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "1a855a0606653d2d82506281e2c686bacb4b2f45", "tree": "7eeca410e738491318c0d80bd0a0940c392e513f", "parents": [ "a035fc3e2531703b539f23bec4ca7943cfc69349" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Dec 09 16:36:28 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Dec 09 16:36:28 2010 +1100" }, "message": "md: fix bug with re-adding of partially recovered device.\n\nWith v0.90 metadata, a hot-spare does not become a full member of the\narray until recovery is complete. So if we re-add such a device to\nthe array, we know that all of it is as up-to-date as the event count\nwould suggest, and so it a bitmap-based recovery is possible.\n\nHowever with v1.x metadata, the hot-spare immediately becomes a full\nmember of the array, but it record how much of the device has been\nrecovered. If the array is stopped and re-assembled recovery starts\nfrom this point.\n\nWhen such a device is hot-added to an array we currently lose the \u0027how\nmuch is recovered\u0027 information and incorrectly included it as a full\nin-sync member (after bitmap-based fixup).\nThis is wrong and unsafe and could corrupt data.\n\nSo be more careful about setting saved_raid_disk - which is what\nguides the re-adding of devices back into an array.\nThe new code matches the code in slot_store which does a similar\nthing, which is encouraging.\n\nThis is suitable for any -stable kernel.\n\nReported-by: \"Dailey, Nate\" \u003cNate.Dailey@stratus.com\u003e\nCc: stable@kernel.org\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "a035fc3e2531703b539f23bec4ca7943cfc69349", "tree": "f10e160ce65745fd7ac56838c491a45ae180cb1e", "parents": [ "a7a07e69653acf8540daa1da053cd84bf86e8e66" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Dec 09 16:17:51 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Dec 09 16:17:51 2010 +1100" }, "message": "md: fix possible deadlock in handling flush requests.\n\nAs recorded in\n https://bugzilla.kernel.org/show_bug.cgi?id\u003d24012\n\nit is possible for a flush request through md to hang. This is due to\nan interaction between the recursion avoidance in\ngeneric_make_request, the insistence in md of only having one flush\nactive at a time, and the possibility of dm (or md) submitting two\nflush requests to a device from the one generic_make_request.\n\nIf a generic_make_request call into dm causes two flush requests to be\nqueued (as happens if the dm table has two targets - they get one\neach), these two will be queued inside generic_make_request.\n\nAssume they are for the same md device.\nThe first is processed and causes 1 or more flush requests to be sent\nto lower devices. These get queued within generic_make_request too.\nThen the second flush to the md device gets handled and it blocks\nwaiting for the first flush to complete. But it won\u0027t complete until\nthe two lower-device requests complete, and they haven\u0027t even been\nsubmitted yet as they are on the generic_make_request queue.\n\nThe deadlock can be broken by using a separate thread to submit the\nrequests to lower devices. md has such a thread readily available:\nmd_wq.\n\nSo use it to submit these requests.\n\nReported-by: Giacomo Catenazzi \u003ccate@cateee.net\u003e\nTested-by: Giacomo Catenazzi \u003ccate@cateee.net\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "a7a07e69653acf8540daa1da053cd84bf86e8e66", "tree": "edeb5ec7fc686c8699193338d3c3964aeb6279a8", "parents": [ "2b74e12e567feb4163e32815bce0be57489e73b9" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Dec 09 16:04:25 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Dec 09 16:04:25 2010 +1100" }, "message": "md: move code in to submit_flushes.\n\nsubmit_flushes is called from exactly one place.\nMove the code that is before and after that call into\nsubmit_flushes.\n\nThis has not functional change, but will make the next patch\nsmaller and easier to follow.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "2b74e12e567feb4163e32815bce0be57489e73b9", "tree": "2eef8f977209a7e5ff88b4366bd72ccf59c8a987", "parents": [ "be20e6c67b6c6024c19094d3447f144d118733b0" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Dec 09 15:59:01 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Dec 09 15:59:01 2010 +1100" }, "message": "md: remove handling of flush_pending in md_submit_flush_data\n\nNone of the functions called between setting flush_pending to 1, and\natomic_dec_and_test can change flush_pending, or will anything\nrunning in any other thread (as -\u003eflush_bio is not NULL). So the\natomic_dec_and_test will always succeed.\nSo remove the atomic_sec and the atomic_dec_and_test.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "be20e6c67b6c6024c19094d3447f144d118733b0", "tree": "170f7a810d5947cdba7edc965676ad7d5ea8948c", "parents": [ "8f9e0ee38f75d4740daa9e42c8af628d33d19a02" ], "author": { "name": "Darrick J. Wong", "email": "djwong@us.ibm.com", "time": "Wed Nov 24 16:40:33 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Nov 24 16:40:33 2010 +1100" }, "message": "md: Call blk_queue_flush() to establish flush/fua support\n\nBefore 2.6.37, the md layer had a mechanism for catching I/Os with the\nbarrier flag set, and translating the barrier into barriers for all\nthe underlying devices. With 2.6.37, I/O barriers have become plain\nold flushes, and the md code was updated to reflect this. However,\none piece was left out -- the md layer does not tell the block layer\nthat it supports flushes or FUA access at all, which results in md\nsilently dropping flush requests.\n\nSince the support already seems there, just add this one piece of\nbookkeeping.\n\nSigned-off-by: Darrick J. Wong \u003cdjwong@us.ibm.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "c26a44ed1e552aaa1d4ceb71842002d235fe98d7", "tree": "47e0d62c2693ae60ae7a5bc44c2dfcd6a2f7e47e", "parents": [ "3561d43fd289f590fdae672e5eb831b8d5cf0bf6" ], "author": { "name": "Justin Maggard", "email": "jmaggard10@gmail.com", "time": "Wed Nov 24 16:36:17 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Nov 24 16:36:17 2010 +1100" }, "message": "md: fix return value of rdev_size_change()\n\nWhen trying to grow an array by enlarging component devices,\nrdev_size_store() expects the return value of rdev_size_change() to be\nin sectors, but the actual value is returned in KBs.\n\nThis functionality was broken by commit\n dd8ac336c13fd8afdb082ebacb1cddd5cf727889\nso this patch is suitable for any kernel since 2.6.30.\n\nCc: stable@kernel.org\nSigned-off-by: Justin Maggard \u003cjmaggard10@gmail.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "77304d2abac6101f7249754ffdd4421258877ab0", "tree": "8ee5914529d70120528a630a8e904c22f8c4f98c", "parents": [ "90fdb0b98a62d78a0650b9fd3ddc58a48f71d740" ], "author": { "name": "Mike Snitzer", "email": "snitzer@redhat.com", "time": "Mon Nov 08 14:39:12 2010 +0100" }, "committer": { "name": "Jens Axboe", "email": "jaxboe@fusionio.com", "time": "Wed Nov 10 14:40:53 2010 +0100" }, "message": "block: read i_size with i_size_read()\n\nConvert direct reads of an inode\u0027s i_size to using i_size_read().\n\ni_size_{read,write} use a seqcount to protect reads from accessing\nincomple writes. Concurrent i_size_write()s require mutual exclussion\nto protect the seqcount that is used by i_size_{read,write}. But\ni_size_read() callers do not need to use additional locking.\n\nSigned-off-by: Mike Snitzer \u003csnitzer@redhat.com\u003e\nAcked-by: NeilBrown \u003cneilb@suse.de\u003e\nAcked-by: Lars Ellenberg \u003clars.ellenberg@linbit.com\u003e\nSigned-off-by: Jens Axboe \u003cjaxboe@fusionio.com\u003e\n" }, { "commit": "a167f663243662aa9153c01086580a11cde9ffdc", "tree": "886e64787421bbf17a1eab7853d67258b598f050", "parents": [ "2b193363ef68667ad717a6723165e0dccf99470f" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Oct 26 18:31:13 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Oct 28 17:36:15 2010 +1100" }, "message": "md: use separate bio pool for each md device.\n\nbio_clone and bio_alloc allocate from a common bio pool.\nIf an md device is stacked with other devices that use this pool, or under\nsomething like swap which uses the pool, then the multiple calls on\nthe pool can cause deadlocks.\n\nSo allocate a local bio pool for each md array and use that rather\nthan the common pool.\n\nThis pool is used both for regular IO and metadata updates.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "2b193363ef68667ad717a6723165e0dccf99470f", "tree": "bd45d5186f0edf2b546c4503d794b479d126ad1f", "parents": [ "1c4588e9c19cae6209a28c9da2f16a18a610b935" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Oct 27 15:16:40 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Oct 28 17:36:11 2010 +1100" }, "message": "md: change type of first arg to sync_page_io.\n\nCurrently sync_page_io takes a \u0027bdev\u0027.\nEvery caller passes \u0027rdev-\u003ebdev\u0027.\nWe will soon want another field out of the rdev in sync_page_io,\nSo just pass the rdev instead of the bdev out of it.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "e804ac780e2f01cb3b914daca2fd4780d1743db1", "tree": "60447c76ea9dbaa526c8cabc14898e4df4498bf6", "parents": [ "57dab0bdf689d42972975ec646d862b0900a4bf3" ], "author": { "name": "Tejun Heo", "email": "tj@kernel.org", "time": "Fri Oct 15 15:36:08 2010 +0200" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Oct 28 17:32:29 2010 +1100" }, "message": "md: fix and update workqueue usage\n\nWorkqueue usage in md has two problems.\n\n* Flush can be used during or depended upon by memory reclaim, but md\n uses the system workqueue for flush_work which may lead to deadlock.\n\n* md depends on flush_scheduled_work() to achieve exclusion against\n completion of removal of previous instances. flush_scheduled_work()\n may incur unexpected amount of delay and is scheduled to be removed.\n\nThis patch adds two workqueues to md - md_wq and md_misc_wq. The\nformer is guaranteed to make forward progress under memory pressure\nand serves flush_work. The latter serves as the flush domain for\nother works.\n\nSigned-off-by: Tejun Heo \u003ctj@kernel.org\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "4b532c9b8c87eb8e51605c4d08dfb5139c758dc5", "tree": "14d4813285bb4aff8e1d7a58a2fdfadd14803a9f", "parents": [ "d97a41dc9c44f5829b7af7aa69fda10fd82b6b4e" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Oct 28 17:30:21 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Oct 28 17:30:21 2010 +1100" }, "message": "md: remove md_mutex locking.\n\nlock_kernel calls were recently pushed down into open/release\nfunctions.\nmd doesn\u0027t need that protection.\nThen the BKL calls were change to md_mutex. We don\u0027t need those\neither.\nSo remove it all.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "d97a41dc9c44f5829b7af7aa69fda10fd82b6b4e", "tree": "4a834cce291edf6798f57d925a6134c287de974d", "parents": [ "12ba8d1e9262ce81a695795410bd9ee5c9407ba1" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Oct 28 17:30:20 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Oct 28 17:30:20 2010 +1100" }, "message": "md: Fix regression with raid1 arrays without persistent metadata.\n\nA RAID1 which has no persistent metadata, whether internal or\nexternal, will hang on the first write.\nThis is caused by commit 070dc6dd7103b6b3f7e4d46e754354a5c15f366e\nIn that case, MD_CHANGE_PENDING never gets cleared.\n\nSo during md_update_sb, is neither persistent or external,\nclear MD_CHANGE_PENDING.\n\nThis is suitable for 2.6.36-stable.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nCc: stable@kernel.org\n" }, { "commit": "a2887097f25cd38cadfc11d10769e2b349fb5eca", "tree": "cd4adcb305365d6ba9acd2c02d4eb9d0125c6f8d", "parents": [ "8abfc6e7a45eb74e51904bbae676fae008b11366", "005a1d15f5a6b2bb4ada80349513effbf22b4588" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Oct 22 17:07:18 2010 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Oct 22 17:07:18 2010 -0700" }, "message": "Merge branch \u0027for-2.6.37/barrier\u0027 of git://git.kernel.dk/linux-2.6-block\n\n* \u0027for-2.6.37/barrier\u0027 of git://git.kernel.dk/linux-2.6-block: (46 commits)\n xen-blkfront: disable barrier/flush write support\n Added blk-lib.c and blk-barrier.c was renamed to blk-flush.c\n block: remove BLKDEV_IFL_WAIT\n aic7xxx_old: removed unused \u0027req\u0027 variable\n block: remove the BH_Eopnotsupp flag\n block: remove the BLKDEV_IFL_BARRIER flag\n block: remove the WRITE_BARRIER flag\n swap: do not send discards as barriers\n fat: do not send discards as barriers\n ext4: do not send discards as barriers\n jbd2: replace barriers with explicit flush / FUA usage\n jbd2: Modify ASYNC_COMMIT code to not rely on queue draining on barrier\n jbd: replace barriers with explicit flush / FUA usage\n nilfs2: replace barriers with explicit flush / FUA usage\n reiserfs: replace barriers with explicit flush / FUA usage\n gfs2: replace barriers with explicit flush / FUA usage\n btrfs: replace barriers with explicit flush / FUA usage\n xfs: replace barriers with explicit flush / FUA usage\n block: pass gfp_mask and flags to sb_issue_discard\n dm: convey that all flushes are processed as empty\n ...\n" }, { "commit": "c37927d4359e81b85de644f8fb08878717cf5f3f", "tree": "25dabf2d905e1410819d1bdaba0bf5f779100d3c", "parents": [ "5704e44d283e907623e3775c1262f206a2c48cf3", "2a48fc0ab24241755dc93bfd4f01d68efab47f5a" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Oct 22 10:49:54 2010 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Fri Oct 22 10:49:54 2010 -0700" }, "message": "Merge branch \u0027trivial\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/arnd/bkl\n\n* \u0027trivial\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/arnd/bkl:\n block: autoconvert trivial BKL users to private mutex\n drivers: autoconvert trivial BKL users to private mutex\n ipmi: autoconvert trivial BKL users to private mutex\n mac: autoconvert trivial BKL users to private mutex\n mtd: autoconvert trivial BKL users to private mutex\n scsi: autoconvert trivial BKL users to private mutex\n\nFix up trivial conflicts (due to addition of private mutex right next to\ndeletion of a version string) in drivers/char/pcmcia/cm40[04]0_cs.c\n" }, { "commit": "fa251f89903d73989e2f63e13d0eaed1e07ce0da", "tree": "3f7fe779941e3b6d67754dd7c44a32f48ea47c74", "parents": [ "dd3932eddf428571762596e17b65f5dc92ca361b", "cd07202cc8262e1669edff0d97715f3dd9260917" ], "author": { "name": "Jens Axboe", "email": "jaxboe@fusionio.com", "time": "Tue Oct 19 09:13:04 2010 +0200" }, "committer": { "name": "Jens Axboe", "email": "jaxboe@fusionio.com", "time": "Tue Oct 19 09:13:04 2010 +0200" }, "message": "Merge branch \u0027v2.6.36-rc8\u0027 into for-2.6.37/barrier\n\nConflicts:\n\tblock/blk-core.c\n\tdrivers/block/loop.c\n\tmm/swapfile.c\n\nSigned-off-by: Jens Axboe \u003cjaxboe@fusionio.com\u003e\n" }, { "commit": "2a48fc0ab24241755dc93bfd4f01d68efab47f5a", "tree": "fa9ae10ce89b26b7d8ae9ce24bdfda5e3007b763", "parents": [ "613655fa39ff6957754fa8ceb8559980920eb8ee" ], "author": { "name": "Arnd Bergmann", "email": "arnd@arndb.de", "time": "Wed Jun 02 14:28:52 2010 +0200" }, "committer": { "name": "Arnd Bergmann", "email": "arnd@arndb.de", "time": "Tue Oct 05 15:01:10 2010 +0200" }, "message": "block: autoconvert trivial BKL users to private mutex\n\nThe block device drivers have all gained new lock_kernel\ncalls from a recent pushdown, and some of the drivers\nwere already using the BKL before.\n\nThis turns the BKL into a set of per-driver mutexes.\nStill need to check whether this is safe to do.\n\nfile\u003d$1\nname\u003d$2\nif grep -q lock_kernel ${file} ; then\n if grep -q \u0027include.*linux.mutex.h\u0027 ${file} ; then\n sed -i \u0027/include.*\u003clinux\\/smp_lock.h\u003e/d\u0027 ${file}\n else\n sed -i \u0027s/include.*\u003clinux\\/smp_lock.h\u003e.*$/include \u003clinux\\/mutex.h\u003e/g\u0027 ${file}\n fi\n sed -i ${file} \\\n -e \"/^#include.*linux.mutex.h/,$ {\n 1,/^\\(static\\|int\\|long\\)/ {\n /^\\(static\\|int\\|long\\)/istatic DEFINE_MUTEX(${name}_mutex);\n\n} }\" \\\n -e \"s/\\(un\\)*lock_kernel\\\u003e[ ]*()/mutex_\\1lock(\\\u0026${name}_mutex)/g\" \\\n -e \u0027/[ ]*cycle_kernel_lock();/d\u0027\nelse\n sed -i -e \u0027/include.*\\\u003csmp_lock.h\\\u003e/d\u0027 ${file} \\\n -e \u0027/cycle_kernel_lock()/d\u0027\nfi\n\nSigned-off-by: Arnd Bergmann \u003carnd@arndb.de\u003e\n" }, { "commit": "ddcf3522cf03a147c867a2e0155761652dbd156a", "tree": "e5a47b7db19dc147df769b6cd8c82ac56964f6e1", "parents": [ "126925c090155f13e90b9e7e8c4010e96027c00a" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Sep 08 16:48:17 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Sep 17 13:53:28 2010 +1000" }, "message": "md: fix v1.x metadata update when a disk is missing.\n\nIf an array with 1.x metadata is assembled with the last disk missing,\nmd doesn\u0027t properly record the fact that the disk was missing.\n\nThis is unlikely to cause a real problem as the event count will be\ndifferent to the count on the missing disk so it won\u0027t be included in\nthe array. However it could still cause confusion.\n\nSo make sure we clear all the relevant slots, not just the early ones.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "126925c090155f13e90b9e7e8c4010e96027c00a", "tree": "f433e7cbd6aba7096a88cc7286b05e0c467ee43d", "parents": [ "9c03f1622af051004416dd3e24d8a0fa31e34178" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Sep 07 17:02:47 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Sep 17 13:53:13 2010 +1000" }, "message": "md: call md_update_sb even for \u0027external\u0027 metadata arrays.\n\nNow that we depend on md_update_sb to clear variable bits in\nmddev-\u003eflags (rather than trying not to set them) it is important to\nalways call md_update_sb when appropriate.\n\nmd_check_recovery has this job but explicitly avoids it for -\u003eexternal\nmetadata arrays. This is not longer appropraite, or needed.\n\nHowever we do want to avoid taking the mddev lock if only\nMD_CHANGE_PENDING is set as that is not cleared by md_update_sb for\nexternal-metadata arrays.\n\nReported-by: \"Kwolek, Adam\" \u003cadam.kwolek@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "e9c7469bb4f502dafc092166201bea1ad5fc0fbf", "tree": "04202b0bb88623d3005c909eaafcb280778902da", "parents": [ "7bc9fddab074d6bb630344e1969e28d20b140621" ], "author": { "name": "Tejun Heo", "email": "tj@kernel.org", "time": "Fri Sep 03 11:56:18 2010 +0200" }, "committer": { "name": "Jens Axboe", "email": "jaxboe@fusionio.com", "time": "Fri Sep 10 12:35:38 2010 +0200" }, "message": "md: implment REQ_FLUSH/FUA support\n\nThis patch converts md to support REQ_FLUSH/FUA instead of now\ndeprecated REQ_HARDBARRIER. In the core part (md.c), the following\nchanges are notable.\n\n* Unlike REQ_HARDBARRIER, REQ_FLUSH/FUA don\u0027t interfere with\n processing of other requests and thus there is no reason to mark the\n queue congested while FLUSH/FUA is in progress.\n\n* REQ_FLUSH/FUA failures are final and its users don\u0027t need retry\n logic. Retry logic is removed.\n\n* Preflush needs to be issued to all member devices but FUA writes can\n be handled the same way as other writes - their processing can be\n deferred to request_queue of member devices. md_barrier_request()\n is renamed to md_flush_request() and simplified accordingly.\n\nFor linear, raid0 and multipath, the core changes are enough. raid1,\n5 and 10 need the following conversions.\n\n* raid1: Handling of FLUSH/FUA bio\u0027s can simply be deferred to\n request_queues of member devices. Barrier related logic removed.\n\n* raid5: Queue draining logic dropped. FUA bit is propagated through\n biodrain and stripe resconstruction such that all the updated parts\n of the stripe are written out with FUA writes if any of the dirtying\n writes was FUA. preread_active_stripes handling in make_request()\n is updated as suggested by Neil Brown.\n\n* raid10: FUA bit needs to be propagated to write clones.\n\nlinear, raid0, 1, 5 and 10 tested.\n\nSigned-off-by: Tejun Heo \u003ctj@kernel.org\u003e\nReviewed-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Jens Axboe \u003cjaxboe@fusionio.com\u003e\n" }, { "commit": "070dc6dd7103b6b3f7e4d46e754354a5c15f366e", "tree": "173e72d08b2070d496c203a6d5156b9a2ad2808c", "parents": [ "bd52b746262c8d77e73903d6608014fb2fcdcd9d" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Aug 30 17:33:34 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Aug 30 18:06:21 2010 +1000" }, "message": "md: resolve confusion of MD_CHANGE_CLEAN\n\nMD_CHANGE_CLEAN is used for two different purposes and this leads to\nconfusion.\nOne of the purposes is largely mirrored by MD_CHANGE_PENDING which is\nnot used for anything else, so have MD_CHANGE_PENDING take over that\npurpose fully.\n\nThe two purposes are:\n 1/ tell md_update_sb that an update is needed and that it is just a\n clean/dirty transition.\n 2/ tell user-space that an transition from clean to dirty is pending\n (something wants to write), and tell te kernel (by clearin the\n flag) that the transition is OK.\n\nThe first purpose remains wit MD_CHANGE_CLEAN, the second is moved\nfully to MD_CHANGE_PENDING.\n\nThis means that various places which conditionally set or cleared\nMD_CHANGE_CLEAN no longer need to be conditional.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "bd52b746262c8d77e73903d6608014fb2fcdcd9d", "tree": "5ee5789f1aae4b238d42c05672db90886b19280e", "parents": [ "7c44ece988a3419e51c833cf14be186a22224dd1" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Mon Aug 30 17:33:33 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Aug 30 18:06:20 2010 +1000" }, "message": "md: don\u0027t clear MD_CHANGE_CLEAN in md_update_sb() for external arrays\n\nIf this bit is cleared in md_update_sb() the kernel will allow writes to the\narray if userspace triggers md_allow_write(), e.g. through stripe_cache_size,\nwhen mdmon is not active. When mdmon is active the array transitions to\nactive-idle bypassing write-pending, setting up a race for mdmon to set the\narray clean before a write arrives.\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "3a3a5ddb7a0f43c3dd0f98673f3d930a456725f8", "tree": "fa1e33c011c9f6350ce5118b89deafacbb1e0f2b", "parents": [ "da5cabf80e2433131bf0ed8993abc0f7ea618c73" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Aug 16 18:09:31 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Aug 18 11:39:38 2010 +1000" }, "message": "Update recovery_offset even when external metadata is used.\n\nThe update of -\u003erecovery_offset in sync_sbs is appropriate even then external\nmetadata is in use. However sync_sbs is only called when native\nmetadata is used.\n\nSo move that update in to the top of md_update_sb (which is the only\ncaller of sync_sbs) before the test on -\u003eexternal.\n\nThis moves the update out of -\u003ewrite_lock protection, but those fields\nonly need -\u003ereconfig_mutex protection which they still have.\n\nAlso move the test on -\u003epersistent up to where -\u003eexternal is set as\nfor metadata update purposes they are the same.\n\nClear MD_CHANGE_DEVS and MD_CHANGE_CLEAN as they can only be confusing\nif -\u003eexternal is set or -\u003epersistent isn\u0027t.\n\nFinally move the update of -\u003eutime down as it is only relevent (like\nthe -\u003eevents update) for native metadata.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nReported-by: \"Kwolek, Adam\" \u003cadam.kwolek@intel.com\u003e\n" }, { "commit": "3d30701b58970425e1d45994d6cb82f828924fdd", "tree": "8b14cf462628bebf8548c1b8c205a674564052d1", "parents": [ "8cbd84f2dd4e52a8771b191030c374ba3e56d291", "fd8aa2c1811bf60ccb2d5de0579c6f62aec1772d" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Aug 10 15:38:19 2010 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Aug 10 15:38:19 2010 -0700" }, "message": "Merge branch \u0027for-linus\u0027 of git://neil.brown.name/md\n\n* \u0027for-linus\u0027 of git://neil.brown.name/md: (24 commits)\n md: clean up do_md_stop\n md: fix another deadlock with removing sysfs attributes.\n md: move revalidate_disk() back outside open_mutex\n md/raid10: fix deadlock with unaligned read during resync\n md/bitmap: separate out loading a bitmap from initialising the structures.\n md/bitmap: prepare for storing write-intent-bitmap via dm-dirty-log.\n md/bitmap: optimise scanning of empty bitmaps.\n md/bitmap: clean up plugging calls.\n md/bitmap: reduce dependence on sysfs.\n md/bitmap: white space clean up and similar.\n md/raid5: export raid5 unplugging interface.\n md/plug: optionally use plugger to unplug an array during resync/recovery.\n md/raid5: add simple plugging infrastructure.\n md/raid5: export is_congested test\n raid5: Don\u0027t set read-ahead when there is no queue\n md: add support for raising dm events.\n md: export various start/stop interfaces\n md: split out md_rdev_init\n md: be more careful setting MD_CHANGE_CLEAN\n md/raid5: ensure we create a unique name for kmem_cache when mddev has no gendisk\n ...\n" }, { "commit": "6e17b0276452912cb13445e5ea552b599984675f", "tree": "1ccac9c3d01f7ea8c6c0061948b92c901253e676", "parents": [ "bb4f1e9d0e2ef93de8e36ca0f5f26625fcd70b7d" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Sat Aug 07 21:41:19 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Sun Aug 08 21:22:45 2010 +1000" }, "message": "md: clean up do_md_stop\n\nThere is only one error exit from do_md_stop, so make that more\nexplicit and discard the \u0027err\u0027 variable.\nAlso drop the \u0027revalidate\u0027 variable by moving the unlock calls around.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "bb4f1e9d0e2ef93de8e36ca0f5f26625fcd70b7d", "tree": "7c7edc0d5fa2b5702358f11396d52d07183708c0", "parents": [ "147e0b6a639ac581ca3bf627bedc3f4a6d3eca66" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Sun Aug 08 21:18:03 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Sun Aug 08 21:21:27 2010 +1000" }, "message": "md: fix another deadlock with removing sysfs attributes.\n\nMove the deletion of sysfs attributes from reconfig_mutex to\nopen_mutex didn\u0027t really help as a process can try to take\nopen_mutex while holding reconfig_mutex, so the same deadlock can\nhappen, just requiring one more process to be involved in the chain.\n\nI looks like I cannot easily use locking to wait for the sysfs\ndeletion to complete, so don\u0027t.\n\nThe only things that we cannot do while the deletions are still\npending is other things which can change the sysfs namespace: run,\ntakeover, stop. Each of these can fail with -EBUSY.\nSo set a flag while doing a sysfs deletion, and fail run, takeover,\nstop if that flag is set.\n\nThis is suitable for 2.6.35.x\n\nCc: stable@kernel.org\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "147e0b6a639ac581ca3bf627bedc3f4a6d3eca66", "tree": "95ca7cb3b2f06586d678ec33c0e9910d11f3af42", "parents": [ "51e9ac77035a3dfcb6fc0a88a0d80b6f99b5edb1" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Fri Aug 06 18:01:59 2010 -0700" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Sun Aug 08 21:20:17 2010 +1000" }, "message": "md: move revalidate_disk() back outside open_mutex\n\nCommit b821eaa5 \"md: remove -\u003echanged and related code\" moved\nrevalidate_disk() under open_mutex, and lockdep noticed.\n\n[ INFO: possible circular locking dependency detected ]\n2.6.32-mdadm-locking #1\n-------------------------------------------------------\nmdadm/3640 is trying to acquire lock:\n (\u0026bdev-\u003ebd_mutex){+.+.+.}, at: [\u003cffffffff811acecb\u003e] revalidate_disk+0x5b/0x90\n\nbut task is already holding lock:\n (\u0026mddev-\u003eopen_mutex){+.+...}, at: [\u003cffffffffa055e07a\u003e] do_md_stop+0x4a/0x4d0 [md_mod]\n\nwhich lock already depends on the new lock.\n\nIt is suitable for 2.6.35.x\n\nCc: \u003cstable@kernel.org\u003e\nReported-by: Przemyslaw Czarnowski \u003cprzemyslaw.hawrylewicz.czarnowski@intel.com\u003e\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "6e9624b8caec290d28b4c6d9ec75749df6372b87", "tree": "47225b544e1da82742795553dc4e8aa70c17afdc", "parents": [ "8a6cfeb6deca3a8fefd639d898b0d163c0b5d368" ], "author": { "name": "Arnd Bergmann", "email": "arnd@arndb.de", "time": "Sat Aug 07 18:25:34 2010 +0200" }, "committer": { "name": "Jens Axboe", "email": "jaxboe@fusionio.com", "time": "Sat Aug 07 18:25:34 2010 +0200" }, "message": "block: push down BKL into .open and .release\n\nThe open and release block_device_operations are currently\ncalled with the BKL held. In order to change that, we must\nfirst make sure that all drivers that currently rely\non this have no regressions.\n\nThis blindly pushes the BKL into all .open and .release\noperations for all block drivers to prepare for the\nnext step. The drivers can subsequently replace the BKL\nwith their own locks or remove it completely when it can\nbe shown that it is not needed.\n\nThe functions blkdev_get and blkdev_put are the only\nremaining users of the big kernel lock in the block\nlayer, besides a few uses in the ioctl code, none\nof which need to serialize with blkdev_{get,put}.\n\nMost of these two functions is also under the protection\nof bdev-\u003ebd_mutex, including the actual calls to\n-\u003eopen and -\u003erelease, and the common code does not\naccess any global data structures that need the BKL.\n\nSigned-off-by: Arnd Bergmann \u003carnd@arndb.de\u003e\nAcked-by: Christoph Hellwig \u003chch@infradead.org\u003e\nSigned-off-by: Jens Axboe \u003cjaxboe@fusionio.com\u003e\n" }, { "commit": "7b6d91daee5cac6402186ff224c3af39d79f4a0e", "tree": "b1518cf0b6c301178e0a320f80610cd5b3aa7625", "parents": [ "33659ebbae262228eef4e0fe990f393d1f0ed941" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Sat Aug 07 18:20:39 2010 +0200" }, "committer": { "name": "Jens Axboe", "email": "jaxboe@fusionio.com", "time": "Sat Aug 07 18:20:39 2010 +0200" }, "message": "block: unify flags for struct bio and struct request\n\nRemove the current bio flags and reuse the request flags for the bio, too.\nThis allows to more easily trace the type of I/O from the filesystem\ndown to the block driver. There were two flags in the bio that were\nmissing in the requests: BIO_RW_UNPLUG and BIO_RW_AHEAD. Also I\u0027ve\nrenamed two request flags that had a superflous RW in them.\n\nNote that the flags are in bio.h despite having the REQ_ name - as\nblkdev.h includes bio.h that is the only way to go for now.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Jens Axboe \u003cjaxboe@fusionio.com\u003e\n" }, { "commit": "69e51b449d383e97b1b9f890f8378c96e9e17346", "tree": "650123fa4f08e8fa7f348a4ca875c59c129e5d84", "parents": [ "e384e58549a2e9a83071ad80280c1a9053cfd84c" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Jun 01 19:37:35 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jul 26 13:21:34 2010 +1000" }, "message": "md/bitmap: separate out loading a bitmap from initialising the structures.\n\ndm makes this distinction between -\u003ectr and -\u003eresume, so we need to\ntoo.\n\nAlso get the new bitmap_load to clear out the bitmap first, as this is\nmost consistent with the dm suspend/resume approach\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "b63d7c2e29bf9cc94989806f2df0cfca4976b830", "tree": "fdb82527ca458769d3c7381375873931bfb23b19", "parents": [ "5ff5afffe6527543866a47ffab12769427283917" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Jun 01 19:37:33 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jul 26 13:21:32 2010 +1000" }, "message": "md/bitmap: clean up plugging calls.\n\n1/ use md_unplug in bitmap.c as we will soon be using bitmaps under\n arrays with no queue attached.\n\n2/ Don\u0027t bother plugging the queue when we set a bit in the bitmap.\n The reason for this was to encourage as many bits as possible to\n get set before we unplug and write stuff out.\n However every personality already plugs the queue after\n bitmap_startwrite either directly (raid1/raid10) or be setting\n STRIPE_BIT_DELAY which causes the queue to be plugged later\n (raid5).\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "252ac5221a71be72b7e7c7b7482af91e9c962e8c", "tree": "cb9542b1391dabc136ce0052eb28948e77a6e2e5", "parents": [ "2ac8740151b082f045e58010eb92560c3a23a0e9" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Jun 01 19:37:29 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jul 26 12:53:08 2010 +1000" }, "message": "md/plug: optionally use plugger to unplug an array during resync/recovery.\n\nIf an array doesn\u0027t have a \u0027queue\u0027 then md_do_sync cannot\nunplug it.\nIn that case it will have a \u0027plugger\u0027, so make that available\nto the mddev, and use it to unplug the array if needed.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "2ac8740151b082f045e58010eb92560c3a23a0e9", "tree": "39bff686e28f033339c6d1cf47042b6dc1586c2f", "parents": [ "11d8a6e3719519fbc0e2c9d61b6fa931b84bf813" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Jun 01 19:37:29 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jul 26 12:53:08 2010 +1000" }, "message": "md/raid5: add simple plugging infrastructure.\n\nmd/raid5 uses the plugging infrastructure provided by the block layer\nand \u0027struct request_queue\u0027. However when we plug raid5 under dm there\nis no request queue so we cannot use that.\n\nSo create a similar infrastructure that is much lighter weight and use\nit for raid5.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "768a418db102bb6aa6064e6090892b5c21ff1f9e", "tree": "2f33acbf0ca542f43c8014201b539ae8f461ee5c", "parents": [ "390ee602a142a93f2c7eb7bffee8e277058b8e0a" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jul 26 11:49:55 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jul 26 12:52:27 2010 +1000" }, "message": "md: add support for raising dm events.\n\ndm uses scheduled work to raise events to user-space.\nSo allow md device to have work_structs and schedule them on an error.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "390ee602a142a93f2c7eb7bffee8e277058b8e0a", "tree": "33a23748dd5ff4ea76b34ed3e458c6da91185376", "parents": [ "e8bb9a839a26f076379e9cb9f46a879d210156f1" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Jun 01 19:37:27 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jul 26 12:52:27 2010 +1000" }, "message": "md: export various start/stop interfaces\n\nexport entry points for starting and stopping md arrays.\nThis will be used by a module to make md/raid5 work under\ndm.\nAlso stop calling md_stop_writes from md_stop, as that won\u0027t\nwork well with dm - it will want to call the two separately.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "e8bb9a839a26f076379e9cb9f46a879d210156f1", "tree": "4da184e861cc5fea4967089711dfdc4fbb175f43", "parents": [ "676e42d896ab6967859fabbb06f4e11b9615cbcf" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Jun 01 19:37:26 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jul 26 12:52:27 2010 +1000" }, "message": "md: split out md_rdev_init\n\nThis functionality will be needed separately in a subsequent patch, so\nsplit it into it\u0027s own exported function.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "676e42d896ab6967859fabbb06f4e11b9615cbcf", "tree": "efab4dffe8e930ec9ef51a5a4d4fd04ffe3749b1", "parents": [ "f4be6b43f1ac60dff00ef0923ee43b0e08872947" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Jun 01 19:37:26 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jul 26 12:52:27 2010 +1000" }, "message": "md: be more careful setting MD_CHANGE_CLEAN\n\nWhen MD_CHANGE_CLEAN is set we might block in md_write_start.\nSo we should only set it when fairly sure that something will clear\nit.\n\nThere are two places where it is set so as to encourage a metadata\nupdate to record the progress of resync/recovery. This should only\nbe done if the internal metadata update mechanisms are in use, which\ncan be tested by by inspecting \u0027-\u003epersistent\u0027.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "00bcb4ac7ee7e557a491b614219142cea0ef16f4", "tree": "992cfa1d0e653aa3de8f0865c5e1a5a0fee4f935", "parents": [ "d0c6f6258478e1dba532bf7c28e2cd6e1047d3a4" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Jun 01 19:37:23 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Jul 21 13:27:53 2010 +1000" }, "message": "md: reduce dependence on sysfs.\n\nWe will want md devices to live as dm targets where sysfs is not\nvisible. So allow md to not connect to sysfs.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "70fffd0bfab1558a8c64c5e903dea1fb84cd9f6b", "tree": "126f2ae8faa2cff8f9dde91cc7a07569ff9851cb", "parents": [ "e4e11e385d1e5516ac76c956d6c25e6c2fa1b8d0" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Jun 16 17:01:25 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Jun 24 13:35:18 2010 +1000" }, "message": "md: Don\u0027t update -\u003erecovery_offset when reshaping an array to fewer devices.\n\nWhen an array is reshaped to have fewer devices, the reshape proceeds\nfrom the end of the devices to the beginning.\n\nIf a device happens to be non-In_sync (which is possible but rare)\nwe would normally update the -\u003erecovery_offset as the reshape\nprogresses. However that would be wrong as the recover_offset records\nthat the early part of the device is in_sync, while in fact it would\nonly be the later part that is in_sync, and in any case the offset\nnumber would be measured from the wrong end of the device.\n\nRelatedly, if after a reshape a spare is discovered to not be\nrecoverred all the way to the end, not allow spare_active\nto incorporate it in the array.\n\nThis becomes relevant in the following sample scenario:\n\nA 4 drive RAID5 is converted to a 6 drive RAID6 in a combined\noperation.\nThe RAID5-\u003eRAID6 conversion will cause a 5 drive to be included as a\nspare, then the 5drive -\u003e 6drive reshape will effectively rebuild that\nspare as it progresses. The 6th drive is treated as in_sync the whole\ntime as there is never any case that we might consider reading from\nit, but must not because there is no valid data.\n\nIf we interrupt this reshape part-way through and reverse it to return\nto a 5-drive RAID6 (or event a 4-drive RAID5), we don\u0027t want to update\nthe recovery_offset - as that would be wrong - and we don\u0027t want to\ninclude that spare as active in the 5-drive RAID6 when the reversed\nreshape completed and it will be mostly out-of-sync still.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "e93f68a1fc6244c05ad8fae28e75835ec74ab34e", "tree": "d282978aac8f6fcec512be2a6e61287bbb6241b1", "parents": [ "0544a21db02c1d8883158fd6f323364f830a120a" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Jun 15 09:36:03 2010 +0100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Jun 24 13:33:24 2010 +1000" }, "message": "md: fix handling of array level takeover that re-arranges devices.\n\nMost array level changes leave the list of devices largely unchanged,\npossibly causing one at the end to become redundant.\nHowever conversions between RAID0 and RAID10 need to renumber\nall devices (except 0).\n\nThis renumbering is currently being done in the -\u003erun method when the\nnew personality takes over. However this is too late as the common\ncode in md.c might already have invalidated some of the devices if\nthey had a -\u003eraid_disk number that appeared to high.\n\nMoving it into the -\u003etakeover method is too early as the array is\nstill active at that time and wrong -\u003eraid_disk numbers could cause\nconfusion.\n\nSo add a -\u003enew_raid_disk field to mdk_rdev_s and use it to communicate\nthe new raid_disk number.\nNow the common code knows exactly which devices need to be renumbered,\nand which can be invalidated, and can do it all at a convenient time\nwhen the array is suspend.\nIt can also update some symlinks in sysfs which previously were not be\nupdated correctly.\n\nReported-by: Maciej Trela \u003cmaciej.trela@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "f3b99be19ded511a1bf05a148276239d9f13eefa", "tree": "c9e59617e67e7a43e38b5c41f3307d54f4279c13", "parents": [ "7e27d6e778cd87b6f2415515d7127eba53fe5d02" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Jun 24 13:31:03 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Jun 24 13:31:03 2010 +1000" }, "message": "Restore partition detection of newly created md arrays.\n\nCommit b821eaa572fd737faaf6928ba046e571526c36c6 broke partition\ndetection for md arrays.\n\nThe logic was almost right. However if revalidate_disk is called\nwhen the device is not yet open, bdev-\u003ebd_disk won\u0027t be set, so the\nflush_disk() Call will not set bd_invalidated.\n\nSo when md_open is called we still need to ensure that\n-\u003ebd_invalidated gets set. This is easily done with a call to\ncheck_disk_size_change in the place where the offending commit removed\ncheck_disk_change. At the important times, the size will have changed\nfrom 0 to non-zero, so check_disk_size_change will set bd_invalidated.\n\nTested-by: Duncan \u003c1i5t5.duncan@cox.net\u003e\nReported-by: Duncan \u003c1i5t5.duncan@cox.net\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "19fdb9eefb21b72edbc365b838502780c392bad6", "tree": "deae04c48532d6eab64ed4b0396737bb854b5506", "parents": [ "be6800a73aa2f3dc14744c3b80e676d189789f04", "3ff195b011d7decf501a4d55aeed312731094796" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Sat May 22 08:31:36 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Sat May 22 08:31:36 2010 +1000" }, "message": "Merge commit \u00273ff195b011d7decf501a4d55aeed312731094796\u0027 into for-linus\n\nConflicts:\n\tdrivers/md/md.c\n\n- Resolved conflict in md_update_sb\n- Added extra \u0027NULL\u0027 arg to new instance of sysfs_get_dirent.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "3ff195b011d7decf501a4d55aeed312731094796", "tree": "8cfdc330abbf82893955f2d7d6e96efee81bfd7c", "parents": [ "bc451f2058238013e1cdf4acd443c01734d332f0" ], "author": { "name": "Eric W. Biederman", "email": "ebiederm@xmission.com", "time": "Tue Mar 30 11:31:26 2010 -0700" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@suse.de", "time": "Fri May 21 09:37:31 2010 -0700" }, "message": "sysfs: Implement sysfs tagged directory support.\n\nThe problem. When implementing a network namespace I need to be able\nto have multiple network devices with the same name. Currently this\nis a problem for /sys/class/net/*, /sys/devices/virtual/net/*, and\npotentially a few other directories of the form /sys/ ... /net/*.\n\nWhat this patch does is to add an additional tag field to the\nsysfs dirent structure. For directories that should show different\ncontents depending on the context such as /sys/class/net/, and\n/sys/devices/virtual/net/ this tag field is used to specify the\ncontext in which those directories should be visible. Effectively\nthis is the same as creating multiple distinct directories with\nthe same name but internally to sysfs the result is nicer.\n\nI am calling the concept of a single directory that looks like multiple\ndirectories all at the same path in the filesystem tagged directories.\n\nFor the networking namespace the set of directories whose contents I need\nto filter with tags can depend on the presence or absence of hotplug\nhardware or which modules are currently loaded. Which means I need\na simple race free way to setup those directories as tagged.\n\nTo achieve a reace free design all tagged directories are created\nand managed by sysfs itself.\n\nUsers of this interface:\n- define a type in the sysfs_tag_type enumeration.\n- call sysfs_register_ns_types with the type and it\u0027s operations\n- sysfs_exit_ns when an individual tag is no longer valid\n\n- Implement mount_ns() which returns the ns of the calling process\n so we can attach it to a sysfs superblock.\n- Implement ktype.namespace() which returns the ns of a syfs kobject.\n\nEverything else is left up to sysfs and the driver layer.\n\nFor the network namespace mount_ns and namespace() are essentially\none line functions, and look to remain that.\n\nTags are currently represented a const void * pointers as that is\nboth generic, prevides enough information for equality comparisons,\nand is trivial to create for current users, as it is just the\nexisting namespace pointer.\n\nThe work needed in sysfs is more extensive. At each directory\nor symlink creating I need to check if the directory it is being\ncreated in is a tagged directory and if so generate the appropriate\ntag to place on the sysfs_dirent. Likewise at each symlink or\ndirectory removal I need to check if the sysfs directory it is\nbeing removed from is a tagged directory and if so figure out\nwhich tag goes along with the name I am deleting.\n\nCurrently only directories which hold kobjects, and\nsymlinks are supported. There is not enough information\nin the current file attribute interfaces to give us anything\nto discriminate on which makes it useless, and there are\nno potential users which makes it an uninteresting problem\nto solve.\n\nSigned-off-by: Eric W. Biederman \u003cebiederm@xmission.com\u003e\nSigned-off-by: Benjamin Thery \u003cbenjamin.thery@bull.net\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n\n" }, { "commit": "be6800a73aa2f3dc14744c3b80e676d189789f04", "tree": "7db76b4488ad45e923223748c41fa8a61a09aa25", "parents": [ "a8707c08f4f718bb0ed65499d3f43201f6e41455" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 10:17:09 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:28:01 2010 +1000" }, "message": "md: don\u0027t insist on valid event count for spare devices.\n\nDevices which know that they are spares do not really need to have\nan event count that matches the rest of the array, so there are no\ndata-in-sync issues. It is enough that the uuid matches.\nSo remove the requirement that the event count is up-to-date.\n\nWe currently still write out and event count on spares, but this\nallows us in a year or 3 to stop doing that completely.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "a8707c08f4f718bb0ed65499d3f43201f6e41455", "tree": "8fc3ea9ea924ebc4f28012c11f3c1e70ad60bcb2", "parents": [ "7b0bb5368a7195606eca475d9f4e291ab7227052" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 09:28:43 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:28:01 2010 +1000" }, "message": "md: simplify updating of event count to sometimes avoid updating spares.\n\nWhen updating the event count for a simple clean \u003c-\u003e dirty transition,\nwe try to avoid updating the spares so they can safely spin-down.\nAs the event_counts across an array must be +/- 1, this means\ndecrementing the event_count on a dirty-\u003eclean transition.\nThis is not always safe and we have to avoid the unsafe time.\nWe current do this with a misguided idea about it being safe or\nnot depending on whether the event_count is odd or even. This\napproach only works reliably in a few common instances, but easily\nfalls down.\n\nSo instead, simply keep internal state concerning whether it is safe\nor not, and always assume it is not safe when an array is first\nassembled.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "75a73a29e520a6ce982b0da6dd8b7560ae3faa90", "tree": "1bcb14b69e2ae7673bf29be6b3f27aee6e896070", "parents": [ "af3a2cd6b8a479345786e7fe5e199ad2f6240e56" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri May 07 19:44:26 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:28:00 2010 +1000" }, "message": "md: restore ability of spare drives to spin down.\n\nSome time ago we stopped the clean/active metadata updates\nfrom being written to a \u0027spare\u0027 device in most cases so that\nit could spin down and say spun down. Device failure/removal\netc are still recorded on spares.\n\nHowever commit 51d5668cb2e3fd1827a55 broke this 50% of the time,\ndepending on whether the event count is even or odd.\nThe change log entry said:\n\n This means that the alignment between \u0027odd/even\u0027 and\n \u0027clean/dirty\u0027 might take a little longer to attain,\n\nhow ever the code makes no attempt to create that alignment, so it\ncould take arbitrarily long.\n\nSo when we find that clean/dirty is not aligned with odd/even,\nforce a second metadata-update immediately. There are already cases\nwhere a second metadata-update is needed immediately (e.g. when a\ndevice fails during the metadata update). We just piggy-back on that.\n\nReported-by: Joe Bryant \u003ctenminjoe@yahoo.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nCc: stable@kernel.org\n" }, { "commit": "f2859af6716ce99cac7f35c5a0c6b7fed346312f", "tree": "37d1af49ce710098bc35d45c7a9aec6e6f8eb5d9", "parents": [ "bb7f8d2217d8753ab5008c78f16697d9e697d570" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Sun May 02 10:04:16 2010 -0700" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:27:58 2010 +1000" }, "message": "md: allow integers to be passed to md/level\n\ne.g. allow md to interpret \u0027echo 4 \u003e md/level\u0027 as a request for raid4.\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\n" }, { "commit": "bb7f8d2217d8753ab5008c78f16697d9e697d570", "tree": "5717c254192b171215bbb8358f68646c3b2e1326", "parents": [ "f1b29bcae116409db5e543622aadab43041c9ae9" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Sat May 01 18:14:57 2010 -0700" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:27:57 2010 +1000" }, "message": "md: notify mdstat waiters of level change\n\nLevel modifications change the output of mdstat. The mdmon manager\nthread is interested in these events for external metadata management.\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\n" }, { "commit": "9e35b99c7efacfddc748c89a0c53b1122b0ee72c", "tree": "5ef48fad2c5de4269cdacdb83a01e41e64683ae5", "parents": [ "fafd7fb052182e087b5a3c6c408e4ac8c2b5fa14" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Apr 06 14:23:02 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:27:56 2010 +1000" }, "message": "md: don\u0027t unregister the thread in mddev_suspend\n\nThis is\n - unnecessary because mddev_suspend is always followed by a call to\n -\u003estop, and each -\u003estop unregisters the thread, and\n - a problem as it makes it awkwards to suspend and then resume a\n device as we will want later.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "fafd7fb052182e087b5a3c6c408e4ac8c2b5fa14", "tree": "0071eab25a38b69a792fb25c3efffbd98609fc18", "parents": [ "21a52c6d05c15f862797736393915bfa8cd40ee9" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Apr 01 15:55:30 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:27:55 2010 +1000" }, "message": "md: factor out init code for an mddev\n\nThis is a simple factorisation that makes mddev_find easier to read.\n\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "21a52c6d05c15f862797736393915bfa8cd40ee9", "tree": "44ffb633d209457979177a52132761a368fcb976", "parents": [ "cca9cf90c504d98644ace52c474770970729f0eb" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Apr 01 15:02:13 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:27:55 2010 +1000" }, "message": "md: pass mddev to make_request functions rather than request_queue\n\nWe used to pass the personality make_request function direct\nto the block layer so the first argument had to be a queue.\nBut now we have the intermediary md_make_request so it makes\nat lot more sense to pass a struct mddev_s.\nIt makes it possible to have an mddev without its own queue too.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "cca9cf90c504d98644ace52c474770970729f0eb", "tree": "d825b55dc2f8742b210479d2af1804b5b31dd791", "parents": [ "a4bd82d0d03b1485975579f131ccfd0aad6b7d6e" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Apr 01 12:08:16 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:27:54 2010 +1000" }, "message": "md: call md_stop_writes from md_stop\n\nThis moves the call to the other side of set_readonly, but that should\nnot be an issue.\nThis encapsulates in \u0027md_stop\u0027 all of the functionality for internally\nstopping the array, leaving all the interactions with externalities\n(sysfs, request_queue, gendisk) in do_md_stop.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "a4bd82d0d03b1485975579f131ccfd0aad6b7d6e", "tree": "7e560963b71f26fc487a1cd932f4b684bd3b3e62", "parents": [ "a047e125403112ceb4d41e68307a2e7498ddba4e" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 29 13:23:10 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:27:54 2010 +1000" }, "message": "md: split md_set_readonly out of do_md_stop\n\nUsing do_md_stop to set an array to read-only is a little confusing.\nNow most of the common code has been factored out, split\nmd_set_readonly off in to a separate function.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "a047e125403112ceb4d41e68307a2e7498ddba4e", "tree": "392928f408e3a6a2d40a7c3b6a178fbb3c411e06", "parents": [ "6177b472ab14e1ac88896960370dd54ba577d926" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 29 12:07:53 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:27:54 2010 +1000" }, "message": "md: factor md_stop_writes out of do_md_stop.\n\nFurther refactoring of do_md_stop.\nThis one requires some explanation as it takes code from different\nplaces in do_md_stop, so some re-ordering happens.\n\nWe only get into this part of do_md_stop if there are no active opens\nof the device, so no writes can be happening and the device must have\nbeen flushed. In md_stop_writes we want to stop any internal sources\nof writes - i.e. resync - and flush out the metadata.\n\nThe only code that was previously before some of this code is\ncode to clean up the queue, the mddev, the gendisk, or sysfs, all\nof which is probably better after code that makes active changes (i.e.\ntriggers writes).\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "6177b472ab14e1ac88896960370dd54ba577d926", "tree": "387eec24b0ac82e028edfdd77d8b425077ca0bfb", "parents": [ "fe60b0142813002be16dfae28780d9779ee22473" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 29 11:37:13 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:27:53 2010 +1000" }, "message": "md: start to refactor do_md_stop\n\ndo_md_stop is large and clunky, so hard to understand.\n\nThis is a first step of refactoring, pulling two simple\nsub-functions out.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "fe60b0142813002be16dfae28780d9779ee22473", "tree": "1b2337036bbb30857531cd2d54729d38fdd75a3a", "parents": [ "b821eaa572fd737faaf6928ba046e571526c36c6" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 29 11:10:42 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:27:53 2010 +1000" }, "message": "md: factor do_md_run to separate accesses to -\u003egendisk\n\nAs part of relaxing the binding between an mddev and gendisk,\nwe separate do_md_run into two functions.\n md_run does all the work internal to md\n do_md_run calls md_run and makes and changes to gendisk\n that are required.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "b821eaa572fd737faaf6928ba046e571526c36c6", "tree": "0db462a3c7da3dbf42d28e2483a27d78839b4589", "parents": [ "49ce6cea85fb8d25ee59486c919406e9cecf1762" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 29 11:18:15 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:27:53 2010 +1000" }, "message": "md: remove -\u003echanged and related code.\n\nWe set -\u003echanged to 1 and call check_disk_change at the end\nof md_open so that bd_invalidated would be set and thus\npartition rescan would happen appropriately.\n\nNow that we call revalidate_disk directly, which sets bd_invalidates,\nthat indirection is no longer needed and can be removed.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "49ce6cea85fb8d25ee59486c919406e9cecf1762", "tree": "36ff1804090759c0b43593feb8880b15121d13e9", "parents": [ "490773268cf64f68da2470e07b52c7944da6312d" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 29 10:51:42 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:27:52 2010 +1000" }, "message": "md: don\u0027t reference gendisk in getgeo\n\nUsing -\u003earray_sectors rather than get_capacity() is more\ndirect and is a step towards relaxing the tight connection\nbetween mddev and gendisk.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "490773268cf64f68da2470e07b52c7944da6312d", "tree": "d394aafa7203c316db6b63f128b8894e18993fca", "parents": [ "2b7f22284d71975e37a82db154386348eec0e52c" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Mar 25 16:20:56 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:27:52 2010 +1000" }, "message": "md: move io accounting out of personalities into md_make_request\n\nWhile I generally prefer letting personalities do as much as possible,\ngiven that we have a central md_make_request anyway we may as well use\nit to simplify code.\nAlso this centralises knowledge of -\u003egendisk which will help later.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "5cac7861b2de95a1f714ebdc652813abd0afcc73", "tree": "552bc6200817c6872f403ab54a50e8c5f7a594fa", "parents": [ "233fca36bb439eadcad28500b5139fed7c64a0ae" ], "author": { "name": "Maciej Trela", "email": "Maciej.Trela@intel.com", "time": "Wed Apr 14 17:17:39 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:27:49 2010 +1000" }, "message": "md: notify level changes through sysfs.\n\nLevel changes can be very significant, so make sure\nto notify them via sysfs.\n\nSigned-off-by: Maciej Trela \u003cmaciej.trela@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "233fca36bb439eadcad28500b5139fed7c64a0ae", "tree": "dfaec050a24564da4d05ec0e21cd814375eae1e8", "parents": [ "b71031076e1169e89bdac1b245ad1488587e4730" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Apr 14 17:02:09 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:27:49 2010 +1000" }, "message": "md: Relax checks on -\u003emax_disks when external metadata handling is used.\n\nWhen metadata is being managed by user-space, md doesn\u0027t know\nwhat the maximum number of devices allowed in an array is\nso -\u003emax_disks is 0. In this case we should allow any (+ve)\nnumber of disks.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "b71031076e1169e89bdac1b245ad1488587e4730", "tree": "b67a3ffc0263a7e380a9545ca066aea7cc46003b", "parents": [ "dab8b29248b3f14f456651a2a6ee9b8fd16d1b3c" ], "author": { "name": "Maciej Trela", "email": "Maciej.Trela@intel.com", "time": "Wed Apr 14 16:58:16 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:27:48 2010 +1000" }, "message": "md: Correctly handle device removal via sysfs\n\nWriting \"none\" to \"../md/dev-xx/slot\" removes that device\nfrom being an active part of the array, but it didn\u0027t\nset -\u003eraid_disk to -1 to record this fact.\n\n\nSigned-off-by: Maciej Trela \u003cMaciej.Trela@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "9af204cf720cedf369cf823bbd806c350201f7ea", "tree": "6aa684772cc1ba978e9dd0f67c3e0d5592588ca3", "parents": [ "54071b3808ee3dc8624d9d6f1b06c4fd5308fa3b" ], "author": { "name": "Trela, Maciej", "email": "Maciej.Trela@intel.com", "time": "Mon Mar 08 16:02:44 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:27:48 2010 +1000" }, "message": "md: Add support for Raid5-\u003eRaid0 and Raid10-\u003eRaid0 takeover\n\n\nSigned-off-by: Maciej Trela \u003cmaciej.trela@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "54071b3808ee3dc8624d9d6f1b06c4fd5308fa3b", "tree": "b254ce6625ce3dd472faac0d59edeb9589b30f2b", "parents": [ "84707f38e767ac470fd82af6c45a8cafe2bd1b9a" ], "author": { "name": "Trela Maciej", "email": "Maciej.Trela@intel.com", "time": "Mon Mar 08 16:02:42 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:27:47 2010 +1000" }, "message": "md:Add support for Raid0-\u003eRaid5 takeover\n\nSigned-off-by: Maciej Trela \u003cmaciej.trela@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "c0cc75f84e0e413bce2dcabea74ef418da45c7c1", "tree": "f5723fbd0f5828cadaeec650abb8066ad52fad71", "parents": [ "7b92813c3c0b6990f14838e3985fb385d2655d0c" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Mar 22 10:28:51 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue May 18 15:27:47 2010 +1000" }, "message": "md: discard StateChanged device flag.\n\nThis was needed when sysfs files could only be \u0027notified\u0027\nfrom process context. Now that we have sys_notify_direct,\nwe can call it directly from an interrupt.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "a64c876fd357906a1f7193723866562ad290654c", "tree": "077fcdab730d40227585025bf15bf8e027949a29", "parents": [ "b6eb127d274385d81ce8dd45c98190f097bce1b4" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Apr 14 17:15:37 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon May 17 14:45:40 2010 +1000" }, "message": "md: manage redundancy group in sysfs when changing level.\n\nSome levels expect the \u0027redundancy group\u0027 to be present,\nothers don\u0027t.\nSo when we change level of an array we might need to\nadd or remove this group.\n\nThis requires fixing up the current practice of overloading -\u003eprivate\nto indicate (when -\u003epers \u003d\u003d NULL) that something needs to be removed.\nSo create a new -\u003eto_remove to fill that role.\n\nWhen changing levels, we may need to add or remove attributes. When\nchanging RAID5 -\u003e RAID6, we both add and remove the same thing. It is\nimportant to catch this and optimise it out as the removal is delayed\nuntil a lock is released, so trying to add immediately would cause\nproblems.\n\n\nCc: stable@kernel.org\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "b6eb127d274385d81ce8dd45c98190f097bce1b4", "tree": "a78eb14056ade77c0026b1106e9a2cd486a762e6", "parents": [ "ef2f80ff7325b2c1888ff02ead28957b5840bf51" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Apr 15 10:13:47 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon May 17 14:40:07 2010 +1000" }, "message": "md: remove unneeded sysfs files more promptly\n\nWhen an array is stopped we need to remove some\nsysfs files which are dependent on the type of array.\n\nWe need to delay that deletion as deleting them while holding\nreconfig_mutex can lead to deadlocks.\n\nWe currently delay them until the array is completely destroyed.\nHowever it is possible to deactivate and then reactivate the array.\nIt is also possible to need to remove sysfs files when changing level,\nwhich can potentially happen several times before an array is\ndestroyed.\n\nSo we need to delete these files more promptly: as soon as\nreconfig_mutex is dropped.\n\nWe need to ensure this happens before do_md_run can restart the array,\nso we use open_mutex for some extra locking. This is not deadlock\nprone.\n\nCc: stable@kernel.org\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "e2218350465e7e0931676b4849b594c978437bce", "tree": "395398081c277c533d28edd70d08a9394e7d8597", "parents": [ "627a2d3c29427637f4c5d31ccc7fcbd8d312cd71" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Wed May 12 08:25:37 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed May 12 08:25:37 2010 +1000" }, "message": "md: set mddev readonly flag on blkdev BLKROSET ioctl\n\nWhen the user sets the block device to readwrite then the mddev should\nfollow suit. Otherwise, the BUG_ON in md_write_start() will be set to\ntrigger.\n\nThe reverse direction, setting mddev-\u003ero to match a set readonly\nrequest, can be ignored because the blkdev level readonly flag precludes\nthe need to have mddev-\u003ero set correctly. Nevermind the fact that\nsetting mddev-\u003ero to 1 may fail if the array is in use.\n\nCc: \u003cstable@kernel.org\u003e\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "1176568de7e066c0be9e46c37503b9fd4730edcf", "tree": "8af6ab7cd59ef6a615048ef31d922aee76cadd57", "parents": [ "87aa63000c484bfb9909989316f615240dfee018" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri May 07 19:44:26 2010 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri May 07 21:10:57 2010 +1000" }, "message": "md: restore ability of spare drives to spin down.\n\nSome time ago we stopped the clean/active metadata updates\nfrom being written to a \u0027spare\u0027 device in most cases so that\nit could spin down and say spun down. Device failure/removal\netc are still recorded on spares.\n\nHowever commit 51d5668cb2e3fd1827a55 broke this 50% of the time,\ndepending on whether the event count is even or odd.\nThe change log entry said:\n\n This means that the alignment between \u0027odd/even\u0027 and\n \u0027clean/dirty\u0027 might take a little longer to attain,\n\nhow ever the code makes no attempt to create that alignment, so it\ncould take arbitrarily long.\n\nSo when we find that clean/dirty is not aligned with odd/even,\nforce a second metadata-update immediately. There are already cases\nwhere a second metadata-update is needed immediately (e.g. when a\ndevice fails during the metadata update). We just piggy-back on that.\n\nReported-by: Joe Bryant \u003ctenminjoe@yahoo.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nCc: stable@kernel.org\n" }, { "commit": "5a0e3ad6af8660be21ca98a971cd00f331318c05", "tree": "5bfb7be11a03176a87296a43ac6647975c00a1d1", "parents": [ "ed391f4ebf8f701d3566423ce8f17e614cde9806" ], "author": { "name": "Tejun Heo", "email": "tj@kernel.org", "time": "Wed Mar 24 17:04:11 2010 +0900" }, "committer": { "name": "Tejun Heo", "email": "tj@kernel.org", "time": "Tue Mar 30 22:02:32 2010 +0900" }, "message": "include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h\n\npercpu.h is included by sched.h and module.h and thus ends up being\nincluded when building most .c files. percpu.h includes slab.h which\nin turn includes gfp.h making everything defined by the two files\nuniversally available and complicating inclusion dependencies.\n\npercpu.h -\u003e slab.h dependency is about to be removed. Prepare for\nthis change by updating users of gfp and slab facilities include those\nheaders directly instead of assuming availability. As this conversion\nneeds to touch large number of source files, the following script is\nused as the basis of conversion.\n\n http://userweb.kernel.org/~tj/misc/slabh-sweep.py\n\nThe script does the followings.\n\n* Scan files for gfp and slab usages and update includes such that\n only the necessary includes are there. ie. if only gfp is used,\n gfp.h, if slab is used, slab.h.\n\n* When the script inserts a new include, it looks at the include\n blocks and try to put the new include such that its order conforms\n to its surrounding. It\u0027s put in the include block which contains\n core kernel includes, in the same order that the rest are ordered -\n alphabetical, Christmas tree, rev-Xmas-tree or at the end if there\n doesn\u0027t seem to be any matching order.\n\n* If the script can\u0027t find a place to put a new include (mostly\n because the file doesn\u0027t have fitting include block), it prints out\n an error message indicating which .h file needs to be added to the\n file.\n\nThe conversion was done in the following steps.\n\n1. The initial automatic conversion of all .c files updated slightly\n over 4000 files, deleting around 700 includes and adding ~480 gfp.h\n and ~3000 slab.h inclusions. The script emitted errors for ~400\n files.\n\n2. Each error was manually checked. Some didn\u0027t need the inclusion,\n some needed manual addition while adding it to implementation .h or\n embedding .c file was more appropriate for others. This step added\n inclusions to around 150 files.\n\n3. The script was run again and the output was compared to the edits\n from #2 to make sure no file was left behind.\n\n4. Several build tests were done and a couple of problems were fixed.\n e.g. lib/decompress_*.c used malloc/free() wrappers around slab\n APIs requiring slab.h to be added manually.\n\n5. The script was run on all .h files but without automatically\n editing them as sprinkling gfp.h and slab.h inclusions around .h\n files could easily lead to inclusion dependency hell. Most gfp.h\n inclusion directives were ignored as stuff from gfp.h was usually\n wildly available and often used in preprocessor macros. Each\n slab.h inclusion directive was examined and added manually as\n necessary.\n\n6. percpu.h was updated not to include slab.h.\n\n7. Build test were done on the following configurations and failures\n were fixed. CONFIG_GCOV_KERNEL was turned off for all tests (as my\n distributed build env didn\u0027t work with gcov compiles) and a few\n more options had to be turned off depending on archs to make things\n build (like ipr on powerpc/64 which failed due to missing writeq).\n\n * x86 and x86_64 UP and SMP allmodconfig and a custom test config.\n * powerpc and powerpc64 SMP allmodconfig\n * sparc and sparc64 SMP allmodconfig\n * ia64 SMP allmodconfig\n * s390 SMP allmodconfig\n * alpha SMP allmodconfig\n * um on x86_64 SMP allmodconfig\n\n8. percpu.h modifications were reverted so that it could be applied as\n a separate patch and serve as bisection point.\n\nGiven the fact that I had only a couple of failures from tests on step\n6, I\u0027m fairly confident about the coverage of this conversion patch.\nIf there is a breakage, it\u0027s likely to be something in one of the arch\nheaders which should be easily discoverable easily on most builds of\nthe specific arch.\n\nSigned-off-by: Tejun Heo \u003ctj@kernel.org\u003e\nGuess-its-ok-by: Christoph Lameter \u003ccl@linux-foundation.org\u003e\nCc: Ingo Molnar \u003cmingo@redhat.com\u003e\nCc: Lee Schermerhorn \u003cLee.Schermerhorn@hp.com\u003e\n" }, { "commit": "52cf25d0ab7f78eeecc59ac652ed5090f69b619e", "tree": "031d1ffb3890bd69c0260c864c512e0be62ac05c", "parents": [ "6c1733aca0b48db4d0e660d54976a1cca25b5eaf" ], "author": { "name": "Emese Revfy", "email": "re.emese@gmail.com", "time": "Tue Jan 19 02:58:23 2010 +0100" }, "committer": { "name": "Greg Kroah-Hartman", "email": "gregkh@suse.de", "time": "Sun Mar 07 17:04:49 2010 -0800" }, "message": "Driver core: Constify struct sysfs_ops in struct kobj_type\n\nConstify struct sysfs_ops.\n\nThis is part of the ops structure constification\neffort started by Arjan van de Ven et al.\n\nBenefits of this constification:\n\n * prevents modification of data that is shared\n (referenced) by many other structure instances\n at runtime\n\n * detects/prevents accidental (but not intentional)\n modification attempts on archs that enforce\n read-only kernel data at runtime\n\n * potentially better optimized code as the compiler\n can assume that the const data cannot be changed\n\n * the compiler/linker move const data into .rodata\n and therefore exclude them from false sharing\n\nSigned-off-by: Emese Revfy \u003cre.emese@gmail.com\u003e\nAcked-by: David Teigland \u003cteigland@redhat.com\u003e\nAcked-by: Matt Domsch \u003cMatt_Domsch@dell.com\u003e\nAcked-by: Maciej Sosnowski \u003cmaciej.sosnowski@intel.com\u003e\nAcked-by: Hans J. Koch \u003chjk@linutronix.de\u003e\nAcked-by: Pekka Enberg \u003cpenberg@cs.helsinki.fi\u003e\nAcked-by: Jens Axboe \u003cjens.axboe@oracle.com\u003e\nAcked-by: Stephen Hemminger \u003cshemminger@vyatta.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n\n" }, { "commit": "ef286f6fa673cd7fb367e1b145069d8dbfcc6081", "tree": "957760503c1b1a417850db3204d6c010d1ce1a67", "parents": [ "9eb07c259207d048e3ee8be2a77b2a4680b1edd4" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Feb 09 16:34:14 2010 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Feb 10 11:26:09 2010 +1100" }, "message": "md: fix some lockdep issues between md and sysfs.\n\n\u003d\u003d\u003d\u003d\u003d\u003d\nThis fix is related to\n http://bugzilla.kernel.org/show_bug.cgi?id\u003d15142\nbut does not address that exact issue.\n\u003d\u003d\u003d\u003d\u003d\u003d\n\nsysfs does like attributes being removed while they are being accessed\n(i.e. read or written) and waits for the access to complete.\n\nAs accessing some md attributes takes the same lock that is held while\nremoving those attributes a deadlock can occur.\n\nThis patch addresses 3 issues in md that could lead to this deadlock.\n\nTwo relate to calling flush_scheduled_work while the lock is held.\nThis is probably a bad idea in general and as we use schedule_work to\ndelete various sysfs objects it is particularly bad.\n\nIn one case flush_scheduled_work is called from md_alloc (called by\nmd_probe) called from do_md_run which holds the lock. This call is\nonly present to ensure that -\u003egendisk is set. However we can be sure\nthat gendisk is always set (though possibly we couldn\u0027t when that code\nwas originally written. This is because do_md_run is called in three\ndifferent contexts:\n 1/ from md_ioctl. This requires that md_open has succeeded, and it\n fails if -\u003egendisk is not set.\n 2/ from writing a sysfs attribute. This can only happen if the\n mddev has been registered in sysfs which happens in md_alloc\n after -\u003egendisk has been set.\n 3/ from autorun_array which is only called by autorun_devices, which\n checks for -\u003egendisk to be set before calling autorun_array.\nSo the call to md_probe in do_md_run can be removed, and the check on\n-\u003egendisk can also go.\n\n\nIn the other case flush_scheduled_work is being called in do_md_stop,\npurportedly to wait for all md_delayed_delete calls (which delete the\ncomponent rdevs) to complete. However there really isn\u0027t any need to\nwait for them - they have already been disconnected in all important\nways.\n\nThe third issue is that raid5-\u003estop() removes some attribute names\nwhile the lock is held. There is already some infrastructure in place\nto delay attribute removal until after the lock is released (using\nschedule_work). So extend that infrastructure to remove the\nraid5_attrs_group.\n\nThis does not address all lockdep issues related to the sysfs\n\"s_active\" lock. The rest can be address by splitting that lockdep\ncontext between symlinks and non-symlinks which hopefully will happen.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "404e4b43fdd6daa7b4a9f81bc7e4358281d763fa", "tree": "7a013e233db56b7c90cf0857d6c3bc74c19cf07f", "parents": [ "7fb9dadc91948ddd16d1d32e414b5e71ec63b97b" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Dec 30 15:25:23 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Dec 30 15:25:23 2009 +1100" }, "message": "md: allow a resync that is waiting for other resync to complete, to be aborted.\n\nIf two arrays share a device, then they will not both resync at the\nsame time. One will wait for the other to complete.\nWhile waiting, the MD_RECOVERY_INTR flag is not checked so a device\nfailure, which would make the resync pointless, does not cause the\nresync to abort, so the failed device cannot be removed (as it cannot\nbe remove while a resync is happening).\n\nSo add a test for MD_RECOVERY_INTR.\n\nReported-by: Brett Russ \u003cbruss@netezza.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "7fb9dadc91948ddd16d1d32e414b5e71ec63b97b", "tree": "d64379c9b336a2792f1877383bdcdd92e837070b", "parents": [ "a2d79c324ac0c26ae9995a312a7731067a7f01fc" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Dec 30 15:19:08 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Dec 30 15:20:43 2009 +1100" }, "message": "md: remove unnecessary code from do_md_run\n\nSince commit dfc7064500061677720fa26352963c772d3ebe6b,\n-\u003ehot_remove_disks has not removed non-failed devices from\nan array until recovery is no longer possible.\nSo the code in do_md_run to get around the fact that\nmd_check_recovery (which calls -\u003ehot_remove_disks) would\nremove partially-in-sync devices is no longer needed.\n\nSo remove it.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "a2d79c324ac0c26ae9995a312a7731067a7f01fc", "tree": "bf9418f4fe8ab86eaf5519be6f1beb363dc64bda", "parents": [ "0f9552b5dc4fe10da37fa3f4a4ca185d90fa41c9" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Mon Dec 21 18:18:36 2009 -0700" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Dec 30 15:20:31 2009 +1100" }, "message": "md: make recovery started by do_md_run() visible via sync_action\n\nBy default md_do_sync() will perform recovery if no other actions are\nspecified. However, action_show() relies on MD_RECOVERY_RECOVER to be\nset otherwise it returns \u0027idle\u0027. So, add a missing set\nMD_RECOVERY_RECOVER when starting recovery.\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "0f9552b5dc4fe10da37fa3f4a4ca185d90fa41c9", "tree": "14f29af551fc226dc4451f1089d4f08dc2611c0d", "parents": [ "cbd1998377504df005302ac90d49db72a48552a6" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Dec 30 12:08:50 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Dec 30 15:20:12 2009 +1100" }, "message": "md: fix small irregularity with start_ro module parameter\n\nThe start_ro modules parameter can be used to force arrays to be\nstarted in \u0027auto-readonly\u0027 in which they are read-only until the first\nwrite. This ensures that no resync/recovery happens until something\nelse writes to the device. This is important for resume-from-disk\noff an md array.\n\nHowever if an array is started \u0027readonly\u0027 (by writing \u0027readonly\u0027 to\nthe \u0027array_state\u0027 sysfs attribute) we want it to be really \u0027readonly\u0027,\nnot \u0027auto-readonly\u0027.\n\nSo strengthen the condition to only set auto-readonly if the\narray is not already read-only.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "cbd1998377504df005302ac90d49db72a48552a6", "tree": "f5c0d83ebe8534477bd252204da804640fd5413b", "parents": [ "6b7b284958d47b77d06745b36bc7f36dab769d9b" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Dec 30 12:08:49 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Dec 30 12:08:49 2009 +1100" }, "message": "md: Fix unfortunate interaction with evms\n\nevms configures md arrays by:\n open device\n send ioctl\n close device\n\nfor each different ioctl needed.\nSince 2.6.29, the device can disappear after the \u0027close\u0027\nunless a significant configuration has happened to the device.\nThe change made by \"SET_ARRAY_INFO\" can too minor to stop the device\nfrom disappearing, but important enough that losing the change is bad.\n\nSo: make sure SET_ARRAY_INFO sets mddev-\u003ectime, and keep the device\nactive as long as ctime is non-zero (it gets zeroed with lots of other\nthings when the array is stopped).\n\nThis is suitable for -stable kernels since 2.6.29.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nCc: stable@kernel.org" }, { "commit": "7b75c2f8cf6d938b571d3bc3f566f883ab7472c4", "tree": "480a924c730a56dfb06a0bec92b63e9086aa8287", "parents": [ "bc058f65e8c7d83c139692e1c26513d3187dd744" ], "author": { "name": "Joe Perches", "email": "joe@perches.com", "time": "Mon Dec 14 18:01:12 2009 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Dec 15 08:53:33 2009 -0800" }, "message": "drivers/md/md.c: use %pU to print UUIDs\n\nSigned-off-by: Joe Perches \u003cjoe@perches.com\u003e\nCc: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "e7d2860b690d4f3bed6824757c540579638e3d1e", "tree": "84268ee28893256fd6a6a7e1d4474f61dbee74e7", "parents": [ "84c95c9acf088c99d8793d78036b67faa5d0b851" ], "author": { "name": "André Goddard Rosa", "email": "andre.goddard@gmail.com", "time": "Mon Dec 14 18:01:06 2009 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Dec 15 08:53:32 2009 -0800" }, "message": "tree-wide: convert open calls to remove spaces to skip_spaces() lib function\n\nMakes use of skip_spaces() defined in lib/string.c for removing leading\nspaces from strings all over the tree.\n\nIt decreases lib.a code size by 47 bytes and reuses the function tree-wide:\n text data bss dec hex filename\n 64688 584 592 65864 10148 (TOTALS-BEFORE)\n 64641 584 592 65817 10119 (TOTALS-AFTER)\n\nAlso, while at it, if we see (*str \u0026\u0026 isspace(*str)), we can be sure to\nremove the first condition (*str) as the second one (isspace(*str)) also\nevaluates to 0 whenever *str \u003d\u003d 0, making it redundant. In other words,\n\"a char equals zero is never a space\".\n\nJulia Lawall tried the semantic patch (http://coccinelle.lip6.fr) below,\nand found occurrences of this pattern on 3 more files:\n drivers/leds/led-class.c\n drivers/leds/ledtrig-timer.c\n drivers/video/output.c\n\n@@\nexpression str;\n@@\n\n( // ignore skip_spaces cases\nwhile (*str \u0026\u0026 isspace(*str)) { \\(str++;\\|++str;\\) }\n|\n- *str \u0026\u0026\nisspace(*str)\n)\n\nSigned-off-by: André Goddard Rosa \u003candre.goddard@gmail.com\u003e\nCc: Julia Lawall \u003cjulia@diku.dk\u003e\nCc: Martin Schwidefsky \u003cschwidefsky@de.ibm.com\u003e\nCc: Jeff Dike \u003cjdike@addtoit.com\u003e\nCc: Ingo Molnar \u003cmingo@elte.hu\u003e\nCc: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: \"H. Peter Anvin\" \u003chpa@zytor.com\u003e\nCc: Richard Purdie \u003crpurdie@rpsys.net\u003e\nCc: Neil Brown \u003cneilb@suse.de\u003e\nCc: Kyle McMartin \u003ckyle@mcmartin.ca\u003e\nCc: Henrique de Moraes Holschuh \u003chmh@hmh.eng.br\u003e\nCc: David Howells \u003cdhowells@redhat.com\u003e\nCc: \u003clinux-ext4@vger.kernel.org\u003e\nCc: Samuel Ortiz \u003csamuel@sortiz.org\u003e\nCc: Patrick McHardy \u003ckaber@trash.net\u003e\nCc: Takashi Iwai \u003ctiwai@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "06e3c817b750c131a20e82eed57a17841ea88ed2", "tree": "55da529f662c29da5b5fd202b5ece9fb907aa431", "parents": [ "4e59ca7da05f0d5d3ad40365c502c8b0fd24c7e3" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Sat Dec 12 21:17:12 2009 -0700" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:58:57 2009 +1100" }, "message": "md: add \u0027recovery_start\u0027 per-device sysfs attribute\n\nEnable external metadata arrays to manage rebuild checkpointing via a\nmd/dev-XXX/recovery_start attribute which reflects rdev-\u003erecovery_offset\n\nAlso update resync_start_store to allow \u0027none\u0027 to be written, for\nconsistency.\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e" }, { "commit": "4e59ca7da05f0d5d3ad40365c502c8b0fd24c7e3", "tree": "d5ddc749ec13db16c1ed7a054546c2ea482c0e1e", "parents": [ "93be75ffde6dfd1ad17cc3ff1dbd135bd711baf4" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Sat Dec 12 21:17:06 2009 -0700" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:57:43 2009 +1100" }, "message": "md: rcu_read_lock() walk of mddev-\u003edisks in md_do_sync()\n\nOther walks of this list are either under rcu_read_lock() or the list\nmutation lock (mddev_lock()). This protects against the improbable case of a\ndisk being removed from the array at the start of md_do_sync().\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\n" }, { "commit": "93be75ffde6dfd1ad17cc3ff1dbd135bd711baf4", "tree": "56006efccad176da1b806978faf60d77c817e6ac", "parents": [ "aa98aa31987ad9831711ae71ea2270228ab62532" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:50:06 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:51:41 2009 +1100" }, "message": "md: integrate spares into array at earliest opportunity.\n\nAs v1.x metadata can record that a member of the array is\nnot completely recovered, it make sense to record that a\nspare has become a regular member of the array at the earliest\nopportunity.\nSo remove the tests on \"recovery_offset \u003e 0\" in super_1_sync\nas they really aren\u0027t needed, and schedule a metadata update\nimmediately after adding spares to a degraded array.\n\nThis means that if a crash happens immediately after a recovery\nstarts, the new device will be included in the array and recovery will\ncontinue from wherever it was up to. Previously this didn\u0027t happen\nunless recovery was at least 1/16 of the way through.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "aa98aa31987ad9831711ae71ea2270228ab62532", "tree": "736036691f07fe4b7d18064aaa0ace5d76b73cf6", "parents": [ "93bd89a6d5f268acbdb8d775e40d3a280b07b5bd" ], "author": { "name": "Arnd Bergmann", "email": "arnd@arndb.de", "time": "Mon Dec 14 12:50:05 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:51:41 2009 +1100" }, "message": "md: move compat_ioctl handling into md.c\n\nThe RAID ioctls are only implemented in md.c, so the\nhandling for them should also be moved there from\nfs/compat_ioctl.c.\n\nSigned-off-by: Arnd Bergmann \u003carnd@arndb.de\u003e\nCc: Neil Brown \u003cneilb@suse.de\u003e\nCc: Andre Noll \u003cmaan@systemlinux.org\u003e\nCc: linux-raid@vger.kernel.org\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "0efb9e6191e1d3d34c1db90b829b742bc36d532e", "tree": "5960d97df87a7eeea56d7dbe801259fc43398d5e", "parents": [ "1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:58 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:51:41 2009 +1100" }, "message": "md: add MODULE_DESCRIPTION for all md related modules.\n\nSuggested by Oren Held \u003corenhe@il.ibm.com\u003e\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "1e50915fe0bbf7a46db0fa7e1e604d3fc95f057d", "tree": "7a722ad6f56c61a6173493f1cd44d809c8b1bd8d", "parents": [ "67b8dc4b06b0e97df55fd76e209f34f9a52e820e" ], "author": { "name": "Robert Becker", "email": "Rob.Becker@riverbed.com", "time": "Mon Dec 14 12:49:58 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:51:41 2009 +1100" }, "message": "raid: improve MD/raid10 handling of correctable read errors.\n\nWe\u0027ve noticed severe lasting performance degradation of our raid\narrays when we have drives that yield large amounts of media errors.\nThe raid10 module will queue each failed read for retry, and also\nwill attempt call fix_read_error() to perform the read recovery.\nRead recovery is performed while the array is frozen, so repeated\nrecovery attempts can degrade the performance of the array for\nextended periods of time.\n\nWith this patch I propose adding a per md device max number of\ncorrected read attempts. Each rdev will maintain a count of\nread correction attempts in the rdev-\u003eread_errors field (not\nused currently for raid10). When we enter fix_read_error()\nwe\u0027ll check to see when the last read error occurred, and\ndivide the read error count by 2 for every hour since the\nlast read error. If at that point our read error count\nexceeds the read error threshold, we\u0027ll fail the raid device.\n\nIn addition in this patch I add sysfs nodes (get/set) for\nthe per md max_read_errors attribute, the rdev-\u003eread_errors\nattribute, and added some printk\u0027s to indicate when\nfix_read_error fails to repair an rdev.\n\nFor testing I used debugfs-\u003efail_make_request to inject\nIO errors to the rdev while doing IO to the raid array.\n\nSigned-off-by: Robert Becker \u003cRob.Becker@riverbed.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "43a705076e51c5af21ec4260a35699775ea298f5", "tree": "ff8e161d841c41992dbbcca2a844816411941c3c", "parents": [ "72e02075a33f739e21430262f71da8e82db9dbb3" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:55 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:51:41 2009 +1100" }, "message": "md: support updating bitmap parameters via sysfs.\n\nA new attribute directory \u0027bitmap\u0027 in \u0027md\u0027 is created which\ncontains files for configuring the bitmap.\n\u0027location\u0027 identifies where the bitmap is, either \u0027none\u0027,\nor \u0027file\u0027 or \u0027sector offset from metadata\u0027.\nWriting \u0027location\u0027 can create or remove a bitmap.\nAdding a \u0027file\u0027 bitmap this way is not yet supported.\n\u0027chunksize\u0027 and \u0027time_base\u0027 must be set before \u0027location\u0027\ncan be set.\n\n\u0027chunksize\u0027 can be set before creating a bitmap, but is\ncurrently always over-ridden by the bitmap superblock.\n\n\u0027time_base\u0027 and \u0027backlog\u0027 can be updated at any time.\n\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nReviewed-by: Andre Noll \u003cmaan@systemlinux.org\u003e\n" }, { "commit": "72e02075a33f739e21430262f71da8e82db9dbb3", "tree": "04a87a16751b714fe0fb41f28ccc54af9f820de1", "parents": [ "f6af949c5672115313cc3c976d85b0533f607d7e" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:55 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:51:41 2009 +1100" }, "message": "md: factor out parsing of fixed-point numbers\n\nsafe_delay_store can parse fixed point numbers (for fractions\nof a second). We will want to do that for another sysfs\nfile soon, so factor out the code.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "42a04b5078ce73a32f85762551d5703c5bd646a1", "tree": "3ef384933cd33d000516c292712da9a99e273360", "parents": [ "c3d9714e88c8685cf9bc837c3241fc005f95fb82" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:53 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:51:41 2009 +1100" }, "message": "md: move offset, daemon_sleep and chunksize out of bitmap structure\n\n... and into bitmap_info. These are all configuration parameters\nthat need to be set before the bitmap is created.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "c3d9714e88c8685cf9bc837c3241fc005f95fb82", "tree": "dd11e16ec911983bb7452bb4fb092769ba612e3b", "parents": [ "709ae4879ae33628ded276ce7da8cd5acfec476b" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:52 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:51:41 2009 +1100" }, "message": "md: collect bitmap-specific fields into one structure.\n\nIn preparation for making bitmap fields configurable via sysfs,\nstart tidying up by making a single structure to contain the\nconfiguration fields.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "a2826aa92e2e14db372eda01d333267258944033", "tree": "9cdd3329205bf480a4782705a3db1738e3faae44", "parents": [ "efa593390e70b0e3c39f6b2dca8876b6b1461e41" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:49 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:49 2009 +1100" }, "message": "md: support barrier requests on all personalities.\n\nPreviously barriers were only supported on RAID1. This is because\nother levels requires synchronisation across all devices and so needed\na different approach.\nHere is that approach.\n\nWhen a barrier arrives, we send a zero-length barrier to every active\ndevice. When that completes - and if the original request was not\nempty - we submit the barrier request itself (with the barrier flag\ncleared) and then submit a fresh load of zero length barriers.\n\nThe barrier request itself is asynchronous, but any subsequent\nrequest will block until the barrier completes.\n\nThe reason for clearing the barrier flag is that a barrier request is\nallowed to fail. If we pass a non-empty barrier through a striping\nraid level it is conceivable that part of it could succeed and part\ncould fail. That would be way too hard to deal with.\nSo if the first run of zero length barriers succeed, we assume all is\nsufficiently well that we send the request and ignore errors in the\nsecond run of barriers.\n\nRAID5 needs extra care as write requests may not have been submitted\nto the underlying devices yet. So we flush the stripe cache before\nproceeding with the barrier.\n\nNote that the second set of zero-length barriers are submitted\nimmediately after the original request is submitted. Thus when\na personality finds mddev-\u003ebarrier to be set during make_request,\nit should not return from make_request until the corresponding\nper-device request(s) have been queued.\n\nThat will be done in later patches.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nReviewed-by: Andre Noll \u003cmaan@systemlinux.org\u003e\n" }, { "commit": "efa593390e70b0e3c39f6b2dca8876b6b1461e41", "tree": "99c6071381f14f5ff59130779d988672aa78ee67", "parents": [ "c07b70ad32ed0a5ec9735cafb1aa10b3a2298b7d" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:49 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:49 2009 +1100" }, "message": "md: don\u0027t reset curr_resync_completed after an interrupted resync\n\nIf a resync/recovery/check/repair is interrupted for some reason, it\ncan be useful to know exactly where it got up to.\nSo in that case, do not clear curr_resync_completed.\nInitialise it when starting a resync/recovery/... instead.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "c07b70ad32ed0a5ec9735cafb1aa10b3a2298b7d", "tree": "451d88cd7e44ee8217a294335a04594bd573b828", "parents": [ "7820f9e1dddcfebae2698fb2a245d04ce3aa6e74" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:48 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:48 2009 +1100" }, "message": "md: adjust resync_min usefully when resync aborts.\n\nWhen a \u0027check\u0027 or \u0027repair\u0027 finished we should clear resync_min\nso that a future check/repair will cover the whole array (by default).\nHowever if it is interrupted, we should update resync_min to\nwhere we got up to, so that when the check/repair continues it\njust does the remainder of the array.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "aa5cbd103887011b4830355f88fb055f9ad2d556", "tree": "92ef7c80999c6d0bfc6fef9a9cd3e4a75ee16c06", "parents": [ "f40542532e96dda5506eb76badea322f2ae4731c" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:46 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:46 2009 +1100" }, "message": "md/bitmap: protect against bitmap removal while being updated.\n\nA write intent bitmap can be removed from an array while the\narray is active.\nWhen this happens, all IO is suspended and flushed before the\nbitmap is removed.\nHowever it is possible that bitmap_daemon_work is still running to\nclear old bits from the bitmap. If it is, it can dereference the\nbitmap after it has been freed.\n\nSo introduce a new mutex to protect bitmap_daemon_work and get it\nbefore destroying a bitmap.\n\nThis is suitable for any current -stable kernel.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\nCc: stable@kernel.org\n" }, { "commit": "1557d33007f63dd96e5d15f33af389378e5f2e54", "tree": "06d05722b2ba5d2a67532f779fa8a88efe3c88f1", "parents": [ "6ec22f9b037fc0c2e00ddb7023fad279c365324d", "c656ae95d1c5c8ed5763356263ace2d03087efec" ], "author": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Dec 08 07:38:50 2009 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Tue Dec 08 07:38:50 2009 -0800" }, "message": "Merge git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/sysctl-2.6\n\n* git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/sysctl-2.6: (43 commits)\n security/tomoyo: Remove now unnecessary handling of security_sysctl.\n security/tomoyo: Add a special case to handle accesses through the internal proc mount.\n sysctl: Drop \u0026 in front of every proc_handler.\n sysctl: Remove CTL_NONE and CTL_UNNUMBERED\n sysctl: kill dead ctl_handler definitions.\n sysctl: Remove the last of the generic binary sysctl support\n sysctl net: Remove unused binary sysctl code\n sysctl security/tomoyo: Don\u0027t look at ctl_name\n sysctl arm: Remove binary sysctl support\n sysctl x86: Remove dead binary sysctl support\n sysctl sh: Remove dead binary sysctl support\n sysctl powerpc: Remove dead binary sysctl support\n sysctl ia64: Remove dead binary sysctl support\n sysctl s390: Remove dead sysctl binary support\n sysctl frv: Remove dead binary sysctl support\n sysctl mips/lasat: Remove dead binary sysctl support\n sysctl drivers: Remove dead binary sysctl support\n sysctl crypto: Remove dead binary sysctl support\n sysctl security/keys: Remove dead binary sysctl support\n sysctl kernel: Remove binary sysctl logic\n ...\n" }, { "commit": "6d4561110a3e9fa742aeec6717248a491dfb1878", "tree": "689e2abf19940416ce597ba56ed31026ff59bd21", "parents": [ "86926d0096279b9739ceeff40f68d3c33b9119a9" ], "author": { "name": "Eric W. Biederman", "email": "ebiederm@xmission.com", "time": "Mon Nov 16 03:11:48 2009 -0800" }, "committer": { "name": "Eric W. Biederman", "email": "ebiederm@xmission.com", "time": "Wed Nov 18 08:37:40 2009 -0800" }, "message": "sysctl: Drop \u0026 in front of every proc_handler.\n\nFor consistency drop \u0026 in front of every proc_handler. Explicity\ntaking the address is unnecessary and it prevents optimizations\nlike stubbing the proc_handlers to NULL.\n\nCc: Alexey Dobriyan \u003cadobriyan@gmail.com\u003e\nCc: Ingo Molnar \u003cmingo@elte.hu\u003e\nCc: Joe Perches \u003cjoe@perches.com\u003e\nSigned-off-by: Eric W. Biederman \u003cebiederm@xmission.com\u003e\n" }, { "commit": "bb9074ff58fe745e4f244f76209241909c82ec9c", "tree": "cf6be00ab88b1e315f6b74a896a370440f677599", "parents": [ "4739a9748e1bd7459f22f7e94e7d85710ca83954", "156171c71a0dc4bce12b4408bb1591f8fe32dc1a" ], "author": { "name": "Eric W. Biederman", "email": "ebiederm@xmission.com", "time": "Tue Nov 17 01:01:34 2009 -0800" }, "committer": { "name": "Eric W. Biederman", "email": "ebiederm@xmission.com", "time": "Tue Nov 17 01:01:34 2009 -0800" }, "message": "Merge commit \u0027v2.6.32-rc7\u0027\n\nResolve the conflict between v2.6.32-rc7 where dn_def_dev_handler\ngets a small bug fix and the sysctl tree where I am removing all\nsysctl strategy routines.\n" }, { "commit": "0261cd9f1cb42fa44ece314d27868d83742bdf03", "tree": "95954fb2e1a10ee1b20198b8fbefd7a8392dc896", "parents": [ "5e8651060cea6b44844521ddcac665e2c021f5d8" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Nov 13 17:40:48 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Nov 13 17:40:48 2009 +1100" }, "message": "md: allow v0.91 metadata to record devices as being active but not in-sync.\n\nThis is a combination that didn\u0027t really make sense before.\nHowever when a reshape is converting e.g. raid5 -\u003e raid6, the extra\ndevice is not fully in-sync, but is certainly active and contains\nimportant data.\nSo allow that start to be meaningful and in particular get\nthe \u0027recovery_offset\u0027 value (which is needed for any non-in-sync\nactive device) from the reshape_position.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "894d2491153a9f8270dbed21175d06fde4eba6c7", "tree": "e49698028c4a953f4b31363a0225c7fab28cffc0", "parents": [ "c2a86a67fadd9dddc58f55ce6323c04dde59ebed" ], "author": { "name": "Eric W. Biederman", "email": "ebiederm@xmission.com", "time": "Thu Nov 05 14:34:02 2009 -0800" }, "committer": { "name": "Eric W. Biederman", "email": "ebiederm@xmission.com", "time": "Thu Nov 12 02:04:58 2009 -0800" }, "message": "sysctl drivers: Remove dead binary sysctl support\n\nNow that sys_sysctl is a wrapper around /proc/sys all of\nthe binary sysctl support elsewhere in the tree is\ndead code.\n\nCc: Jens Axboe \u003caxboe@kernel.dk\u003e\nCc: Corey Minyard \u003cminyard@acm.org\u003e\nCc: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\nCc: Matt Mackall \u003cmpm@selenic.com\u003e\nCc: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\nCc: Neil Brown \u003cneilb@suse.de\u003e\nCc: \"James E.J. Bottomley\" \u003cJames.Bottomley@suse.de\u003e\nAcked-by: Clemens Ladisch \u003cclemens@ladisch.de\u003e for drivers/char/hpet.c\nSigned-off-by: Eric W. Biederman \u003cebiederm@xmission.com\u003e\n" } ], "next": "5e8651060cea6b44844521ddcac665e2c021f5d8" }