)]}' { "log": [ { "commit": "7820f9e1dddcfebae2698fb2a245d04ce3aa6e74", "tree": "fd8853ea31528663d0f81167c92431e7a13f0781", "parents": [ "8553fe7ec731e4f997245e14319572cb15118018" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:47 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Dec 14 12:49:47 2009 +1100" }, "message": "md: remove sparse warning:symbol XXX was not declared.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "cdc2ae6d6a30df8fd92c5e300d0e3005e13eb6b0", "tree": "f64a34e565e8b8c8e983b278d9f17162a0f76ecc", "parents": [ "0ba459d26260d4d13346c76642f461b2bf607eef" ], "author": { "name": "Andre Noll", "email": "maan@systemlinux.org", "time": "Thu Jun 18 08:46:47 2009 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Thu Jun 18 08:46:47 2009 +1000" }, "message": "md: fix some comments.\n\n1/ Raid5 has learned to take over also raid4 and raid6 arrays.\n2/ new_chunk in mdp_superblock_1 is in sectors, not bytes.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "f701d589aa34d7531183c9ac6f7713ba14212b02", "tree": "d388cd7fa54c520f12233470a35ebb0676677e7a", "parents": [ "18b0033491f584a2d79697da714b1ef9d6b27d22" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Tue Mar 31 15:09:39 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 15:09:39 2009 +1100" }, "message": "md/raid6: move raid6 data processing to raid6_pq.ko\n\nMove the raid6 data processing routines into a standalone module\n(raid6_pq) to prepare them to be called from async_tx wrappers and other\nnon-md drivers/modules. This precludes a circular dependency of raid456\nneeding the async modules for data processing while those modules in\nturn depend on raid456 for the base level synchronous raid6 routines.\n\nTo support this move:\n1/ The exportable definitions in raid6.h move to include/linux/raid/pq.h\n2/ The raid6_call, recovery calls, and table symbols are exported\n3/ Extra #ifdef __KERNEL__ statements to enable the userspace raid6test to\n compile\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "43b2e5d86d8bdd77386226db0bc961529492c043", "tree": "601a885b1410324678cf319eee77cc54a02f2cf3", "parents": [ "bff61975b3d6c18ee31457cc5b4d73042f44915f" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:33:13 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:33:13 2009 +1100" }, "message": "md: move md_k.h from include/linux/raid/ to drivers/md/\n\nIt really is nicer to keep related code together..\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "bff61975b3d6c18ee31457cc5b4d73042f44915f", "tree": "3aff48088b35172e74f56ae54f0b53e76a0c2150", "parents": [ "92022950c6b1bb3da90b2976b20271cdfd98b8a3" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:33:13 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:33:13 2009 +1100" }, "message": "md: move lots of #include lines out of .h files and into .c\n\nThis makes the includes more explicit, and is preparation for moving\nmd_k.h to drivers/md/md.h\n\nRemove include/raid/md.h as its only remaining use was to #include\nother files.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "92022950c6b1bb3da90b2976b20271cdfd98b8a3", "tree": "5405257242ddcadef6e90ea597289558de4e03f2", "parents": [ "8b2b5c217c20b5460218ab8731295f2e46c7dd29" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:33:13 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:33:13 2009 +1100" }, "message": "md: move most content from md.h to md_k.h\n\nThe extern function definitions are kernel-internal definitions, so\nthey belong in md_k.h\n\nThe MD_*_VERSION values could reasonably go in a number of places,\nbut md_u.h seems most reasonable.\n\nThis leaves almost nothing in md.h. It will go soon.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "8b2b5c217c20b5460218ab8731295f2e46c7dd29", "tree": "f5da8b06b3d2a53e80c31e0c0aa386e381b3a841", "parents": [ "ef740c372dfd80e706dbf955d4e4aedda6c0c148" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:27:03 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:27:03 2009 +1100" }, "message": "md: move LEVEL_* definition from md_k.h to md_u.h\n\n.. as they are part of the user-space interface.\nAlso move MdpMinorShift into there so we can remove duplication.\n\nLastly move mdp_major in. It is less obviously part of the user-space\ninterface, but do_mounts_md.c uses it, and it is acting a bit like\nuser-space.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "ef740c372dfd80e706dbf955d4e4aedda6c0c148", "tree": "8d9ef9db346ee1ba319a125c9de83cdde049510d", "parents": [ "2a40a8aed083d988df6822bb9b1b08fb7ce21e1d" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Tue Mar 31 14:27:03 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:27:03 2009 +1100" }, "message": "md: move headers out of include/linux/raid/\n\nMove the headers with the local structures for the disciplines and\nbitmap.h into drivers/md/ so that they are more easily grepable for\nhacking and not far away. md.h is left where it is for now as there\nare some uses from the outside.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "eea1bf384e05b5ab747f8530c4fba9e9e6907fff", "tree": "ed4c05f8bd7e5805092e9c6a2c257ca71dc0fe2d", "parents": [ "99adcd9d67aaf04e28f5ae96df280f236bde4b66" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:27:02 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 31 14:27:02 2009 +1100" }, "message": "md: Fix is_mddev_idle test (again).\n\nThere are two problems with is_mddev_idle.\n\n1/ sync_io is \u0027atomic_t\u0027 and hence \u0027int\u0027. curr_events and all the\n rest are \u0027long\u0027.\n So if sync_io were to wrap on a 64bit host, the value of\n curr_events would go very negative suddenly, and take a very\n long time to return to positive.\n\n So do all calculations as \u0027int\u0027. That gives us plenty of precision\n for what we need.\n\n2/ To initialise rdev-\u003elast_events we simply call is_mddev_idle, on\n the assumption that it will make sure that last_events is in a\n suitable range. It used to do this, but now it does not.\n So now we need to be more explicit about initialisation.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "bcf74582af3feca80ec96cc21d0a26c938d1863e", "tree": "5649b38f3f26a3eff1ead14cf00e908aa8030306", "parents": [ "03cf1e0c3b4ee4ef51dc7eb197a4d098ad4873af" ], "author": { "name": "Jaswinder Singh Rajput", "email": "jaswinderrajput@gmail.com", "time": "Fri Jan 30 20:06:44 2009 +0530" }, "committer": { "name": "Jaswinder Singh Rajput", "email": "jaswinderrajput@gmail.com", "time": "Fri Jan 30 23:32:45 2009 +0530" }, "message": "headers_check fix: raid/md_p.h\n\nfix the following \u0027make headers_check\u0027 warning:\n\n usr/include/linux/raid/md_p.h:85: found __[us]{8,16,32,64} type without #include \u003clinux/types.h\u003e\n\nSigned-off-by: Jaswinder Singh Rajput \u003cjaswinderrajput@gmail.com\u003e\n" }, { "commit": "4044ba58dd15cb01797c4fd034f39ef4a75f7cc3", "tree": "e1bea8143538fc3eaeeb8578c2f9231e32809a25", "parents": [ "efeb53c0e57213e843b7ef3cc6ebcdea7d6186ac" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:11 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:11 2009 +1100" }, "message": "md: don\u0027t retry recovery of raid1 that fails due to error on source drive.\n\nIf a raid1 has only one working drive and it has a sector which\ngives an error on read, then an attempt to recover onto a spare will\nfail, but as the single remaining drive is not removed from the\narray, the recovery will be immediately re-attempted, resulting\nin an infinite recovery loop.\n\nSo detect this situation and don\u0027t retry recovery once an error\non the lone remaining drive is detected.\n\nAllow recovery to be retried once every time a spare is added\nin case the problem wasn\u0027t actually a media error.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "efeb53c0e57213e843b7ef3cc6ebcdea7d6186ac", "tree": "ef580effd8809fb0bc5d6ffa6f3b8abaa9180539", "parents": [ "d3374825ce57ba2214d375023979f6197ccc1385" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:10 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:10 2009 +1100" }, "message": "md: Allow md devices to be created by name.\n\nUsing sequential numbers to identify md devices is somewhat artificial.\nUsing names can be a lot more user-friendly.\n\nAlso, creating md devices by opening the device special file is a bit\nawkward.\n\nSo this patch provides a new option for creating and naming devices.\n\nWriting a name such as \"md_home\" to\n /sys/modules/md_mod/parameters/new_array\nwill cause an array with that name to be created. It will appear in\n/sys/block/ /proc/partitions and /proc/mdstat as \u0027md_home\u0027.\nIt will have an arbitrary minor number allocated.\n\nmd devices that a created by an open are destroyed on the last\nclose when the device is inactive.\nFor named md devices, they will not be destroyed until the array\nis explicitly stopped, either with the STOP_ARRAY ioctl or by\nwriting \u0027clear\u0027 to /sys/block/md_XXXX/md/array_state.\n\nThe name of the array must start \u0027md_\u0027 to avoid conflict with\nother devices.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "d3374825ce57ba2214d375023979f6197ccc1385", "tree": "441ea927a7c702e4eadeafbac8be97d664bfb83b", "parents": [ "a21d15042d8cd736caf82c2bac564f3f93f3d017" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:10 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:10 2009 +1100" }, "message": "md: make devices disappear when they are no longer needed.\n\nCurrently md devices, once created, never disappear until the module\nis unloaded. This is essentially because the gendisk holds a\nreference to the mddev, and the mddev holds a reference to the\ngendisk, this a circular reference.\n\nIf we drop the reference from mddev to gendisk, then we need to ensure\nthat the mddev is destroyed when the gendisk is destroyed. However it\nis not possible to hook into the gendisk destruction process to enable\nthis.\n\nSo we drop the reference from the gendisk to the mddev and destroy the\ngendisk when the mddev gets destroyed. However this has a\ncomplication.\nBetween the call\n __blkdev_get-\u003eget_gendisk-\u003ekobj_lookup-\u003emd_probe\nand the call\n __blkdev_get-\u003emd_open\n\nthere is no obvious way to hold a reference on the mddev any more, so\nunless something is done, it will disappear and gendisk will be\ndestroyed prematurely.\n\nAlso, once we decide to destroy the mddev, there will be an unlockable\nmoment before the gendisk is unlinked (blk_unregister_region) during\nwhich a new reference to the gendisk can be created. We need to\nensure that this reference can not be used. i.e. the -\u003eopen must\nfail.\n\nSo:\n 1/ in md_probe we set a flag in the mddev (hold_active) which\n indicates that the array should be treated as active, even\n though there are no references, and no appearance of activity.\n This is cleared by md_release when the device is closed if it\n is no longer needed.\n This ensures that the gendisk will survive between md_probe and\n md_open.\n\n 2/ In md_open we check if the mddev we expect to open matches\n the gendisk that we did open.\n If there is a mismatch we return -ERESTARTSYS and modify\n __blkdev_get to retry from the top in that case.\n In the -ERESTARTSYS sys case we make sure to wait until\n the old gendisk (that we succeeded in opening) is really gone so\n we loop at most once.\n\nSome udev configurations will always open an md device when it first\nappears. If we allow an md device that was just created by an open\nto disappear on an immediate close, then this can race with such udev\nconfigurations and result in an infinite loop the device being opened\nand closed, then re-open due to the \u0027ADD\u0027 even from the first open,\nand then close and so on.\nSo we make sure an md device, once created by an open, remains active\nat least until some md \u0027ioctl\u0027 has been made on it. This means that\nall normal usage of md devices will allow them to disappear promptly\nwhen not needed, but the worst that an incorrect usage will do it\ncause an inactive md device to be left in existence (it can easily be\nremoved).\n\nAs an array can be stopped by writing to a sysfs attribute\n echo clear \u003e /sys/block/mdXXX/md/array_state\nwe need to use scheduled work for deleting the gendisk and other\nkobjects. This allows us to wait for any pending gendisk deletion to\ncomplete by simply calling flush_scheduled_work().\n\n\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "cd2ac9321c26dc7a76455cd2a4df89123fa2b73e", "tree": "8163a2cc791282cf32fafed19a60f357882d6169", "parents": [ "159ec1fc060ab22b157a62364045f5e98749c4d3" ], "author": { "name": "Cheng Renquan", "email": "crquan@gmail.com", "time": "Fri Jan 09 08:31:08 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:08 2009 +1100" }, "message": "md: need another print_sb for mdp_superblock_1\n\nmd_print_devices is called in two code path: MD_BUG(...), and md_ioctl\nwith PRINT_RAID_DEBUG. it will dump out all in use md devices\ninformation;\n\nHowever, it wrongly processed two types of superblock in one:\n\nThe header file \u003clinux/raid/md_p.h\u003e has defined two types of superblock,\nstruct mdp_superblock_s (typedefed with mdp_super_t) according to md with\nmetadata 0.90, and struct mdp_superblock_1 according to md with metadata\n1.0 and later,\n\nThese two types of superblock are very different,\n\nThe md_print_devices code processed them both in mdp_super_t, that would\nlead to wrong informaton dump like:\n\n\t[ 6742.345877]\n\t[ 6742.345887] md:\t**********************************\n\t[ 6742.345890] md:\t* \u003cCOMPLETE RAID STATE PRINTOUT\u003e *\n\t[ 6742.345892] md:\t**********************************\n\t[ 6742.345896] md1: \u003cram7\u003e\u003cram6\u003e\u003cram5\u003e\u003cram4\u003e\n\t[ 6742.345907] md: rdev ram7, SZ:00065472 F:0 S:1 DN:3\n\t[ 6742.345909] md: rdev superblock:\n\t[ 6742.345914] md: SB: (V:0.90.0) ID:\u003c42ef13c7.598c059a.5f9f1645.801e9ee6\u003e CT:4919856d\n\t[ 6742.345918] md: L5 S00065472 ND:4 RD:4 md1 LO:2 CS:65536\n\t[ 6742.345922] md: UT:4919856d ST:1 AD:4 WD:4 FD:0 SD:0 CSUM:b7992907 E:00000001\n\t[ 6742.345924] D 0: DISK\u003cN:0,(1,8),R:0,S:6\u003e\n\t[ 6742.345930] D 1: DISK\u003cN:1,(1,10),R:1,S:6\u003e\n\t[ 6742.345933] D 2: DISK\u003cN:2,(1,12),R:2,S:6\u003e\n\t[ 6742.345937] D 3: DISK\u003cN:3,(1,14),R:3,S:6\u003e\n\t[ 6742.345942] md: THIS: DISK\u003cN:3,(1,14),R:3,S:6\u003e\n\t...\n\t[ 6742.346058] md0: \u003cram3\u003e\u003cram2\u003e\u003cram1\u003e\u003cram0\u003e\n\t[ 6742.346067] md: rdev ram3, SZ:00065472 F:0 S:1 DN:3\n\t[ 6742.346070] md: rdev superblock:\n\t[ 6742.346073] md: SB: (V:1.0.0) ID:\u003c369aad81.00000000.00000000.00000000\u003e CT:9a322a9c\n\t[ 6742.346077] md: L-1507699579 S976570180 ND:48 RD:0 md0 LO:65536 CS:196610\n\t[ 6742.346081] md: UT:00000018 ST:0 AD:131048 WD:0 FD:8 SD:0 CSUM:00000000 E:00000000\n\t[ 6742.346084] D 0: DISK\u003cN:-1,(-1,-1),R:-1,S:-1\u003e\n\t[ 6742.346089] D 1: DISK\u003cN:-1,(-1,-1),R:-1,S:-1\u003e\n\t[ 6742.346092] D 2: DISK\u003cN:-1,(-1,-1),R:-1,S:-1\u003e\n\t[ 6742.346096] D 3: DISK\u003cN:-1,(-1,-1),R:-1,S:-1\u003e\n\t[ 6742.346102] md: THIS: DISK\u003cN:0,(0,0),R:0,S:0\u003e\n\t...\n\t[ 6742.346219] md:\t**********************************\n\t[ 6742.346221]\n\nHere md1 is metadata 0.90.0, and md0 is metadata 1.2\n\nAfter some more code to distinguish these two types of superblock, in this patch,\n\nit will generate dump information like:\n\n\t[ 7906.755790]\n\t[ 7906.755799] md:\t**********************************\n\t[ 7906.755802] md:\t* \u003cCOMPLETE RAID STATE PRINTOUT\u003e *\n\t[ 7906.755804] md:\t**********************************\n\t[ 7906.755808] md1: \u003cram7\u003e\u003cram6\u003e\u003cram5\u003e\u003cram4\u003e\n\t[ 7906.755819] md: rdev ram7, SZ:00065472 F:0 S:1 DN:3\n\t[ 7906.755821] md: rdev superblock (MJ:0):\n\t[ 7906.755826] md: SB: (V:0.90.0) ID:\u003c3fca7a0d.a612bfed.5f9f1645.801e9ee6\u003e CT:491989f3\n\t[ 7906.755830] md: L5 S00065472 ND:4 RD:4 md1 LO:2 CS:65536\n\t[ 7906.755834] md: UT:491989f3 ST:1 AD:4 WD:4 FD:0 SD:0 CSUM:00fb52ad E:00000001\n\t[ 7906.755836] D 0: DISK\u003cN:0,(1,8),R:0,S:6\u003e\n\t[ 7906.755842] D 1: DISK\u003cN:1,(1,10),R:1,S:6\u003e\n\t[ 7906.755845] D 2: DISK\u003cN:2,(1,12),R:2,S:6\u003e\n\t[ 7906.755849] D 3: DISK\u003cN:3,(1,14),R:3,S:6\u003e\n\t[ 7906.755855] md: THIS: DISK\u003cN:3,(1,14),R:3,S:6\u003e\n\t...\n\t[ 7906.755972] md0: \u003cram3\u003e\u003cram2\u003e\u003cram1\u003e\u003cram0\u003e\n\t[ 7906.755981] md: rdev ram3, SZ:00065472 F:0 S:1 DN:3\n\t[ 7906.755984] md: rdev superblock (MJ:1):\n\t[ 7906.755989] md: SB: (V:1) (F:0) Array-ID:\u003c5fbcf158:55aa:5fbe:9a79:1e939880dcbd\u003e\n\t[ 7906.755990] md: Name: \"DG5:0\" CT:1226410480\n\t[ 7906.755998] md: L5 SZ130944 RD:4 LO:2 CS:128 DO:24 DS:131048 SO:8 RO:0\n\t[ 7906.755999] md: Dev:00000003 UUID: 9194d744:87f7:a448:85f2:7497b84ce30a\n\t[ 7906.756001] md: (F:0) UT:1226410480 Events:0 ResyncOffset:-1 CSUM:0dbcd829\n\t[ 7906.756003] md: (MaxDev:384)\n\t...\n\t[ 7906.756113] md:\t**********************************\n\t[ 7906.756116]\n\nthis md0 (metadata 1.2) information dumping is exactly according to struct\nmdp_superblock_1.\n\nSigned-off-by: Cheng Renquan \u003ccrquan@gmail.com\u003e\nCc: Neil Brown \u003cneilb@suse.de\u003e\nCc: Dan Williams \u003cdan.j.williams@gmail.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "159ec1fc060ab22b157a62364045f5e98749c4d3", "tree": "1de0edfd782245b271d2898e36ae76c00e1e1b6d", "parents": [ "ccacc7d2cf03114a24ab903f710118e9e5d43273" ], "author": { "name": "Cheng Renquan", "email": "crquan@gmail.com", "time": "Fri Jan 09 08:31:08 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:08 2009 +1100" }, "message": "md: use list_for_each_entry macro directly\n\nThe rdev_for_each macro defined in \u003clinux/raid/md_k.h\u003e is identical to\nlist_for_each_entry_safe, from \u003clinux/list.h\u003e, it should be defined to\nuse list_for_each_entry_safe, instead of reinventing the wheel.\n\nBut some calls to each_entry_safe don\u0027t really need a safe version,\njust a direct list_for_each_entry is enough, this could save a temp\nvariable (tmp) in every function that used rdev_for_each.\n\nIn this patch, most rdev_for_each loops are replaced by list_for_each_entry,\ntotally save many tmp vars; and only in the other situations that will call\nlist_del to delete an entry, the safe version is used.\n\nSigned-off-by: Cheng Renquan \u003ccrquan@gmail.com\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "ccacc7d2cf03114a24ab903f710118e9e5d43273", "tree": "c856e2a17f6c6a26996a8cfba87680a2375061d5", "parents": [ "83838ed87898e0a8ff8dbf001e54e6c017f0a011" ], "author": { "name": "Andre Noll", "email": "maan@systemlinux.org", "time": "Fri Jan 09 08:31:08 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:08 2009 +1100" }, "message": "md: raid0: make hash_spacing and preshift sector-based.\n\nThis patch renames the hash_spacing and preshift members of struct\nraid0_private_data to spacing and sector_shift respectively and\nchanges the semantics as follows:\n\nWe always have spacing \u003d 2 * hash_spacing. In case\nsizeof(sector_t) \u003e sizeof(u32) we also have sector_shift \u003d preshift + 1\nwhile sector_shift \u003d preshift \u003d 0 otherwise.\n\nNote that the values of nb_zone and zone are unaffected by these changes\nbecause in the sector_div() preceeding the assignement of these two\nvariables both arguments double.\n\nSigned-off-by: Andre Noll \u003cmaan@systemlinux.org\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "83838ed87898e0a8ff8dbf001e54e6c017f0a011", "tree": "218e6c8dbe52257251f165cd544c4bebbeae3c40", "parents": [ "0825b87a7dd9645c7e16489fec839a3cb5c40a08" ], "author": { "name": "Andre Noll", "email": "maan@systemlinux.org", "time": "Fri Jan 09 08:31:07 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:07 2009 +1100" }, "message": "md: raid0: Represent the size of strip zones in sectors.\n\nThis completes the block -\u003e sector conversion of struct strip_zone.\n\nSigned-off-by: Andre Noll \u003cmaan@systemlinux.org\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "6199d3db0fc34f8ada895879d04a353a6ae632bc", "tree": "5a7d5f4a080abf6c46a87f121a859fd45fd53254", "parents": [ "019c4e2f3e02aac4b44003913b54ca4b332e4371" ], "author": { "name": "Andre Noll", "email": "maan@systemlinux.org", "time": "Fri Jan 09 08:31:07 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:07 2009 +1100" }, "message": "md: raid0: Represent zone-\u003ezone_offset in sectors.\n\nFor the same reason as in the previous patch, rename it from zone_offset\nto zone_start.\n\nSigned-off-by: Andre Noll \u003cmaan@systemlinux.org\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "019c4e2f3e02aac4b44003913b54ca4b332e4371", "tree": "ebdd73075be543d5feb1a1e86a793a2b3311ea9b", "parents": [ "e0f06868341700c5c1964a04f6c5b51d0a2d5bca" ], "author": { "name": "Andre Noll", "email": "maan@systemlinux.org", "time": "Fri Jan 09 08:31:06 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:06 2009 +1100" }, "message": "md: raid0: Represent device offset in sectors.\n\nRename zone-\u003edev_offset to zone-\u003edev_start to make sure all users\nhave been converted.\n\nSigned-off-by: Andre Noll \u003cmaan@systemlinux.org\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "0c3573f19d135d718264e38c46597295bd6154b7", "tree": "0943035f89d163d9d7b354445303fb03e5ea7fb1", "parents": [ "538452700d95480c16e7aa6b10ff77cd937d33f4" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:05 2009 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 09 08:31:05 2009 +1100" }, "message": "md: use sysfs_notify_dirent to notify changes to md/sync_action.\n\nThere is no compelling need for this, but sysfs_notify_dirent is a\nnicer interface and the change is good for consistency.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "3c0ee63a64a20351ed6c16ec797e1f8c850741ea", "tree": "482b825a00356a2b7b605065ce1d6ebe87591eb5", "parents": [ "b62b75905d571c29262a6c38cf9e5f089c203871" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Oct 21 13:25:28 2008 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Oct 21 13:25:28 2008 +1100" }, "message": "md: use sysfs_notify_dirent to notify changes to md/dev-xxx/state\n\nThe \u0027state\u0027 file for a device reports, for example, when the device\nhas failed. Changes should be reported to userspace ASAP without\nthe possibility of blocking on low-memory. sysfs_notify does\nhave that possibility (as it takes a mutex which can be held\nacross a kmalloc) so use sysfs_notify_dirent instead.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "b62b75905d571c29262a6c38cf9e5f089c203871", "tree": "0ca9a74c1d53aad0532aaebebb031b9d8edc5d90", "parents": [ "0cfd81031a26717fe14380d18275f8e217571615" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Oct 21 13:25:21 2008 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Oct 21 13:25:21 2008 +1100" }, "message": "md: use sysfs_notify_dirent to notify changes to md/array_state\n\nNow that we have sysfs_notify_dirent, use it to notify changes\nto md/array_state.\nAs sysfs_notify_dirent can be called in atomic context, we can\nremove the delayed notify and the MD_NOTIFY_ARRAY_STATE flag.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "d710e13812600037a723a673dc5c96a071de98d3", "tree": "df8e34fb02cb7909090aa697da7c1db4814ee122", "parents": [ "fb4d8c76e56a887b9eee99fbc55fe82b18625d30" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Oct 13 11:55:12 2008 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Oct 13 11:55:12 2008 +1100" }, "message": "md: remove space after function name in declaration and call.\n\nHaving\n function (args)\ninstead of\n function(args)\n\nmake is harder to search for calls of particular functions.\nSo remove all those spaces.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "fb4d8c76e56a887b9eee99fbc55fe82b18625d30", "tree": "0ca96887e40db671957b79d493830b9527b04949", "parents": [ "ab5bd5cbc8d4b868378d062eed3d4240930fbb86" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Oct 13 11:55:12 2008 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Oct 13 11:55:12 2008 +1100" }, "message": "md: Remove unnecessary #includes, #defines, and function declarations.\n\nA lot of cruft has gathered over the years. Time to remove it.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "ab5bd5cbc8d4b868378d062eed3d4240930fbb86", "tree": "39c6299f79398d7f00b50c4ba39c52e2aea22e00", "parents": [ "23242fbb470ff4c8c4d41f178832cf1929273d7d" ], "author": { "name": "Andre Noll", "email": "maan@systemlinux.org", "time": "Mon Oct 13 11:55:12 2008 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Oct 13 11:55:12 2008 +1100" }, "message": "md: Convert remaining 1k representations in linear.c to sectors.\n\nThis patch renames hash_spacing and preshift to spacing and\nsector_shift respectively with the following change of semantics:\n\nCase 1: (sizeof(sector_t) \u003c\u003d sizeof(u32)).\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\nIn this case, we have sector_shift \u003d preshift \u003d 0 and spacing \u003d\n2 * hash_spacing.\n\nHence, the index for the hash table which is computed by the new code\nin which_dev() as sector / spacing equals the old value which was\n(sector/2) / hash_spacing.\n\nNote also that the value of nb_zone stays the same because both sz\nand base double.\n\nCase 2: (sizeof(sector_t) \u003e sizeof(u32)).\n~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\n(aka the shifting dance case). Here we have sector_shift \u003d preshift +\n1 and\n\nspacing \u003d 2 * hash_spacing\n\nduring the computation of nb_zone and curr_sector, but\n\nspacing \u003d hash_spacing\n\nin which_dev() because in the last hunk of the patch for linear.c we\nshift down conf-\u003espacing (\u003d 2 * hash_spacing) by one more bit than\nin the old code.\n\nHence in the computation of nb_zone, sz and base have the same value\nas before, so nb_zone is not affected. Also curr_sector in the next\nhunk stays the same.\n\nIn which_dev() the hash table index is computed as\n\n(sector \u003e\u003e sector_shift) / spacing\n\nIn view of sector_shift \u003d preshift + 1 and spacing \u003d hash_spacing,\nthis equals\n\n((sector/2) \u003e\u003e preshift) / hash_spacing\n\nwhich is the value computed by the old code.\n\nSigned-off-by: Andre Noll \u003cmaan@systemlinux.org\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "6283815d1853b7daf31dc4adb83e5c1dc9568251", "tree": "cd4f00ce17e7c274091ca9015b164d6f06611975", "parents": [ "451708d2a439accbce136637ed4f156fc27371ab" ], "author": { "name": "Andre Noll", "email": "maan@systemlinux.org", "time": "Mon Oct 13 11:55:12 2008 +1100" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Oct 13 11:55:12 2008 +1100" }, "message": "md: linear: Represent dev_info-\u003esize and dev_info-\u003eoffset in sectors.\n\nRename them to num_sectors and start_sector which is more descriptive.\n\nSigned-off-by: Andre Noll \u003cmaan@systemlinux.org\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "d8e64406a037a64444175730294e449c9e21f5ec", "tree": "5ac7525899ebc1d2fd9a83a6e19cd0b1b1b1711d", "parents": [ "2339788376e2d69a9154130e4dacd5b21ce63094" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Wed Jul 23 13:09:48 2008 -0700" }, "committer": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Wed Jul 23 13:09:48 2008 -0700" }, "message": "md: delay notification of \u0027active_idle\u0027 to the recovery thread\n\nsysfs_notify might sleep, so do not call it from md_safemode_timeout.\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\n" }, { "commit": "4b80991c6cb9efa607bc4fd6f3ecdf5511c31bb0", "tree": "5e2ba7d509af245c29bdf04b00960cc367972c44", "parents": [ "f2ea68cf42aafdd93393b6b8b20fc3c2b5f4390c" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jul 21 17:05:25 2008 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jul 21 17:05:25 2008 +1000" }, "message": "md: Protect access to mddev-\u003edisks list using RCU\n\nAll modifications and most access to the mddev-\u003edisks list are made\nunder the reconfig_mutex lock. However there are three places where\nthe list is walked without any locking. If a reconfig happens at this\ntime, havoc (and oops) can ensue.\n\nSo use RCU to protect these accesses:\n - wrap them in rcu_read_{,un}lock()\n - use list_for_each_entry_rcu\n - add to the list with list_add_rcu\n - delete from the list with list_del_rcu\n - delay the \u0027free\u0027 with call_rcu rather than schedule_work\n\nNote that export_rdev did a list_del_init on this list. In almost all\ncases the entry was not in the list anymore so it was a no-op and so\nsafe. It is no longer safe as after list_del_rcu we may not touch\nthe list_head.\nAn audit shows that export_rdev is called:\n - after unbind_rdev_from_array, in which case the delete has\n already been done,\n - after bind_rdev_to_array fails, in which case the delete isn\u0027t needed.\n - before the device has been put on a list at all (e.g. in\n add_new_disk where reading the superblock fails).\n - and in autorun devices after a failure when the device is on a\n different list.\n\nSo remove the list_del_init call from export_rdev, and add it back\nimmediately before the called to export_rdev for that last case.\n\nNote also that -\u003esame_set is sometimes used for lists other than\nmddev-\u003elist (e.g. candidates). In these cases rcu is not needed.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "f2ea68cf42aafdd93393b6b8b20fc3c2b5f4390c", "tree": "00b025b91898ff32dba742b5075dd290fec4dc91", "parents": [ "d6e2215052810678bc9782fd980b52706fc71f50" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jul 21 17:05:25 2008 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jul 21 17:05:25 2008 +1000" }, "message": "md: only count actual openers as access which prevent a \u0027stop\u0027\n\nOpen isn\u0027t the only thing that increments -\u003eactive. e.g. reading\n/proc/mdstat will increment it briefly. So to avoid false positives\nin testing for concurrent access, introduce a new counter that counts\njust the number of times the md device it open.\n\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "d6e2215052810678bc9782fd980b52706fc71f50", "tree": "63f355d1e072b6c4c48913e114c0154a5b08d792", "parents": [ "f233ea5c9e0d8b95e4283bf6a3436b88f6fd3586" ], "author": { "name": "Andre Noll", "email": "maan@systemlinux.org", "time": "Mon Jul 21 17:05:25 2008 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jul 21 17:05:25 2008 +1000" }, "message": "md: linear: Make array_size sector-based and rename it to array_sectors.\n\nSigned-off-by: Andre Noll \u003cmaan@systemlinux.org\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "f233ea5c9e0d8b95e4283bf6a3436b88f6fd3586", "tree": "8a36b621de46da23f3957c6e3ea4d653c2937544", "parents": [ "15f4a5fdf3aa07b53f6a7969664741db5882e485" ], "author": { "name": "Andre Noll", "email": "maan@systemlinux.org", "time": "Mon Jul 21 17:05:22 2008 +1000" }, "committer": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jul 21 17:05:22 2008 +1000" }, "message": "md: Make mddev-\u003earray_size sector-based.\n\nThis patch renames the array_size field of struct mddev_s to array_sectors\nand converts all instances to use units of 512 byte sectors instead of 1k\nblocks.\n\nSigned-off-by: Andre Noll \u003cmaan@systemlinux.org\u003e\nSigned-off-by: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "7e93a89251d4ed7bd4475db62616ccd03ddfd01a", "tree": "8c419717a524629383ceeff42b53eda27b3a0433", "parents": [ "0f420358e3a2abc028320ace7783e2e38cae77bf" ], "author": { "name": "Andre Noll", "email": "maan@systemlinux.org", "time": "Fri Jul 11 22:02:23 2008 +1000" }, "committer": { "name": "Neil Brown", "email": "neilb@suse.de", "time": "Fri Jul 11 22:02:23 2008 +1000" }, "message": "md: Remove some unused macros.\n\nSigned-off-by: Andre Noll \u003cmaan@systemlinux.org\u003e\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\n" }, { "commit": "0f420358e3a2abc028320ace7783e2e38cae77bf", "tree": "99b068212ad1dd8c5e97b151d796d66f53d1f3bb", "parents": [ "b73df2d3d629aefa187a0a3574fd81455e026bc8" ], "author": { "name": "Andre Noll", "email": "maan@systemlinux.org", "time": "Fri Jul 11 22:02:23 2008 +1000" }, "committer": { "name": "Neil Brown", "email": "neilb@suse.de", "time": "Fri Jul 11 22:02:23 2008 +1000" }, "message": "md: Turn rdev-\u003esb_offset into a sector-based quantity.\n\nRename it to sb_start to make sure all users have been converted.\n\nSigned-off-by: Andre Noll \u003cmaan@systemlinux.org\u003e\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\n" }, { "commit": "b5470dc5fc18a8ff6517c3bb538d1479e58ecb02", "tree": "37b0eb3a4691bdbe58dc5c6c73b2dc8d3925b332", "parents": [ "1fe797e67fb07d605b82300934d0de67068a0aca" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Fri Jun 27 21:44:04 2008 -0700" }, "committer": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Mon Jun 30 17:18:19 2008 -0700" }, "message": "md: resolve external metadata handling deadlock in md_allow_write\n\nmd_allow_write() marks the metadata dirty while holding mddev-\u003elock and then\nwaits for the write to complete. For externally managed metadata this causes a\ndeadlock as userspace needs to take the lock to communicate that the metadata\nupdate has completed.\n\nChange md_allow_write() in the \u0027external\u0027 case to start the \u0027mark active\u0027\noperation and then return -EAGAIN. The expected side effects while waiting for\nuserspace to write \u0027active\u0027 to \u0027array_state\u0027 are holding off reshape (code\ncurrently handles -ENOMEM), cause some \u0027stripe_cache_size\u0027 change requests to\nfail, cause some GET_BITMAP_FILE ioctl requests to fall back to GFP_NOIO, and\ncause updates to \u0027raid_disks\u0027 to fail. Except for \u0027stripe_cache_size\u0027 changes\nthese failures can be mitigated by coordinating with mdmon.\n\nmd_write_start() still prevents writes from occurring until the metadata\nhandler has had a chance to take action as it unconditionally waits for\nMD_CHANGE_CLEAN to be cleared.\n\n[neilb@suse.de: return -EAGAIN, try GFP_NOIO]\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\n" }, { "commit": "d8ee0728b5b30d7a6f62c399a95e953616d31f23", "tree": "7f9fcf2b0f6222b2a2b8ee44d69af1fd6990064d", "parents": [ "600aa10993012ff2dd5617720dac081e4f992017" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Sat Jun 28 08:32:06 2008 +1000" }, "committer": { "name": "Neil Brown", "email": "neilb@notabene.brown", "time": "Sat Jun 28 08:32:06 2008 +1000" }, "message": "md: replace R5_WantPrexor with R5_WantDrain, add \u0027prexor\u0027 reconstruct_states\n\nFrom: Dan Williams \u003cdan.j.williams@intel.com\u003e\n\nCurrently ops_run_biodrain and other locations have extra logic to determine\nwhich blocks are processed in the prexor and non-prexor cases. This can be\neliminated if handle_write_operations5 flags the blocks to be processed in all\ncases via R5_Wantdrain. The presence of the prexor operation is tracked in\nsh-\u003ereconstruct_state.\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\n" }, { "commit": "600aa10993012ff2dd5617720dac081e4f992017", "tree": "ead3e928aaa45e68bc65ea9aedc513c5b9c3d2d6", "parents": [ "976ea8d475675da6e86bd434328814ccbf5ae641" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Sat Jun 28 08:32:05 2008 +1000" }, "committer": { "name": "Neil Brown", "email": "neilb@notabene.brown", "time": "Sat Jun 28 08:32:05 2008 +1000" }, "message": "md: replace STRIPE_OP_{BIODRAIN,PREXOR,POSTXOR} with \u0027reconstruct_states\u0027\n\nFrom: Dan Williams \u003cdan.j.williams@intel.com\u003e\n\nTrack the state of reconstruct operations (recalculating the parity block\nusually due to incoming writes, or as part of array expansion) Reduces the\nscope of the STRIPE_OP_{BIODRAIN,PREXOR,POSTXOR} flags to only tracking whether\na reconstruct operation has been requested via the ops_request field of struct\nstripe_head_state.\n\nThis is the final step in the removal of ops.{pending,ack,complete,count}, i.e.\nthe STRIPE_OP_{BIODRAIN,PREXOR,POSTXOR} flags only request an operation and do\nnot track the state of the operation.\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\n" }, { "commit": "ecc65c9b3f9b9d740a5deade3d85b39be56401b6", "tree": "e6b4e827befc6849716689f573c89aa0a41e5d26", "parents": [ "f0e43bcdebf709d747a3effb210aff1941e819ab" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Sat Jun 28 08:31:57 2008 +1000" }, "committer": { "name": "Neil Brown", "email": "neilb@notabene.brown", "time": "Sat Jun 28 08:31:57 2008 +1000" }, "message": "md: replace STRIPE_OP_CHECK with \u0027check_states\u0027\n\nFrom: Dan Williams \u003cdan.j.williams@intel.com\u003e\n\nThe STRIPE_OP_* flags record the state of stripe operations which are\nperformed outside the stripe lock. Their use in indicating which\noperations need to be run is straightforward; however, interpolating what\nthe next state of the stripe should be based on a given combination of\nthese flags is not straightforward, and has led to bugs. An easier to read\nimplementation with minimal degrees of freedom is needed.\n\nTowards this goal, this patch introduces explicit states to replace what was\npreviously interpolated from the STRIPE_OP_* flags. For now this only converts\nthe handle_parity_checks5 path, removing a user of the\nops.{pending,ack,complete,count} fields of struct stripe_operations.\n\nThis conversion also found a remaining issue with the current code. There is\na small window for a drive to fail between when we schedule a repair and when\nthe parity calculation for that repair completes. When this happens we will\nwriteback to \u0027failed_num\u0027 when we really want to write back to \u0027pd_idx\u0027.\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\n" }, { "commit": "2b7497f0e0a0b9cf21d822e427d5399b2056501a", "tree": "8cf4d8e056ddafe48d49af0d8afe600868d2d21b", "parents": [ "b203886edbcaac3ca427cf4dbcb50b18bdb346fd" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Sat Jun 28 08:31:52 2008 +1000" }, "committer": { "name": "Neil Brown", "email": "neilb@notabene.brown", "time": "Sat Jun 28 08:31:52 2008 +1000" }, "message": "md: kill STRIPE_OP_IO flag\n\nFrom: Dan Williams \u003cdan.j.williams@intel.com\u003e\n\nThe R5_Want{Read,Write} flags already gate i/o. So, this flag is\nsuperfluous and we can unconditionally call ops_run_io().\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\n" }, { "commit": "b203886edbcaac3ca427cf4dbcb50b18bdb346fd", "tree": "d96cf939fd3a7ab454f61110b91b3a928eb5fe7c", "parents": [ "0cd17fec983b6bca505eecee1af33138687220b6" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Sat Jun 28 08:31:50 2008 +1000" }, "committer": { "name": "Neil Brown", "email": "neilb@notabene.brown", "time": "Sat Jun 28 08:31:50 2008 +1000" }, "message": "md: kill STRIPE_OP_MOD_DMA in raid5 offload\n\nFrom: Dan Williams \u003cdan.j.williams@intel.com\u003e\n\nThis micro-optimization allowed the raid code to skip a re-read of the\nparity block after checking parity. It took advantage of the fact that\nxor-offload-engines have their own internal result buffer and can check\nparity without writing to memory. Remove it for the following reasons:\n\n1/ It is a layering violation for MD to need to manage the DMA and\n non-DMA paths within async_xor_zero_sum\n2/ Bad precedent to toggle the \u0027ops\u0027 flags outside the lock\n3/ Hard to realize a performance gain as reads will not need an updated\n parity block and writes will dirty it anyways.\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\n" }, { "commit": "526647320e696f434647f38421a6ecf65b859c43", "tree": "aa6bf13e6aa766051ba32a8b64157f4adf9fcd3e", "parents": [ "a99ac97113d5bc25ddc4d17f404c2024ac6c57f9" ], "author": { "name": "Neil Brown", "email": "neilb@notabene.brown", "time": "Sat Jun 28 08:31:44 2008 +1000" }, "committer": { "name": "Neil Brown", "email": "neilb@notabene.brown", "time": "Sat Jun 28 08:31:44 2008 +1000" }, "message": "Make sure all changes to md/dev-XX/state are notified\n\nThe important state change happens during an interrupt\nin md_error. So just set a flag there and call sysfs_notify\nlater in process context.\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\n" }, { "commit": "72a23c211e4587859d5bf61ac4962d76e593fb02", "tree": "b35b554d7eb9c4b3a2cbc4d9378d362e5e56e44f", "parents": [ "0fd62b861eac7d2dea9b7e939953b20f37186ea1" ], "author": { "name": "Neil Brown", "email": "neilb@notabene.brown", "time": "Sat Jun 28 08:31:41 2008 +1000" }, "committer": { "name": "Neil Brown", "email": "neilb@notabene.brown", "time": "Sat Jun 28 08:31:41 2008 +1000" }, "message": "Make sure all changes to md/sync_action are notified.\n\nWhen the \u0027resync\u0027 thread starts or stops, when we explicitly\nset sync_action, or when we determine that there is definitely nothing\nto do, we notify sync_action.\n\nTo stop \"sync_action\" from occasionally showing the wrong value,\nwe introduce a new flags - MD_RECOVERY_RECOVER - to say that a\nrecovery is probably needed or happening, and we make sure\nthat we set MD_RECOVERY_RUNNING before clearing MD_RECOVERY_NEEDED.\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\n" }, { "commit": "5e96ee65c8bd629ce093da67a066d3946468298a", "tree": "e1ff9e4984d71ffaa842e7e1d19c282fa9e01bcd", "parents": [ "a0da84f35b25875870270d16b6eccda4884d61a7" ], "author": { "name": "Neil Brown", "email": "neilb@notabene.brown", "time": "Sat Jun 28 08:31:24 2008 +1000" }, "committer": { "name": "Neil Brown", "email": "neilb@notabene.brown", "time": "Sat Jun 28 08:31:24 2008 +1000" }, "message": "Allow setting start point for requested check/repair\n\nThis makes it possible to just resync a small part of an array.\ne.g. if a drive reports that it has questionable sectors,\na \u0027repair\u0027 of just the region covering those sectors will\ncause them to be read and, if there is an error, re-written\nwith correct data.\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\n" }, { "commit": "a0da84f35b25875870270d16b6eccda4884d61a7", "tree": "3c092bcef7a8c8704054b02197156e1c803306b2", "parents": [ "0e13fe23a00ad88c737d91d94a050707c6139ce4" ], "author": { "name": "Neil Brown", "email": "neilb@notabene.brown", "time": "Sat Jun 28 08:31:22 2008 +1000" }, "committer": { "name": "Neil Brown", "email": "neilb@notabene.brown", "time": "Sat Jun 28 08:31:22 2008 +1000" }, "message": "Improve setting of \"events_cleared\" for write-intent bitmaps.\n\nWhen an array is degraded, bits in the write-intent bitmap are not\ncleared, so that if the missing device is re-added, it can be synced\nby only updated those parts of the device that have changed since\nit was removed.\n\nThe enable this a \u0027events_cleared\u0027 value is stored. It is the event\ncounter for the array the last time that any bits were cleared.\n\nSometimes - if a device disappears from an array while it is \u0027clean\u0027 -\nthe events_cleared value gets updated incorrectly (there are subtle\nordering issues between updateing events in the main metadata and the\nbitmap metadata) resulting in the missing device appearing to require\na full resync when it is re-added.\n\nWith this patch, we update events_cleared precisely when we are about\nto clear a bit in the bitmap. We record events_cleared when we clear\nthe bit internally, and copy that to the superblock which is written\nout before the bit on storage. This makes it more \"obviously correct\".\n\nWe also need to update events_cleared when the event_count is going\nbackwards (as happens on a dirty-\u003eclean transition of a non-degraded\narray).\n\nThanks to Mike Snitzer for identifying this problem and testing early\n\"fixes\".\n\nCc: \"Mike Snitzer\" \u003csnitzer@gmail.com\u003e\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\n" }, { "commit": "dfc7064500061677720fa26352963c772d3ebe6b", "tree": "a8ca495bccf98837c6762ffba54a8009c9772259", "parents": [ "90b08710e41a07d4ff0fb8940dcce3a552991a56" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri May 23 13:04:39 2008 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat May 24 09:56:10 2008 -0700" }, "message": "md: restart recovery cleanly after device failure.\n\nWhen we get any IO error during a recovery (rebuilding a spare), we abort\nthe recovery and restart it.\n\nFor RAID6 (and multi-drive RAID1) it may not be best to restart at the\nbeginning: when multiple failures can be tolerated, the recovery may be\nable to continue and re-doing all that has already been done doesn\u0027t make\nsense.\n\nWe already have the infrastructure to record where a recovery is up to\nand restart from there, but it is not being used properly.\nThis is because:\n - We sometimes abort with MD_RECOVERY_ERR rather than just MD_RECOVERY_INTR,\n which causes the recovery not be be checkpointed.\n - We remove spares and then re-added them which loses important state\n information.\n\nThe distinction between MD_RECOVERY_ERR and MD_RECOVERY_INTR really isn\u0027t\nneeded. If there is an error, the relevant drive will be marked as\nFaulty, and that is enough to ensure correct handling of the error. So we\nfirst remove MD_RECOVERY_ERR, changing some of the uses of it to\nMD_RECOVERY_INTR.\n\nThen we cause the attempt to remove a non-faulty device from an array to\nfail (unless recovery is impossible as the array is too degraded). Then\nwhen remove_and_add_spares attempts to remove the devices on which\nrecovery can continue, it will fail, they will remain in place, and\nrecovery will continue on them as desired.\n\nIssue: If we are halfway through rebuilding a spare and another drive\nfails, and a new spare is immediately available, do we want to:\n 1/ complete the current rebuild, then go back and rebuild the new spare or\n 2/ restart the rebuild from the start and rebuild both devices in\n parallel.\n\nBoth options can be argued for. The code currently takes option 2 as\n a/ this requires least code change\n b/ this results in a minimally-degraded array in minimal time.\n\nCc: \"Eivind Sarto\" \u003civan@kasenna.com\u003e\nSigned-off-by: 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": "90b08710e41a07d4ff0fb8940dcce3a552991a56", "tree": "8e45d1c6d9b4020099fd36781065bf8b8fdb76e4", "parents": [ "4f54b0e9485644a3c5fca2ae43bcbe7376825747" ], "author": { "name": "Bernd Schubert", "email": "bs@q-leap.de", "time": "Fri May 23 13:04:38 2008 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat May 24 09:56:10 2008 -0700" }, "message": "md: allow parallel resync of md-devices.\n\nIn some configurations, a raid6 resync can be limited by CPU speed\n(Calculating P and Q and moving data) rather than by device speed. In\nthese cases there is nothing to be gained byt serialising resync of arrays\nthat share a device, and doing the resync in parallel can provide benefit.\n So add a sysfs tunable to flag an array as being allowed to resync in\nparallel with other arrays that use (a different part of) the same device.\n\nSigned-off-by: Bernd Schubert \u003cbs@q-leap.de\u003e\nSigned-off-by: 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": "6bcfd601861cce45ca73ac1d714f1286b6b3f0d4", "tree": "175173d057e10dd006d6dbd033395977aff55dd9", "parents": [ "03de250a269bfa8e6a9e6ccb4a1dbce19dae8a61" ], "author": { "name": "Christoph Hellwig", "email": "hch@lst.de", "time": "Fri May 23 13:04:34 2008 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat May 24 09:56:09 2008 -0700" }, "message": "md: kill file_path wrapper\n\nKill the trivial and rather pointless file_path wrapper around d_path.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: 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": "03de250a269bfa8e6a9e6ccb4a1dbce19dae8a61", "tree": "9829b363599187fefab9ddc31be014075b474d12", "parents": [ "84255d1018c50e72c71a49f359989597d53a3f53" ], "author": { "name": "Adrian Bunk", "email": "bunk@kernel.org", "time": "Fri May 23 13:04:33 2008 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Sat May 24 09:56:09 2008 -0700" }, "message": "md: proper extern for mdp_major\n\nThis patch adds a proper extern for mdp_major in include/linux/raid/md.h\n\nSigned-off-by: Adrian Bunk \u003cbunk@kernel.org\u003e\nSigned-off-by: 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": "6bfe0b499082fd3950429017cd8ebf2a6c458aa5", "tree": "81476cf7f7ddbea135bdb93729e0bffae0e7c163", "parents": [ "11e2ede0228ee0f81ccacd15894908c3bf241f73" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Wed Apr 30 00:52:32 2008 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Wed Apr 30 08:29:33 2008 -0700" }, "message": "md: support blocking writes to an array on device failure\n\nAllows a userspace metadata handler to take action upon detecting a device\nfailure.\n\nBased on an original patch by Neil Brown.\n\nChanges:\n-added blocked_wait waitqueue to rdev\n-don\u0027t qualify Blocked with Faulty always let userspace block writes\n-added md_wait_for_blocked_rdev to wait for the block device to be clear, if\n userspace misses the notification another one is sent every 5 seconds\n-set MD_RECOVERY_NEEDED after clearing \"blocked\"\n-kill DoBlock flag, just test mddev-\u003eexternal\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: 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": "8b3e6cdc53b7f29f7026955d6cb6902a49322a15", "tree": "69d9f22a526e687fe2892d327caa3fa6ddd65cf6", "parents": [ "e46b272b6608783ed7aa7b0594871550ce20b849" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Mon Apr 28 02:15:53 2008 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@linux-foundation.org", "time": "Mon Apr 28 08:58:42 2008 -0700" }, "message": "md: introduce get_priority_stripe() to improve raid456 write performance\n\nImprove write performance by preventing the delayed_list from dumping all its\nstripes onto the handle_list in one shot. Delayed stripes are now further\ndelayed by being held on the \u0027hold_list\u0027. The \u0027hold_list\u0027 is bypassed when:\n\n * a STRIPE_IO_STARTED stripe is found at the head of \u0027handle_list\u0027\n * \u0027handle_list\u0027 is empty and i/o is being done to satisfy full stripe-width\n write requests\n * \u0027bypass_count\u0027 is less than \u0027bypass_threshold\u0027. By default the threshold\n is 1, i.e. every other stripe handled is a preread stripe provided the\n top two conditions are false.\n\nBenchmark data:\nSystem: 2x Xeon 5150, 4x SATA, mem\u003d1GB\nBaseline: 2.6.24-rc7\nConfiguration: mdadm --create /dev/md0 /dev/sd[b-e] -n 4 -l 5 --assume-clean\nTest1: dd if\u003d/dev/zero of\u003d/dev/md0 bs\u003d1024k count\u003d2048\n * patched: +33% (stripe_cache_size \u003d 256), +25% (stripe_cache_size \u003d 512)\n\nTest2: tiobench --size 2048 --numruns 5 --block 4096 --block 131072 (XFS)\n * patched: +13%\n * patched + preread_bypass_threshold \u003d 0: +37%\n\nChanges since v1:\n* reduce bypass_threshold from (chunk_size / sectors_per_chunk) to (1) and\n make it configurable. This defaults to fairness and modest performance\n gains out of the box.\nChanges since v2:\n* [neilb@suse.de]: kill STRIPE_PRIO_HI and preread_needed as they are not\n necessary, the important change was clearing STRIPE_DELAYED in\n add_stripe_bio and this has been moved out to make_request for the hang\n fix.\n* [neilb@suse.de]: simplify get_priority_stripe\n* [dan.j.williams@intel.com]: reset the bypass_count when -\u003ehold_list is\n sampled empty (+11%)\n* [dan.j.williams@intel.com]: decrement the bypass_count at the detection\n of stripes being naturally promoted off of hold_list +2%. Note, resetting\n bypass_count instead of decrementing on these events yields +4% but that is\n probably too aggressive.\nChanges since v3:\n* cosmetic fixups\n\nTested-by: James W. Laferriere \u003cbabydr@baby-dragons.com\u003e\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nSigned-off-by: 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": "5a6483feb0c5193519625d0ea8c4254364d423cc", "tree": "2235220e522882ac5872937fa43d3d1b188c1f4e", "parents": [ "cb688371e27880d86c42323826846d1cd7caad8f" ], "author": { "name": "Matthew Wilcox", "email": "matthew@wil.cx", "time": "Tue Feb 26 10:00:17 2008 -0500" }, "committer": { "name": "Matthew Wilcox", "email": "willy@linux.intel.com", "time": "Fri Apr 18 22:16:54 2008 -0400" }, "message": "include: Remove unnecessary inclusions of asm/semaphore.h\n\nNone of these files use any of the functionality promised by\nasm/semaphore.h. It\u0027s possible that they (or some user of them) rely\non it dragging in some unrelated header file, but I can\u0027t build all\nthese files, so we\u0027ll have to fix any build failures as they come up.\n\nSigned-off-by: Matthew Wilcox \u003cwilly@linux.intel.com\u003e\n" }, { "commit": "d0fae18f1b53a1d39135a968792be034bdf7ff26", "tree": "3448dab652696848df47dcafb7772220b9e58e4f", "parents": [ "a1801f858e57f87a7f79914346921cc729632295" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 04 14:29:31 2008 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Tue Mar 04 16:35:18 2008 -0800" }, "message": "md: clean up irregularity with raid autodetect\n\nWhen a raid1 array is stopped, all components currently get added to the list\nfor auto-detection. However we should really only add components that were\nfound by autodetection in the first place. So add a flag to record that\ninformation, and use it.\n\nSigned-off-by: 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": "8311c29d40235062a843f4a8e8a70a44af6fe4c9", "tree": "c869143fae8f135646300d1bac6639af5bb30dd7", "parents": [ "a35e63efa1fb18c6f20f38e3ddf3f8ffbcf0f6e7" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Mar 04 14:29:30 2008 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Tue Mar 04 16:35:17 2008 -0800" }, "message": "md: reduce CPU wastage on idle md array with a write-intent bitmap\n\nOn an md array with a write-intent bitmap, a thread wakes up every few seconds\nand scans the bitmap looking for work to do. If the array is idle, there will\nbe no work to do, but a lot of scanning is done to discover this.\n\nSo cache the fact that the bitmap is completely clean, and avoid scanning the\nwhole bitmap when the cache is known to be clean.\n\nSigned-off-by: 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": "73c34431c7119d0bc7d3436abfad75fe47b2c51f", "tree": "c91210130d1115354f011e55c98db9361d4416f8", "parents": [ "d089c6af10c2be5988f03667d6d22fe6085fbe5e" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Feb 06 01:39:59 2008 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Wed Feb 06 10:41:19 2008 -0800" }, "message": "md: change ITERATE_RDEV_GENERIC to rdev_for_each_list, and remove ITERATE_RDEV_PENDING.\n\nFinish ITERATE_ to for_each conversion.\n\nSigned-off-by: 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": "d089c6af10c2be5988f03667d6d22fe6085fbe5e", "tree": "815eb0596bd7c908f30c268da6b5c5eff0e0bc21", "parents": [ "29ac4aa3fc68a86279aca50f20df4d614de2e204" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Feb 06 01:39:59 2008 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Wed Feb 06 10:41:19 2008 -0800" }, "message": "md: change ITERATE_RDEV to rdev_for_each\n\nAs this is more in line with common practice in the kernel. Also swap the\nargs around to be more like list_for_each.\n\nSigned-off-by: 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": "c5d79adba7ced41d7ac097c2ab74759d10522dd5", "tree": "ab5a45046244602f2a27be0b34fb26155a3c8dee", "parents": [ "1ec4a9398dc05061b6258061676fede733458893" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Feb 06 01:39:54 2008 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Wed Feb 06 10:41:18 2008 -0800" }, "message": "md: allow devices to be shared between md arrays\n\nCurrently, a given device is \"claimed\" by a particular array so that it cannot\nbe used by other arrays.\n\nThis is not ideal for DDF and other metadata schemes which have their own\npartitioning concept.\n\nSo for externally managed metadata, just claim the device for md in general,\nrequire that \"offset\" and \"size\" are set properly for each device, and make\nsure that if a device is included in different arrays then the active sections\ndo not overlap.\n\nThis involves adding another flag to the rdev which makes it awkward to set\n\"-\u003eflags \u003d 0\" to clear certain flags. So now clear flags explicitly by name\nwhen we want to clear things.\n\nSigned-off-by: 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": "c620727779f7cc8ea96efb71f0651a26349e59c1", "tree": "777abdad9c9ef10cb4df5c0efc736e6c64851ed8", "parents": [ "c303da6d713b87b7b3f999f5acce8ecc76ff1adb" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Feb 06 01:39:52 2008 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Wed Feb 06 10:41:18 2008 -0800" }, "message": "md: allow a maximum extent to be set for resyncing\n\nThis allows userspace to control resync/reshape progress and synchronise it\nwith other activities, such as shared access in a SAN, or backing up critical\nsections during a tricky reshape.\n\nWriting a number of sectors (which must be a multiple of the chunk size if\nsuch is meaningful) causes a resync to pause when it gets to that point.\n\nSigned-off-by: 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": "e691063a61f7f72a7d2882eb744b07a520cde23b", "tree": "4f5ceb7ed310a7d1bb076271926260723ac5ee6d", "parents": [ "b47490c9bc73d0b34e4c194db40de183e592e446" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Feb 06 01:39:51 2008 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Wed Feb 06 10:41:18 2008 -0800" }, "message": "md: support \u0027external\u0027 metadata for md arrays\n\n- Add a state flag \u0027external\u0027 to indicate that the metadata is managed\n externally (by user-space) so important changes need to be\n left of user-space to handle.\n Alternates are non-persistant (\u0027none\u0027) where there is no stable metadata -\n after the array is stopped there is no record of it\u0027s status - and\n internal which can be version 0.90 or version 1.x\n These are selected by writing to the \u0027metadata\u0027 attribute.\n\n- move the updating of superblocks (sync_sbs) to after we have checked if\n there are any superblocks or not.\n\n- New array state \u0027write_pending\u0027. This means that the metadata records\n the array as \u0027clean\u0027, but a write has been requested, so the metadata has\n to be updated to record a \u0027dirty\u0027 array before the write can continue.\n This change is reported to md by writing \u0027active\u0027 to the array_state\n attribute.\n\n- tidy up marking of sb_dirty:\n - don\u0027t set sb_dirty when resync finishes as md_check_recovery\n calls md_update_sb when the sync thread finishes anyway.\n - Don\u0027t set sb_dirty in multipath_run as the array might not be dirty.\n - don\u0027t mark superblock dirty when switching to \u0027clean\u0027 if there\n is no internal superblock (if external, userspace can choose to\n update the superblock whenever it chooses to).\n\nSigned-off-by: 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": "b47490c9bc73d0b34e4c194db40de183e592e446", "tree": "8334581aff7aa0b199df04c6f9d707c1902ad14f", "parents": [ "66c811e99322767bad5db4368de93aac604f02a2" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Feb 06 01:39:50 2008 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Wed Feb 06 10:41:18 2008 -0800" }, "message": "md: Update md bitmap during resync.\n\nCurrently an md array with a write-intent bitmap does not updated that bitmap\nto reflect successful partial resync. Rather the entire bitmap is updated\nwhen the resync completes.\n\nThis is because there is no guarentee that resync requests will complete in\norder, and tracking each request individually is unnecessarily burdensome.\n\nHowever there is value in regularly updating the bitmap, so add code to\nperiodically pause while all pending sync requests complete, then update the\nbitmap. Doing this only every few seconds (the same as the bitmap update\ntime) does not notciably affect resync performance.\n\n[snitzer@gmail.com: export bitmap_cond_end_sync]\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nCc: \"Mike Snitzer\" \u003csnitzer@gmail.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "5ebf2c1260705a2ce51ad19af33059f08211579d", "tree": "a710660aaa499f17239f62328e75cb7159da4d3b", "parents": [ "4d936ec1fdc1541cd6d59d21ddb8b9386e2fcc4c" ], "author": { "name": "Adrian Bunk", "email": "bunk@kernel.org", "time": "Tue Oct 16 23:30:52 2007 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Wed Oct 17 08:43:03 2007 -0700" }, "message": "bitmap.h: remove dead artifacts\n\nbitmap_active() no longer exists and BITMAP_ACTIVE is no longer used.\n\nSigned-off-by: Adrian Bunk \u003cbunk@kernel.org\u003e\nCc: Neil Brown \u003cneilb@suse.de\u003e\nCc: \"J. Bruce Fields\" \u003cbfields@fieldses.org\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "165125e1e480f9510a5ffcfbfee4e3ee38c05f23", "tree": "8009c8a5ff09e26dc2418d42f66ecafb055c52a2", "parents": [ "f695baf2df9e0413d3521661070103711545207a" ], "author": { "name": "Jens Axboe", "email": "jens.axboe@oracle.com", "time": "Tue Jul 24 09:28:11 2007 +0200" }, "committer": { "name": "Jens Axboe", "email": "jens.axboe@oracle.com", "time": "Tue Jul 24 09:28:11 2007 +0200" }, "message": "[BLOCK] Get rid of request_queue_t typedef\n\nSome of the code has been gradually transitioned to using the proper\nstruct request_queue, but there\u0027s lots left. So do a full sweet of\nthe kernel and get rid of this typedef and replace its uses with\nthe proper type.\n\nSigned-off-by: Jens Axboe \u003cjens.axboe@oracle.com\u003e\n" }, { "commit": "4ad1366376bfef32ec0ffa12d1faa483d6f330bd", "tree": "87a9c864ec5ebd446f6c99f3298bc7638efa8f1e", "parents": [ "f0d76d70bc77b9b11256a3a23e98e80878be1578" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Jul 17 04:06:13 2007 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Tue Jul 17 10:23:15 2007 -0700" }, "message": "md: change bitmap_unplug and others to void functions\n\nbitmap_unplug only ever returns 0, so it may as well be void. Two callers try\nto print a message if it returns non-zero, but that message is already printed\nby bitmap_file_kick.\n\nwrite_page returns an error which is not consistently checked. It always\ncauses BITMAP_WRITE_ERROR to be set on an error, and that can more\nconveniently be checked.\n\nWhen the return of write_page is checked, an error causes bitmap_file_kick to\nbe called - so move that call into write_page - and protect against recursive\ncalls into bitmap_file_kick.\n\nbitmap_update_sb returns an error that is never checked.\n\nSo make these \u0027void\u0027 and be consistent about checking the bit.\n\nSigned-off-by: 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": "713f6ab18b0e7d39f14401362bfe8015b1aedde1", "tree": "fc6ef865d09de1ec816ed96860ffc27dd48d837b", "parents": [ "df968c4e8d809deb2602fb0e8db758f26a4006b9" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Jul 17 04:06:12 2007 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Tue Jul 17 10:23:15 2007 -0700" }, "message": "md: improve the is_mddev_idle test fix\n\nDon\u0027t use \u0027unsigned\u0027 variable to track sync vs non-sync IO, as the only thing\nwe want to do with them is a signed comparison, and fix up the comment which\nhad become quite wrong.\n\nSigned-off-by: 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": "b5e98d65d34a1c11a2135ea8a9b2619dbc7216c8", "tree": "bf88aad375bb0cbf6c346ec912c06c2607850b21", "parents": [ "e89f89629b5de76e504d1be75c82c4a6b2419583" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Tue Jan 02 13:52:31 2007 -0700" }, "committer": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Fri Jul 13 08:06:17 2007 -0700" }, "message": "md: handle_stripe5 - add request/completion logic for async read ops\n\nWhen a read bio is attached to the stripe and the corresponding block is\nmarked R5_UPTODATE, then a read (biofill) operation is scheduled to copy\nthe data from the stripe cache to the bio buffer. handle_stripe flags the\nblocks to be operated on with the R5_Wantfill flag. If new read requests\narrive while raid5_run_ops is running they will not be handled until\nhandle_stripe is scheduled to run again.\n\nChangelog:\n* cleanup to_read and to_fill accounting\n* do not fail reads that have reached the cache\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nAcked-By: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "f38e12199a94ca458e4f03c5a2c984fb80adadc5", "tree": "706f54c46d4a4c839dd43c1403854dde860c6be5", "parents": [ "e33129d84130459dbb764a1a52a4bfceab3da978" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Tue Jan 02 13:52:30 2007 -0700" }, "committer": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Fri Jul 13 08:06:17 2007 -0700" }, "message": "md: handle_stripe5 - add request/completion logic for async compute ops\n\nhandle_stripe will compute a block when a backing disk has failed, or when\nit determines it can save a disk read by computing the block from all the\nother up-to-date blocks.\n\nPreviously a block would be computed under the lock and subsequent logic in\nhandle_stripe could use the newly up-to-date block. With the raid5_run_ops\nimplementation the compute operation is carried out a later time outside\nthe lock. To preserve the old functionality we take advantage of the\ndependency chain feature of async_tx to flag the block as R5_Wantcompute\nand then let other parts of handle_stripe operate on the block as if it\nwere up-to-date. raid5_run_ops guarantees that the block will be ready\nbefore it is used in another operation.\n\nHowever, this only works in cases where the compute and the dependent\noperation are scheduled at the same time. If a previous call to\nhandle_stripe sets the R5_Wantcompute flag there is no facility to pass the\nasync_tx dependency chain across successive calls to raid5_run_ops. The\nreq_compute variable protects against this case.\n\nChangelog:\n* remove the req_compute BUG_ON\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nAcked-By: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "91c00924846a0034020451c280c76baa4299f9dc", "tree": "7124ed6706937b793a10c37a861c5fc0f2e5b348", "parents": [ "45b4233caac05da0118b608a9fc2a40a9fc580cd" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Tue Jan 02 13:52:30 2007 -0700" }, "committer": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Fri Jul 13 08:06:15 2007 -0700" }, "message": "md: raid5_run_ops - run stripe operations outside sh-\u003elock\n\nWhen the raid acceleration work was proposed, Neil laid out the following\nattack plan:\n\n1/ move the xor and copy operations outside spin_lock(\u0026sh-\u003elock)\n2/ find/implement an asynchronous offload api\n\nThe raid5_run_ops routine uses the asynchronous offload api (async_tx) and\nthe stripe_operations member of a stripe_head to carry out xor+copy\noperations asynchronously, outside the lock.\n\nTo perform operations outside the lock a new set of state flags is needed\nto track new requests, in-flight requests, and completed requests. In this\nnew model handle_stripe is tasked with scanning the stripe_head for work,\nupdating the stripe_operations structure, and finally dropping the lock and\ncalling raid5_run_ops for processing. The following flags outline the\nrequests that handle_stripe can make of raid5_run_ops:\n\nSTRIPE_OP_BIOFILL\n - copy data into request buffers to satisfy a read request\nSTRIPE_OP_COMPUTE_BLK\n - generate a missing block in the cache from the other blocks\nSTRIPE_OP_PREXOR\n - subtract existing data as part of the read-modify-write process\nSTRIPE_OP_BIODRAIN\n - copy data out of request buffers to satisfy a write request\nSTRIPE_OP_POSTXOR\n - recalculate parity for new data that has entered the cache\nSTRIPE_OP_CHECK\n - verify that the parity is correct\nSTRIPE_OP_IO\n - submit i/o to the member disks (note this was already performed outside\n the stripe lock, but it made sense to add it as an operation type\n\nThe flow is:\n1/ handle_stripe sets STRIPE_OP_* in sh-\u003eops.pending\n2/ raid5_run_ops reads sh-\u003eops.pending, sets sh-\u003eops.ack, and submits the\n operation to the async_tx api\n3/ async_tx triggers the completion callback routine to set\n sh-\u003eops.complete and release the stripe\n4/ handle_stripe runs again to finish the operation and optionally submit\n new operations that were previously blocked\n\nNote this patch just defines raid5_run_ops, subsequent commits (one per\nmajor operation type) modify handle_stripe to take advantage of this\nroutine.\n\nChangelog:\n* removed ops_complete_biodrain in favor of ops_complete_postxor and\n ops_complete_write.\n* removed the raid5_run_ops workqueue\n* call bi_end_io for reads in ops_complete_biofill, saves a call to\n handle_stripe\n* explicitly handle the 2-disk raid5 case (xor becomes memcpy), Neil Brown\n* fix race between async engines and bi_end_io call for reads, Neil Brown\n* remove unnecessary spin_lock from ops_complete_biofill\n* remove test_and_set/test_and_clear BUG_ONs, Neil Brown\n* remove explicit interrupt handling for channel switching, this feature\n was absorbed (i.e. it is now implicit) by the async_tx api\n* use return_io in ops_complete_biofill\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nAcked-By: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "a445685647e825c713175d180ffc8dd54d90589b", "tree": "d2db5674e51d33162e1e5993b6e6680ec534e2df", "parents": [ "9bc89cd82d6f88fb0ca39b30445c329a430fd66b" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Mon Jul 09 11:56:43 2007 -0700" }, "committer": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Fri Jul 13 08:06:15 2007 -0700" }, "message": "raid5: refactor handle_stripe5 and handle_stripe6 (v3)\n\nhandle_stripe5 and handle_stripe6 have very deep logic paths handling the\nvarious states of a stripe_head. By introducing the \u0027stripe_head_state\u0027\nand \u0027r6_state\u0027 objects, large portions of the logic can be moved to\nsub-routines.\n\n\u0027struct stripe_head_state\u0027 consumes all of the automatic variables that previously\nstood alone in handle_stripe5,6. \u0027struct r6_state\u0027 contains the handle_stripe6\nspecific variables like p_failed and q_failed.\n\nOne of the nice side effects of the \u0027stripe_head_state\u0027 change is that it\nallows for further reductions in code duplication between raid5 and raid6.\nThe following new routines are shared between raid5 and raid6:\n\n\thandle_completed_write_requests\n\thandle_requests_to_failed_array\n\thandle_stripe_expansion\n\nChanges:\n* v2: fixed \u0027conf-\u003eraid_disk-1\u0027 for the raid6 \u0027handle_stripe_expansion\u0027 path\n* v3: removed the unused \u0027dirty\u0027 field from struct stripe_head_state\n* v3: coalesced open coded bi_end_io routines into return_io()\n\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nAcked-By: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "9bc89cd82d6f88fb0ca39b30445c329a430fd66b", "tree": "7bd0e856abd359f84edea1bacfd1dd32edd93fbb", "parents": [ "685784aaf3cd0e3ff5e36c7ecf6f441cdbf57f73" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Tue Jan 02 11:10:44 2007 -0700" }, "committer": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Fri Jul 13 08:06:14 2007 -0700" }, "message": "async_tx: add the async_tx api\n\nThe async_tx api provides methods for describing a chain of asynchronous\nbulk memory transfers/transforms with support for inter-transactional\ndependencies. It is implemented as a dmaengine client that smooths over\nthe details of different hardware offload engine implementations. Code\nthat is written to the api can optimize for asynchronous operation and the\napi will fit the chain of operations to the available offload resources. \n \n\tI imagine that any piece of ADMA hardware would register with the\n\t\u0027async_*\u0027 subsystem, and a call to async_X would be routed as\n\tappropriate, or be run in-line. - Neil Brown\n\nasync_tx exploits the capabilities of struct dma_async_tx_descriptor to\nprovide an api of the following general format:\n\nstruct dma_async_tx_descriptor *\nasync_\u003coperation\u003e(..., struct dma_async_tx_descriptor *depend_tx,\n\t\t\tdma_async_tx_callback cb_fn, void *cb_param)\n{\n\tstruct dma_chan *chan \u003d async_tx_find_channel(depend_tx, \u003coperation\u003e);\n\tstruct dma_device *device \u003d chan ? chan-\u003edevice : NULL;\n\tint int_en \u003d cb_fn ? 1 : 0;\n\tstruct dma_async_tx_descriptor *tx \u003d device ?\n\t\tdevice-\u003edevice_prep_dma_\u003coperation\u003e(chan, len, int_en) : NULL;\n\n\tif (tx) { /* run \u003coperation\u003e asynchronously */\n\t\t...\n\t\ttx-\u003etx_set_dest(addr, tx, index);\n\t\t...\n\t\ttx-\u003etx_set_src(addr, tx, index);\n\t\t...\n\t\tasync_tx_submit(chan, tx, flags, depend_tx, cb_fn, cb_param);\n\t} else { /* run \u003coperation\u003e synchronously */\n\t\t...\n\t\t\u003coperation\u003e\n\t\t...\n\t\tasync_tx_sync_epilog(flags, depend_tx, cb_fn, cb_param);\n\t}\n\n\treturn tx;\n}\n\nasync_tx_find_channel() returns a capable channel from its pool. The\nchannel pool is organized as a per-cpu array of channel pointers. The\nasync_tx_rebalance() routine is tasked with managing these arrays. In the\nuniprocessor case async_tx_rebalance() tries to spread responsibility\nevenly over channels of similar capabilities. For example if there are two\ncopy+xor channels, one will handle copy operations and the other will\nhandle xor. In the SMP case async_tx_rebalance() attempts to spread the\noperations evenly over the cpus, e.g. cpu0 gets copy channel0 and xor\nchannel0 while cpu1 gets copy channel 1 and xor channel 1. When a\ndependency is specified async_tx_find_channel defaults to keeping the\noperation on the same channel. A xor-\u003ecopy-\u003exor chain will stay on one\nchannel if it supports both operation types, otherwise the transaction will\ntransition between a copy and a xor resource.\n\nCurrently the raid5 implementation in the MD raid456 driver has been\nconverted to the async_tx api. A driver for the offload engines on the\nIntel Xscale series of I/O processors, iop-adma, is provided in a later\ncommit. With the iop-adma driver and async_tx, raid456 is able to offload\ncopy, xor, and xor-zero-sum operations to hardware engines.\n \nOn iop342 tiobench showed higher throughput for sequential writes (20 - 30%\nimprovement) and sequential reads to a degraded array (40 - 55%\nimprovement). For the other cases performance was roughly equal, +/- a few\npercentage points. On a x86-smp platform the performance of the async_tx\nimplementation (in synchronous mode) was also +/- a few percentage points\nof the original implementation. According to \u0027top\u0027 on iop342 CPU\nutilization drops from ~50% to ~15% during a \u0027resync\u0027 while the speed\naccording to /proc/mdstat doubles from ~25 MB/s to ~50 MB/s.\n \nThe tiobench command line used for testing was: tiobench --size 2048\n--block 4096 --block 131072 --dir /mnt/raid --numruns 5\n* iop342 had 1GB of memory available\n\nDetails:\n* if CONFIG_DMA_ENGINE\u003dn the asynchronous path is compiled away by making\n async_tx_find_channel a static inline routine that always returns NULL\n* when a callback is specified for a given transaction an interrupt will\n fire at operation completion time and the callback will occur in a\n tasklet. if the the channel does not support interrupts then a live\n polling wait will be performed\n* the api is written as a dmaengine client that requests all available\n channels\n* In support of dependencies the api implicitly schedules channel-switch\n interrupts. The interrupt triggers the cleanup tasklet which causes\n pending operations to be scheduled on the next channel\n* Xor engines treat an xor destination address differently than a software\n xor routine. To the software routine the destination address is an implied\n source, whereas engines treat it as a write-only destination. This patch\n modifies the xor_blocks routine to take a an explicit destination address\n to mirror the hardware.\n\nChangelog:\n* fixed a leftover debug print\n* don\u0027t allow callbacks in async_interrupt_cond\n* fixed xor_block changes\n* fixed usage of ASYNC_TX_XOR_DROP_DEST\n* drop dma mapping methods, suggested by Chris Leech\n* printk warning fixups from Andrew Morton\n* don\u0027t use inline in C files, Adrian Bunk\n* select the API when MD is enabled\n* BUG_ON xor source counts \u003c\u003d 1\n* implicitly handle hardware concerns like channel switching and\n interrupts, Neil Brown\n* remove the per operation type list, and distribute operation capabilities\n evenly amongst the available channels\n* simplify async_tx_find_channel to optimize the fast path\n* introduce the channel_table_initialized flag to prevent early calls to\n the api\n* reorganize the code to mimic crypto\n* include mm.h as not all archs include it in dma-mapping.h\n* make the Kconfig options non-user visible, Adrian Bunk\n* move async_tx under crypto since it is meant as \u0027core\u0027 functionality, and\n the two may share algorithms in the future\n* move large inline functions into c files\n* checkpatch.pl fixes\n* gpl v2 only correction\n\nCc: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\nAcked-By: NeilBrown \u003cneilb@suse.de\u003e\n" }, { "commit": "685784aaf3cd0e3ff5e36c7ecf6f441cdbf57f73", "tree": "10f99829f7d877b87614fe69be77e363c026a8d7", "parents": [ "d379b01e9087a582d58f4b678208a4f8d8376fe7" ], "author": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Mon Jul 09 11:56:42 2007 -0700" }, "committer": { "name": "Dan Williams", "email": "dan.j.williams@intel.com", "time": "Fri Jul 13 08:06:14 2007 -0700" }, "message": "xor: make \u0027xor_blocks\u0027 a library routine for use with async_tx\n\nThe async_tx api tries to use a dma engine for an operation, but will fall\nback to an optimized software routine otherwise. Xor support is\nimplemented using the raid5 xor routines. For organizational purposes this\nroutine is moved to a common area.\n\nThe following fixes are also made:\n* rename xor_block \u003d\u003e xor_blocks, suggested by Adrian Bunk\n* ensure that xor.o initializes before md.o in the built-in case\n* checkpatch.pl fixes\n* mark calibrate_xor_blocks __init, Adrian Bunk\n\nCc: Adrian Bunk \u003cbunk@stusta.de\u003e\nCc: NeilBrown \u003cneilb@suse.de\u003e\nCc: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\nSigned-off-by: Dan Williams \u003cdan.j.williams@intel.com\u003e\n" }, { "commit": "ab6085c795a71b6a21afe7469d30a365338add7a", "tree": "d9d901ea1c3401906553ef9e684a1094a1b3083a", "parents": [ "787f17feb204ed1c6331892fb8124b80dc9fe288" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed May 23 13:58:10 2007 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Wed May 23 20:14:14 2007 -0700" }, "message": "md: don\u0027t write more than is required of the last page of a bitmap\n\nIt is possible that real data or metadata follows the bitmap without full page\nalignment.\n\nSo limit the last write to be only the required number of bytes, rounded up to\nthe hard sector size of the device.\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nCc: \u003cstable@kernel.org\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "44ce6294d07555c3d313757105fd44b78208407f", "tree": "29659bee16a4d7111124c6f41289bc9c11669e70", "parents": [ "497f050c42e46a4b1f6a9bcd8827fa5d97fe1feb" ], "author": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Wed May 09 18:51:36 2007 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Wed May 09 18:51:36 2007 -0700" }, "message": "Revert \"md: improve partition detection in md array\"\n\nThis reverts commit 5b479c91da90eef605f851508744bfe8269591a0.\n\nQuoth Neil Brown:\n\n \"It causes an oops when auto-detecting raid arrays, and it doesn\u0027t\n seem easy to fix.\n\n The array may not be \u0027open\u0027 when do_md_run is called, so\n bdev-\u003ebd_disk might be NULL, so bd_set_size can oops.\n\n This whole approach of opening an md device before it has been\n assembled just seems to get more and more painful. I think I\u0027m going\n to have to come up with something clever to provide both backward\n comparability with usage expectation, and sane integration into the\n rest of the kernel.\"\n\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "5b479c91da90eef605f851508744bfe8269591a0", "tree": "d7c2844926d96d794d66b974b300eba2d047465e", "parents": [ "08a02ecd28bad35a47357e611044dcbeab06e3d7" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed May 09 02:35:39 2007 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Wed May 09 12:30:57 2007 -0700" }, "message": "md: improve partition detection in md array\n\nmd currently uses -\u003emedia_changed to make sure rescan_partitions\nis call on md array after they are assembled.\n\nHowever that doesn\u0027t happen until the array is opened, which is later\nthan some people would like.\n\nSo use blkdev_ioctl to do the rescan immediately that the\narray has been assembled.\n\nThis means we can remove all the -\u003echange infrastructure as it was only used\nto trigger a partition rescan.\n\nSigned-off-by: 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": "5792a2856a63cdc568e08a7d6f9b2413d9217b3e", "tree": "042a09fbfdf75dac5efa3bf61c7d6c6dd4c6ba7f", "parents": [ "456a09dce9ca9b0013cabcda918aee851a04471d" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Wed Apr 04 19:08:18 2007 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Wed Apr 04 21:12:47 2007 -0700" }, "message": "[PATCH] md: avoid a deadlock when removing a device from an md array via sysfs\n\nA device can be removed from an md array via e.g.\n echo remove \u003e /sys/block/md3/md/dev-sde/state\n\nThis will try to remove the \u0027dev-sde\u0027 subtree which will deadlock\nsince\n commit e7b0d26a86943370c04d6833c6edba2a72a6e240\n\nWith this patch we run the kobject_del via schedule_work so as to\navoid the deadlock.\n\nCc: Alan Stern \u003cstern@rowland.harvard.edu\u003e\nSigned-off-by: 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": "da6e1a32fb8d7539a27f699c8671f64d7fefd0cc", "tree": "8faa7713ad1333b30d8ba668627251dbc1e0b4ad", "parents": [ "aaf68cfbf2241d24d46583423f6bff5c47e088b3" ], "author": { "name": "Neil Brown", "email": "neilb@suse.de", "time": "Thu Feb 08 14:20:37 2007 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Fri Feb 09 09:25:47 2007 -0800" }, "message": "[PATCH] md: avoid possible BUG_ON in md bitmap handling\n\nmd/bitmap tracks how many active write requests are pending on blocks\nassociated with each bit in the bitmap, so that it knows when it can clear\nthe bit (when count hits zero).\n\nThe counter has 14 bits of space, so if there are ever more than 16383, we\ncannot cope.\n\nCurrently the code just calles BUG_ON as \"all\" drivers have request queue\nlimits much smaller than this.\n\nHowever is seems that some don\u0027t. Apparently some multipath configurations\ncan allow more than 16383 concurrent write requests.\n\nSo, in this unlikely situation, instead of calling BUG_ON we now wait\nfor the count to drop down a bit. This requires a new wait_queue_head,\nsome waiting code, and a wakeup call.\n\nTested by limiting the counter to 20 instead of 16383 (writes go a lot slower\nin that case...).\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nCc: \u003cstable@kernel.org\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "2a2275d630b982e5f90206f9bc497f6695a3ec5d", "tree": "88cddee709b2107b74e5424810d4ffb6e3772382", "parents": [ "a0ad13ef643a5829d63c456ab6143bbda60b44a9" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Fri Jan 26 00:57:11 2007 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.linux-foundation.org", "time": "Fri Jan 26 13:51:00 2007 -0800" }, "message": "[PATCH] md: fix potential memalloc deadlock in md\n\nIf a GFP_KERNEL allocation is attempted in md while the mddev_lock is held,\nit is possible for a deadlock to eventuate.\n\nThis happens if the array was marked \u0027clean\u0027, and the memalloc triggers a\nwrite-out to the md device.\n\nFor the writeout to succeed, the array must be marked \u0027dirty\u0027, and that\nrequires getting the mddev_lock.\n\nSo, before attempting a GFP_KERNEL allocation while holding the lock, make\nsure the array is marked \u0027dirty\u0027 (unless it is currently read-only).\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n" }, { "commit": "46031f9a38a9773021f1872abc713d62467ac22e", "tree": "fe91f661fe0aad5f149447797c5d31544453ca38", "parents": [ "f679623f50545bc0577caf2d0f8675b61162f059" ], "author": { "name": "Raz Ben-Jehuda(caro)", "email": "raziebe@gmail.com", "time": "Sun Dec 10 02:20:47 2006 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.osdl.org", "time": "Sun Dec 10 09:57:20 2006 -0800" }, "message": "[PATCH] md: allow reads that have bypassed the cache to be retried on failure\n\nIf a bypass-the-cache read fails, we simply try again through the cache. If\nit fails again it will trigger normal recovery precedures.\n\nupdate 1:\n\nFrom: NeilBrown \u003cneilb@suse.de\u003e\n\n1/\n chunk_aligned_read and retry_aligned_read assume that\n data_disks \u003d\u003d raid_disks - 1\n which is not true for raid6.\n So when an aligned read request bypasses the cache, we can get the wrong data.\n\n2/ The cloned bio is being used-after-free in raid5_align_endio\n (to test BIO_UPTODATE).\n\n3/ We forgot to add rdev-\u003edata_offset when submitting\n a bio for aligned-read\n\n4/ clone_bio calls blk_recount_segments and then we change bi_bdev,\n so we need to invalidate the segment counts.\n\n5/ We don\u0027t de-reference the rdev when the read completes.\n This means we need to record the rdev to so it is still\n available in the end_io routine. Fortunately\n bi_next in the original bio is unused at this point so\n we can stuff it in there.\n\n6/ We leak a cloned bio if the target rdev is not usable.\n\nFrom: NeilBrown \u003cneilb@suse.de\u003e\n\nupdate 2:\n\n1/ When aligned requests fail (read error) they need to be retried\n via the normal method (stripe cache). As we cannot be sure that\n we can process a single read in one go (we may not be able to\n allocate all the stripes needed) we store a bio-being-retried\n and a list of bioes-that-still-need-to-be-retried.\n When find a bio that needs to be retried, we should add it to\n the list, not to single-bio...\n\n2/ We were never incrementing \u0027scnt\u0027 when resubmitting failed\n aligned requests.\n\n[akpm@osdl.org: build fix]\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "e18b890bb0881bbab6f4f1a6cd20d9c60d66b003", "tree": "4828be07e1c24781c264b42c5a75bcd968223c3f", "parents": [ "441e143e95f5aa1e04026cb0aa71c801ba53982f" ], "author": { "name": "Christoph Lameter", "email": "clameter@sgi.com", "time": "Wed Dec 06 20:33:20 2006 -0800" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@woody.osdl.org", "time": "Thu Dec 07 08:39:25 2006 -0800" }, "message": "[PATCH] slab: remove kmem_cache_t\n\nReplace all uses of kmem_cache_t with struct kmem_cache.\n\nThe patch was generated using the following script:\n\n\t#!/bin/sh\n\t#\n\t# Replace one string by another in all the kernel sources.\n\t#\n\n\tset -e\n\n\tfor file in `find * -name \"*.c\" -o -name \"*.h\"|xargs grep -l $1`; do\n\t\tquilt add $file\n\t\tsed -e \"1,\\$s/$1/$2/g\" $file \u003e/tmp/$$\n\t\tmv /tmp/$$ $file\n\t\tquilt refresh\n\tdone\n\nThe script was run like this\n\n\tsh replace kmem_cache_t \"struct kmem_cache\"\n\nSigned-off-by: Christoph Lameter \u003cclameter@sgi.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "4f2e639af4bd5e152fc79256e333643d3dd6c10f", "tree": "1adf32d929c552d7e4b24475baa45c6108436f79", "parents": [ "1c05b4bc22cd640d3a534bd2851a8413d5df3709" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Sat Oct 21 10:24:09 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Sat Oct 21 13:35:05 2006 -0700" }, "message": "[PATCH] md: endian annotations for the bitmap superblock\n\nAnd a couple of bug fixes found by sparse.\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "1c05b4bc22cd640d3a534bd2851a8413d5df3709", "tree": "dceceabea9bdb92213e2a2d318cdd1b152832cbd", "parents": [ "da3ed32fe568148ede256975d40825ffcdac767b" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Sat Oct 21 10:24:08 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Sat Oct 21 13:35:05 2006 -0700" }, "message": "[PATCH] md: endian annotation for v1 superblock access\n\nIncludes a couple of bugfixes found by sparse.\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "e8703fe1f5cdcff686f7eb0a46487b5a04a9324a", "tree": "3b52bfa6ee57d59e059fd0e8d8504dbd3ee073b4", "parents": [ "d33a56d3639eba077489c937943a32ef6237b1b8" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Oct 03 01:15:59 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Tue Oct 03 08:04:18 2006 -0700" }, "message": "[PATCH] md: remove MAX_MD_DEVS which is an arbitrary limit\n\nOnce upon a time we needed to fixed limit to the number of md devices,\nprobably because we preallocated some array. This need no longer exists, but\nwe still have an arbitrary limit.\n\nSo remove MAX_MD_DEVS and allow as many devices as we can fit into the \u0027minor\u0027\npart of a device number.\n\nAlso remove some useless noise at init time (which reports MAX_MD_DEVS) and\nremove MD_THREAD_NAME_MAX which hasn\u0027t been used for a while.\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "11ce99e625fe2718ad2682bfdd99070b337e6252", "tree": "48e40104a058f27e9cd717c42edcf6738fef2372", "parents": [ "867868fb557eb2a2120b80779468fa372584ddb0" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Oct 03 01:15:52 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Tue Oct 03 08:04:17 2006 -0700" }, "message": "[PATCH] md: Remove working_disks from raid1 state data\n\nIt is equivalent to conf-\u003eraid_disks - conf-\u003emddev-\u003edegraded.\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "9b1d1dac181d8c1b9492e05cee660a985d035a06", "tree": "af12b1eaac4e0f7f3528ec26a223faeabed35845", "parents": [ "76186dd8b73d2b7b9b4c8629b89c845e97009801" ], "author": { "name": "Paul Clements", "email": "paul.clements@steeleye.com", "time": "Tue Oct 03 01:15:49 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Tue Oct 03 08:04:17 2006 -0700" }, "message": "[PATCH] md: new sysfs interface for setting bits in the write-intent-bitmap\n\nAdd a new sysfs interface that allows the bitmap of an array to be dirtied.\nThe interface is write-only, and is used as follows:\n\necho \"1000\" \u003e /sys/block/md2/md/bitmap\n\n(dirty the bit for chunk 1000 [offset 0] in the in-memory and on-disk\nbitmaps of array md2)\n\necho \"1000-2000\" \u003e /sys/block/md1/md/bitmap\n\n(dirty the bits for chunks 1000-2000 in md1\u0027s bitmap)\n\nThis is useful, for example, in cluster environments where you may need to\ncombine two disjoint bitmaps into one (following a server failure, after a\nsecondary server has taken over the array). By combining the bitmaps on\nthe two servers, a full resync can be avoided (This was discussed on the\nlist back on March 18, 2005, \"[PATCH 1/2] md bitmap bug fixes\" thread).\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "76186dd8b73d2b7b9b4c8629b89c845e97009801", "tree": "1f1c2fe5530de65fa149faa3e6b2969044e7b0a8", "parents": [ "02c2de8cc835885bdff51a8bfd6c0b659b969f50" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Oct 03 01:15:48 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Tue Oct 03 08:04:17 2006 -0700" }, "message": "[PATCH] md: remove \u0027working_disks\u0027 from raid10 state\n\nIt isn\u0027t needed as mddev-\u003edegraded contains equivalent info.\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "02c2de8cc835885bdff51a8bfd6c0b659b969f50", "tree": "3c3b3adf01e4ec4139888d681eca5becb3374fda", "parents": [ "850b2b420cd5b363ed4cf48a8816d656c8b5251b" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Oct 03 01:15:47 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Tue Oct 03 08:04:17 2006 -0700" }, "message": "[PATCH] md: remove the working_disks and failed_disks from raid5 state data.\n\nThey are not needed. conf-\u003efailed_disks is the same as mddev-\u003edegraded and\nconf-\u003eworking_disks is conf-\u003eraid_disks - mddev-\u003edegraded.\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "850b2b420cd5b363ed4cf48a8816d656c8b5251b", "tree": "b63aa37b3fb7dfb7a0b674d5a2ebe9da13cc7405", "parents": [ "6814d5368d68341ec6b5e4ecd10ea5947130775a" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Oct 03 01:15:46 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Tue Oct 03 08:04:17 2006 -0700" }, "message": "[PATCH] md: replace magic numbers in sb_dirty with well defined bit flags\n\nInstead of magic numbers (0,1,2,3) in sb_dirty, we have\nsome flags instead:\nMD_CHANGE_DEVS\n Some device state has changed requiring superblock update\n on all devices.\nMD_CHANGE_CLEAN\n The array has transitions from \u0027clean\u0027 to \u0027dirty\u0027 or back,\n requiring a superblock update on active devices, but possibly\n not on spares\nMD_CHANGE_PENDING\n A superblock update is underway.\n\nWe wait for an update to complete by waiting for all flags to be clear. A\nflag can be set at any time, even during an update, without risk that the\nchange will be lost.\n\nStop exporting md_update_sb - isn\u0027t needed.\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "b5c124af69119c1b5c1e728bd2e7b5b1fad9b7be", "tree": "7caf3a0fec3dfd4e4e9781aa67be9430f618ccf0", "parents": [ "fbedac04fa11d7f9f9f425c7ec253f55becaae57" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Tue Oct 03 01:15:45 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Tue Oct 03 08:04:16 2006 -0700" }, "message": "[PATCH] md: fix a comment that is wrong in raid5.h\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "fbedac04fa11d7f9f9f425c7ec253f55becaae57", "tree": "700b49b6ea0da293d07a6a32cc154347e134686f", "parents": [ "999d816851c3e080412a19558f111d01852d2f04" ], "author": { "name": "Adrian Bunk", "email": "bunk@stusta.de", "time": "Tue Oct 03 01:15:44 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Tue Oct 03 08:04:16 2006 -0700" }, "message": "[PATCH] md: the scheduled removal of the START_ARRAY ioctl for md\n\nThis patch contains the scheduled removal of the START_ARRAY ioctl for md.\n\nSigned-off-by: Adrian Bunk \u003cbunk@stusta.de\u003e\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "9361401eb7619c033e2394e4f9f6d410d6719ac7", "tree": "04b94a71f2366988c17740d1c16cfbdec41d5d2e", "parents": [ "d366e40a1cabd453be6e2609caa7e12f9ca17b1f" ], "author": { "name": "David Howells", "email": "dhowells@redhat.com", "time": "Sat Sep 30 20:45:40 2006 +0200" }, "committer": { "name": "Jens Axboe", "email": "axboe@nelson.home.kernel.dk", "time": "Sat Sep 30 20:52:31 2006 +0200" }, "message": "[PATCH] BLOCK: Make it possible to disable the block layer [try #6]\n\nMake it possible to disable the block layer. Not all embedded devices require\nit, some can make do with just JFFS2, NFS, ramfs, etc - none of which require\nthe block layer to be present.\n\nThis patch does the following:\n\n (*) Introduces CONFIG_BLOCK to disable the block layer, buffering and blockdev\n support.\n\n (*) Adds dependencies on CONFIG_BLOCK to any configuration item that controls\n an item that uses the block layer. This includes:\n\n (*) Block I/O tracing.\n\n (*) Disk partition code.\n\n (*) All filesystems that are block based, eg: Ext3, ReiserFS, ISOFS.\n\n (*) The SCSI layer. As far as I can tell, even SCSI chardevs use the\n \t block layer to do scheduling. Some drivers that use SCSI facilities -\n \t such as USB storage - end up disabled indirectly from this.\n\n (*) Various block-based device drivers, such as IDE and the old CDROM\n \t drivers.\n\n (*) MTD blockdev handling and FTL.\n\n (*) JFFS - which uses set_bdev_super(), something it could avoid doing by\n \t taking a leaf out of JFFS2\u0027s book.\n\n (*) Makes most of the contents of linux/blkdev.h, linux/buffer_head.h and\n linux/elevator.h contingent on CONFIG_BLOCK being set. sector_div() is,\n however, still used in places, and so is still available.\n\n (*) Also made contingent are the contents of linux/mpage.h, linux/genhd.h and\n parts of linux/fs.h.\n\n (*) Makes a number of files in fs/ contingent on CONFIG_BLOCK.\n\n (*) Makes mm/bounce.c (bounce buffering) contingent on CONFIG_BLOCK.\n\n (*) set_page_dirty() doesn\u0027t call __set_page_dirty_buffers() if CONFIG_BLOCK\n is not enabled.\n\n (*) fs/no-block.c is created to hold out-of-line stubs and things that are\n required when CONFIG_BLOCK is not set:\n\n (*) Default blockdev file operations (to give error ENODEV on opening).\n\n (*) Makes some /proc changes:\n\n (*) /proc/devices does not list any blockdevs.\n\n (*) /proc/diskstats and /proc/partitions are contingent on CONFIG_BLOCK.\n\n (*) Makes some compat ioctl handling contingent on CONFIG_BLOCK.\n\n (*) If CONFIG_BLOCK is not defined, makes sys_quotactl() return -ENODEV if\n given command other than Q_SYNC or if a special device is specified.\n\n (*) In init/do_mounts.c, no reference is made to the blockdev routines if\n CONFIG_BLOCK is not defined. This does not prohibit NFS roots or JFFS2.\n\n (*) The bdflush, ioprio_set and ioprio_get syscalls can now be absent (return\n error ENOSYS by way of cond_syscall if so).\n\n (*) The seclvl_bd_claim() and seclvl_bd_release() security calls do nothing if\n CONFIG_BLOCK is not set, since they can\u0027t then happen.\n\nSigned-Off-By: David Howells \u003cdhowells@redhat.com\u003e\nSigned-off-by: Jens Axboe \u003caxboe@kernel.dk\u003e\n" }, { "commit": "fadcfa33b6319a5faf8af2287f08bf93a7f926b6", "tree": "367e931ec64a88c20a4d15c351d4c7dbb1b7adf1", "parents": [ "47a5c6fa0e204a2b63309c648bb2fde36836c826" ], "author": { "name": "David Woodhouse", "email": "dwmw2@infradead.org", "time": "Tue Sep 19 12:43:58 2006 +0100" }, "committer": { "name": "David Woodhouse", "email": "dwmw2@infradead.org", "time": "Tue Sep 19 12:43:58 2006 +0100" }, "message": "[HEADERS] One line per header in Kbuild files to reduce conflicts\n\nSigned-off-by: David Woodhouse \u003cdwmw2@infradead.org\u003e\n" }, { "commit": "ff4e8d9a9f46e3a7f89d14ade52fe5d53a82c022", "tree": "e15fc4d8af0045a3947e3a25844773c6ee50289a", "parents": [ "0b8c9de05c2a860fe6b02fedcb48763bcee648b3" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jul 10 04:44:16 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Mon Jul 10 13:24:16 2006 -0700" }, "message": "[PATCH] md: fix resync speed calculation for restarted resyncs\n\nWe introduced \u0027io_sectors\u0027 recently so we could count the sectors that causes\nio during resync separate from sectors which didn\u0027t cause IO - there can be a\ndifference if a bitmap is being used to accelerate resync.\n\nHowever when a speed is reported, we find the number of sectors processed\nrecently by subtracting an oldish io_sectors count from a current\n\u0027curr_resync\u0027 count. This is wrong because curr_resync counts all sectors,\nnot just io sectors.\n\nSo, add a field to mddev to store the curren io_sectors separately from\ncurr_resync, and use that in the calculations.\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "6fa0cb1141da80eed4f86155fb51931bc1c31888", "tree": "df9b3c378ae4f44260eaae1a4b9d5c4ccf7bb641", "parents": [ "c6482dde1c2811afba289b2344268f850595f350", "257a5bdeb0441789d8e34e1b3e92b26d0f51bbf0" ], "author": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Tue Jul 04 12:55:45 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Tue Jul 04 12:55:45 2006 -0700" }, "message": "Merge git://git.infradead.org/hdrinstall-2.6\n\n* git://git.infradead.org/hdrinstall-2.6:\n Remove export of include/linux/isdn/tpam.h\n Remove \u003clinux/i2c-id.h\u003e and \u003clinux/i2c-algo-ite.h\u003e from userspace export\n Restrict headers exported to userspace for SPARC and SPARC64\n Add empty Kbuild files for \u0027make headers_install\u0027 in remaining arches.\n Add Kbuild file for Alpha \u0027make headers_install\u0027\n Add Kbuild file for SPARC \u0027make headers_install\u0027\n Add Kbuild file for IA64 \u0027make headers_install\u0027\n Add Kbuild file for S390 \u0027make headers_install\u0027\n Add Kbuild file for i386 \u0027make headers_install\u0027\n Add Kbuild file for x86_64 \u0027make headers_install\u0027\n Add Kbuild file for PowerPC \u0027make headers_install\u0027\n Add generic Kbuild files for \u0027make headers_install\u0027\n Basic implementation of \u0027make headers_check\u0027\n Basic implementation of \u0027make headers_install\u0027\n" }, { "commit": "42543769142d2375f2b5f8fc9cac999f84bd4c4c", "tree": "404606c37da872639111c5b641f07fff2ded1dff", "parents": [ "07d84d109d8beedd68df9da2e4e9f25c8217e7fb" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jun 26 00:27:57 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Mon Jun 26 09:58:39 2006 -0700" }, "message": "[PATCH] md: Don\u0027t write dirty/clean update to spares - leave them alone\n\n- record the \u0027event\u0027 count on each individual device (they\n might sometimes be slightly different now)\n- add a new value for \u0027sb_dirty\u0027: \u00273\u0027 means that the super\n block only needs to be updated to record a clean\u003c-\u003edirty\n transition.\n- Prefer odd event numbers for dirty states and even numbers\n for clean states\n- Using all the above, don\u0027t update the superblock on\n a spare device if the update is just doing a clean-dirty\n transition. To accomodate this, a transition from\n dirty back to clean might now decrement the events counter\n if nothing else has changed.\n\nThe net effect of this is that spare drives will not see any IO requests\nduring normal running of the array, so they can go to sleep if that is what\nthey want to do.\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "d785a06a0b9d0cd86b3cc1bf8e236e62af7b47ed", "tree": "7a238aedb0facb5c207a0477296e78b9ef7d551b", "parents": [ "acc55e220166a5ad898e66ad6153fd62eaaac76d" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jun 26 00:27:48 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Mon Jun 26 09:58:38 2006 -0700" }, "message": "[PATCH] md/bitmap: change md/bitmap file handling to use bmap to file blocks\n\nIf md is asked to store a bitmap in a file, it tries to hold onto the page\ncache pages for that file, manipulate them directly, and call a cocktail of\noperations to write the file out. I don\u0027t believe this is a supportable\napproach.\n\nThis patch changes the approach to use the same approach as swap files. i.e.\nbmap is used to enumerate all the block address of parts of the file and we\nwrite directly to those blocks of the device.\n\nswapfile only uses parts of the file that provide a full pages at contiguous\naddresses. We don\u0027t have that luxury so we have to cope with pages that are\nnon-contiguous in storage. To handle this we attach buffers to each page, and\nstore the addresses in those buffers.\n\nWith this approach the pagecache may contain data which is inconsistent with\nwhat is on disk. To alleviate the problems this can cause, md invalidates the\npagecache when releasing the file. If the file is to be examined while the\narray is active (a non-critical but occasionally useful function), O_DIRECT io\nmust be used. And new version of mdadm will have support for this.\n\nThis approach simplifies a lot of code:\n - we no longer need to keep a list of pages which we need to wait for,\n as the b_endio function can keep track of how many outstanding\n writes there are. This saves a mempool.\n - -EAGAIN returns from write_page are no longer possible (not sure if\n they ever were actually).\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "0b79ccf0cdd9f59e5f99017e1a5d23da336544b2", "tree": "8688d9810fcba1e24abce726eaf35ff32f6b58d9", "parents": [ "d7375ab324971e7acbea9f02a0269ae7348f4147" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jun 26 00:27:44 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Mon Jun 26 09:58:38 2006 -0700" }, "message": "[PATCH] md/bitmap: remove bitmap writeback daemon\n\nmd/bitmap currently has a separate thread to wait for writes to the bitmap\nfile to complete (as we cannot get a callback on that action).\n\nHowever this isn\u0027t needed as bitmap_unplug is called from process context and\nwaits for the writeback thread to do it\u0027s work. The same result can be\nachieved by doing the waiting directly in bitmap_unplug.\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "5e56341d029f0c2cf31e78dc01d4c861ba4d6a5e", "tree": "e77087a31d3d1b86c563fb4461f07ee642de280b", "parents": [ "c93983bf517c100a31e40ef087e19bd3d7aa2d28" ], "author": { "name": "Adrian Bunk", "email": "bunk@stusta.de", "time": "Mon Jun 26 00:27:42 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Mon Jun 26 09:58:37 2006 -0700" }, "message": "[PATCH] md: make md_print_devices() static\n\nThis patch makes the needlessly global md_print_devices() static.\n\nSigned-off-by: Adrian Bunk \u003cbunk@stusta.de\u003e\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "c93983bf517c100a31e40ef087e19bd3d7aa2d28", "tree": "9361c68d5f00ccd34cbc0a3bc7bc2389ce7f4c3a", "parents": [ "7c7546ccf6463edbeee8d9aac6de7be1cd80d08a" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jun 26 00:27:41 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Mon Jun 26 09:58:37 2006 -0700" }, "message": "[PATCH] md: support stripe/offset mode in raid10\n\nThe \"industry standard\" DDF format allows for a stripe/offset layout where\ndata is duplicated on different stripes. e.g.\n\n A B C D\n D A B C\n E F G H\n H E F G\n\n(columns are drives, rows are stripes, LETTERS are chunks of data).\n\nThis is similar to raid10\u0027s \u0027far\u0027 mode, but not quite the same. So enhance\n\u0027far\u0027 mode with a \u0027far/offset\u0027 option which follows the layout of DDFs\nstripe/offset.\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "7c7546ccf6463edbeee8d9aac6de7be1cd80d08a", "tree": "56c1f734db9f8a66a7c8c5ef11fb35e07dbb2f91", "parents": [ "5fd6c1dce06ec24ef3de20fe0c7ecf2ba9fe5ef9" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jun 26 00:27:41 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Mon Jun 26 09:58:37 2006 -0700" }, "message": "[PATCH] md: allow a linear array to have drives added while active\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "5fd6c1dce06ec24ef3de20fe0c7ecf2ba9fe5ef9", "tree": "bd7cc8c22615e8622d3d63b7fc68dcc3ac1964de", "parents": [ "a8a55c387da28d67d98f56e4f5021462cb61f7a6" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jun 26 00:27:40 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Mon Jun 26 09:58:37 2006 -0700" }, "message": "[PATCH] md: allow checkpoint of recovery with version-1 superblock\n\nFor a while we have had checkpointing of resync. The version-1 superblock\nallows recovery to be checkpointed as well, and this patch implements that.\n\nDue to early carelessness we need to add a feature flag to signal that the\nrecovery_offset field is in use, otherwise older kernels would assume that a\npartially recovered array is in fact fully recovered.\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "16a53ecc35f2a80dc285be2e769768847d89ca37", "tree": "19d005f19af68e9b98efaf16885bb60498f540c1", "parents": [ "16f17b39f385212b73278a76d482cdcaaebe6c02" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jun 26 00:27:38 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Mon Jun 26 09:58:37 2006 -0700" }, "message": "[PATCH] md: merge raid5 and raid6 code\n\nThere is a lot of commonality between raid5.c and raid6main.c. This patches\nmerges both into one module called raid456. This saves a lot of code, and\npaves the way for online raid5-\u003eraid6 migrations.\n\nThere is still duplication, e.g. between handle_stripe5 and handle_stripe6.\nThis will probably be cleaned up later.\n\nCc: \"H. Peter Anvin\" \u003chpa@zytor.com\u003e\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "8932c2e0dcae52e73430878fd8a7a7800176eada", "tree": "3b734ccaa0fb210f1fd76ff9bb6fb9700d1c4095", "parents": [ "c70810b327a247d12805554d0aa4605e257effb8" ], "author": { "name": "NeilBrown", "email": "neilb@suse.de", "time": "Mon Jun 26 00:27:36 2006 -0700" }, "committer": { "name": "Linus Torvalds", "email": "torvalds@g5.osdl.org", "time": "Mon Jun 26 09:58:36 2006 -0700" }, "message": "[PATCH] md: remove arbitrary limit on chunk size\n\nThe largest chunk size the code can support without substantial surgery is\n2^30 bytes, so make that the limit instead of an arbitrary 4Meg. Some day,\nthe \u0027chunksize\u0027 should change to a sector-shift instead of a byte-count. Then\nno limit would be needed.\n\nSigned-off-by: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@osdl.org\u003e\n" }, { "commit": "8555255f0b426858d8648c6206b70eb906cf4ec7", "tree": "3afe2ae27f6390bd6cb2350a578fafc690fa7803", "parents": [ "684753599afc76aa8f66c731bafb7204b39265b8" ], "author": { "name": "David Woodhouse", "email": "dwmw2@infradead.org", "time": "Sun Jun 18 12:14:01 2006 +0100" }, "committer": { "name": "David Woodhouse", "email": "dwmw2@infradead.org", "time": "Sun Jun 18 12:14:01 2006 +0100" }, "message": "Add generic Kbuild files for \u0027make headers_install\u0027\n\nThis adds the Kbuild files listing the files which are to be installed by\nthe \u0027headers_install\u0027 make target, in generic directories.\n\nSigned-off-by: David Woodhouse \u003cdwmw2@infradead.org\u003e\n" } ], "next": "6f91fe88e4e28b40b4f08d99e0ea6d17b70e9567" }