)]}'
{
  "log": [
    {
      "commit": "dbd5768f87ff6fb0a4fe09c4d7b6c4a24de99430",
      "tree": "42ea94ea733538f797aa745945fc43c4d1b89217",
      "parents": [
        "7994e6f7254354e03028a11f98a27bd67dace9f1"
      ],
      "author": {
        "name": "Jan Kara",
        "email": "jack@suse.cz",
        "time": "Thu May 03 14:48:02 2012 +0200"
      },
      "committer": {
        "name": "Fengguang Wu",
        "email": "fengguang.wu@intel.com",
        "time": "Sun May 06 13:43:41 2012 +0800"
      },
      "message": "vfs: Rename end_writeback() to clear_inode()\n\nAfter we moved inode_sync_wait() from end_writeback() it doesn\u0027t make sense\nto call the function end_writeback() anymore. Rename it to clear_inode()\nwhich well says what the function really does - set I_CLEAR flag.\n\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\nSigned-off-by: Fengguang Wu \u003cfengguang.wu@intel.com\u003e\n"
    },
    {
      "commit": "bef41c267e2b903f411c0f56236027f68553b721",
      "tree": "ebbf53837c19c3dd55081b770f76e9a4aec9b001",
      "parents": [
        "c6e49e3f266dbe62773941dca8afa65f53b5415f"
      ],
      "author": {
        "name": "Al Viro",
        "email": "viro@zeniv.linux.org.uk",
        "time": "Tue Jul 26 03:07:49 2011 -0400"
      },
      "committer": {
        "name": "Al Viro",
        "email": "viro@zeniv.linux.org.uk",
        "time": "Tue Jan 03 22:55:05 2012 -0500"
      },
      "message": "exofs: propagate umode_t\n\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n"
    },
    {
      "commit": "bfe8684869601dacfcb2cd69ef8cfd9045f62170",
      "tree": "4e213aaa766b26f43f0f9ec7998a7745239d9377",
      "parents": [
        "6d6b77f163c7eabedbba00ed2abb7d4a570bff76"
      ],
      "author": {
        "name": "Miklos Szeredi",
        "email": "mszeredi@suse.cz",
        "time": "Fri Oct 28 14:13:29 2011 +0200"
      },
      "committer": {
        "name": "Christoph Hellwig",
        "email": "hch@serles.lst.de",
        "time": "Wed Nov 02 12:53:43 2011 +0100"
      },
      "message": "filesystems: add set_nlink()\n\nReplace remaining direct i_nlink updates with a new set_nlink()\nupdater function.\n\nSigned-off-by: Miklos Szeredi \u003cmszeredi@suse.cz\u003e\nTested-by: Toshiyuki Okajima \u003ctoshi.okajima@jp.fujitsu.com\u003e\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\n"
    },
    {
      "commit": "dd296619974c50c46c67e58f355a7e85ef3f0c01",
      "tree": "516eb00e50add1fe1cce74e8967857af5d41083e",
      "parents": [
        "769ba8d92025fa390f3097e658b8ed6e032d68e9"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Wed Oct 12 15:42:07 2011 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Mon Oct 24 17:22:28 2011 -0700"
      },
      "message": "exofs: Support for RAID5 read-4-write interface.\n\nThe ore need suplied a r4w_get_page/r4w_put_page API\nfrom Filesystem so it can get cache pages to read-into when\nwriting parial stripes.\n\nAlso I commented out and NULLed the .writepage (singular)\nvector. Because it gives terrible write pattern to raid\nand is apparently not needed. Even in OOM conditions the\nsystem copes (even better) with out it.\n\nTODO: How to specify to write_cache_pages() to start\n      or include a certain page?\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "4b46c9f5cf69505f0bc708995b88b0cc60317ffd",
      "tree": "e5369fe948509c230470f922a0cd89cda60f2692",
      "parents": [
        "5a51c0c7e9a913649aa65d8233470682bcbb7694"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Wed Sep 28 13:25:50 2011 +0300"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Fri Oct 14 18:54:42 2011 +0200"
      },
      "message": "ore/exofs: Change ore_check_io API\n\nCurrent ore_check_io API receives a residual\npointer, to report partial IO. But it is actually\nnot used, because in a multiple devices IO there\nis never a linearity in the IO failure.\n\nOn the other hand if every failing device is reported\nthrough a received callback measures can be taken to\nhandle only failed devices. One at a time.\n\nThis will also be needed by the objects-layout-driver\nfor it\u0027s error reporting facility.\n\nExofs is not currently using the new information and\nkeeps the old behaviour of failing the complete IO in\ncase of an error. (No partial completion)\n\nTODO: Use an ore_check_io callback to set_page_error only\nthe failing pages. And re-dirty write pages.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "5a51c0c7e9a913649aa65d8233470682bcbb7694",
      "tree": "4ed43b3a2f9fade227e098771a5bed66f6a71dc4",
      "parents": [
        "3bd9856857339d7ee8c4ad50030583f1b9415c39"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Wed Sep 28 13:18:45 2011 +0300"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Fri Oct 14 18:54:41 2011 +0200"
      },
      "message": "ore/exofs: Define new ore_verify_layout\n\nAll users of the ore will need to check if current code\nsupports the given layout. For example RAID5/6 is not\ncurrently supported.\n\nSo move all the checks from exofs/super.c to a new\nore_verify_layout() to be used by ore users.\n\nNote that any new layout should be passed through the\nore_verify_layout() because the ore engine will prepare\nand verify some internal members of ore_layout, and\nassumes it\u0027s called.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "154a9300cd87eee7538f356c9d339f06b0b1d257",
      "tree": "fc8f427a2db1a3817883f35048f0a62751083c36",
      "parents": [
        "6851a5e5c12b35f8bb8986d0ff16ca9be4cf2c09"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Fri Aug 26 21:00:32 2011 -0700"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Fri Oct 14 18:54:39 2011 +0200"
      },
      "message": "exofs: Support for short read/writes\n\nIf at read/write_done the actual IO was shorter then requested,\nreported in returned ios-\u003elength. It is not an error. The reminder\nof the pages should just be unlocked but not marked uptodate or\nend_page_writeback. They will be re issued later by the VFS.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "b916c5cd4d895a27b47a652648958f73e4f23ac6",
      "tree": "9fe6e59edd44119c79a18b9df0b02a0c4dacb6d1",
      "parents": [
        "d866d875f68fdeae63df334d291fe138dc636d96"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Wed Sep 28 11:55:51 2011 +0300"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Fri Oct 14 18:52:50 2011 +0200"
      },
      "message": "ore: Only IO one group at a time (API change)\n\nUsually a single IO is confined to one group of devices\n(group_width) and at the boundary of a raid group it can\nspill into a second group. Current code would allocate a\nfull device_table size array at each io_state so it can\ncomply to requests that span two groups. Needless to say\nthat is very wasteful, specially when device_table count\ncan get very large (hundreds even thousands), while a\ngroup_width is usually 8 or 10.\n\n* Change ore API to trim on IO that spans two raid groups.\n  The user passes offset+length to ore_get_rw_state, the\n  ore might trim on that length if spanning a group boundary.\n  The user must check ios-\u003elength or ios-\u003enrpages to see\n  how much IO will be preformed. It is the responsibility\n  of the user to re-issue the reminder of the IO.\n\n* Modify exofs To copy spilled pages on to the next IO.\n  This means one last kick is needed after all coalescing\n  of pages is done.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "5bf696dad4beecb6174e701c97e1f2574e6a2c96",
      "tree": "b4cfd7e00a61310aaf5ac90e670c840184fc115d",
      "parents": [
        "de74b05ace743b4a7aefad9e9b33ff899979b34a"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Wed Sep 28 11:39:59 2011 +0300"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Mon Oct 03 17:07:50 2011 +0200"
      },
      "message": "exofs: Rename struct ore_components comps \u003d\u003e oc\n\nore_components already has a comps member so this leads\nto things like comps-\u003ecomps which is annoying. the name oc\nwas already used in new code. So rename all old usage of\nore_components comps \u003d\u003e ore_components oc.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "8ff660ab85f524bdc7652eb5d38aaef1d66aa9c7",
      "tree": "c4a29cde4fc8654ae00e65cb520e13f9fe7f4e08",
      "parents": [
        "9e9db45649eb5d3ee5622fdad741914ecf1016a0"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sat Aug 06 19:26:31 2011 -0700"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sat Aug 06 19:36:18 2011 -0700"
      },
      "message": "exofs: Rename raid engine from exofs/ios.c \u003d\u003e ore\n\nORE stands for \"Objects Raid Engine\"\n\nThis patch is a mechanical rename of everything that was in ios.c\nand its API declaration to an ore.c and an osd_ore.h header. The ore\nengine will later be used by the pnfs objects layout driver.\n\n* File ios.c \u003d\u003e ore.c\n\n* Declaration of types and API are moved from exofs.h to a new\n  osd_ore.h\n\n* All used types are prefixed by ore_ from their exofs_ name.\n\n* Shift includes from exofs.h to osd_ore.h so osd_ore.h is\n  independent, include it from exofs.h.\n\nOther than a pure rename there are no other changes. Next patch\nwill move the ore into it\u0027s own module and will export the API\nto be used by exofs and later the layout driver\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "9e9db45649eb5d3ee5622fdad741914ecf1016a0",
      "tree": "19ab9e1431e3d6535cef3f2cba6fcff12bb6ba6c",
      "parents": [
        "85e44df4748670a1a7d8441b2d75843cdebc478a"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Fri Aug 05 15:06:04 2011 -0700"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sat Aug 06 19:35:32 2011 -0700"
      },
      "message": "exofs: ios: Move to a per inode components \u0026 device-table\n\nExofs raid engine was saving on memory space by having a single layout-info,\nsingle pid, and a single device-table, global to the filesystem. Then passing\na credential and object_id info at the io_state level, private for each\ninode. It would also devise this contraption of rotating the device table\nview for each inode-\u003eino to spread out the device usage.\n\nThis is not compatible with the pnfs-objects standard, demanding that\neach inode can have it\u0027s own layout-info, device-table, and each object\ncomponent it\u0027s own pid, oid and creds.\n\nSo: Bring exofs raid engine to be usable for generic pnfs-objects use by:\n\n* Define an exofs_comp structure that holds obj_id and credential info.\n\n* Break up exofs_layout struct to an exofs_components structure that holds a\n  possible array of exofs_comp and the array of devices + the size of the\n  arrays.\n\n* Add a \"comps\" parameter to get_io_state() that specifies the ids creds\n  and device array to use for each IO.\n\n  This enables to keep the layout global, but the device-table view, creds\n  and IDs at the inode level. It only adds two 64bit to each inode, since\n  some of these members already existed in another form.\n\n* ios raid engine now access layout-info and comps-info through the passed\n  pointers. Everything is pre-prepared by caller for generic access of\n  these structures and arrays.\n\nAt the exofs Level:\n\n* Super block holds an exofs_components struct that holds the device\n  array, previously in layout. The devices there are in device-table\n  order. The device-array is twice bigger and repeats the device-table\n  twice so now each inode\u0027s device array can point to a random device\n  and have a round-robin view of the table, making it compatible to\n  previous exofs versions.\n\n* Each inode has an exofs_components struct that is initialized at\n  load time, with it\u0027s own view of the device table IDs and creds.\n  When doing IO this gets passed to the io_state together with the\n  layout.\n\nWhile preforming this change. Bugs where found where credentials with the\nwrong IDs where used to access the different SB objects (super.c). As well\nas some dead code. It was never noticed because the target we use does not\ncheck the credentials.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "85e44df4748670a1a7d8441b2d75843cdebc478a",
      "tree": "c5bc0cdf7dad56cc6f3a38f99c88f62325a1e029",
      "parents": [
        "e1042ba0991aab80ced34f7dade6ec25f22b4304"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Mon May 16 15:26:47 2011 +0300"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sat Aug 06 19:35:31 2011 -0700"
      },
      "message": "exofs: Move exofs specific osd operations out of ios.c\n\nios.c will be moving to an external library, for use by the\nobjects-layout-driver. Remove from it some exofs specific functions.\n\nAlso g_attr_logical_length is used both by inode.c and ios.c\nmove definition to the later, to keep it independent\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "e1042ba0991aab80ced34f7dade6ec25f22b4304",
      "tree": "5953383f9235df91acfc2315a5c6fbdfb359ecf1",
      "parents": [
        "16f75bb35d54b44356f496272c013f7ace5fa698"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Tue Nov 16 20:09:58 2010 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sat Aug 06 19:35:31 2011 -0700"
      },
      "message": "exofs: Add offset/length to exofs_get_io_state\n\nIn future raid code we will need to know the IO offset/length\nand if it\u0027s a read or write to determine some of the array\nsizes we\u0027ll need.\n\nSo add a new exofs_get_rw_state() API for use when\nwriteing/reading. All other simple cases are left using the\nold way.\n\nThe major change to this is that now we need to call\nexofs_get_io_state later at inode.c::read_exec and\ninode.c::write_exec when we actually know these things. So this\npatch is kept separate so I can test things apart from other\nchanges.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "6c5103890057b1bb781b26b7aae38d33e4c517d8",
      "tree": "e6e57961dcddcb5841acb34956e70b9dc696a880",
      "parents": [
        "3dab04e6978e358ad2307bca563fabd6c5d2c58b",
        "9d2e157d970a73b3f270b631828e03eb452d525e"
      ],
      "author": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Thu Mar 24 10:16:26 2011 -0700"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Thu Mar 24 10:16:26 2011 -0700"
      },
      "message": "Merge branch \u0027for-2.6.39/core\u0027 of git://git.kernel.dk/linux-2.6-block\n\n* \u0027for-2.6.39/core\u0027 of git://git.kernel.dk/linux-2.6-block: (65 commits)\n  Documentation/iostats.txt: bit-size reference etc.\n  cfq-iosched: removing unnecessary think time checking\n  cfq-iosched: Don\u0027t clear queue stats when preempt.\n  blk-throttle: Reset group slice when limits are changed\n  blk-cgroup: Only give unaccounted_time under debug\n  cfq-iosched: Don\u0027t set active queue in preempt\n  block: fix non-atomic access to genhd inflight structures\n  block: attempt to merge with existing requests on plug flush\n  block: NULL dereference on error path in __blkdev_get()\n  cfq-iosched: Don\u0027t update group weights when on service tree\n  fs: assign sb-\u003es_bdi to default_backing_dev_info if the bdi is going away\n  block: Require subsystems to explicitly allocate bio_set integrity mempool\n  jbd2: finish conversion from WRITE_SYNC_PLUG to WRITE_SYNC and explicit plugging\n  jbd: finish conversion from WRITE_SYNC_PLUG to WRITE_SYNC and explicit plugging\n  fs: make fsync_buffers_list() plug\n  mm: make generic_writepages() use plugging\n  blk-cgroup: Add unaccounted time to timeslice_used.\n  block: fixup plugging stubs for !CONFIG_BLOCK\n  block: remove obsolete comments for blkdev_issue_zeroout.\n  blktrace: Use rq-\u003ecmd_flags directly in blk_add_trace_rq.\n  ...\n\nFix up conflicts in fs/{aio.c,super.c}\n"
    },
    {
      "commit": "1cea312ad49d9cb964179a784fedb1fcfe396283",
      "tree": "27c45af006b48b1a079698605ea9007398f652b5",
      "parents": [
        "9ed96484311b89360b80a4181d856cbdb21630fd"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Thu Feb 03 17:53:25 2011 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Tue Mar 15 15:02:51 2011 +0200"
      },
      "message": "exofs: Write sbi-\u003es_nextid as part of the Create command\n\nBefore when creating a new inode, we\u0027d set the sb-\u003es_dirt flag,\nand sometime later the system would write out s_nextid as part\nof the sb_info. Also on inode sync we would force the sb sync\nas well.\n\nDefine the s_nextid as a new partition attribute and set it\nevery time we create a new object.\nAt mount we read it from it\u0027s new place.\n\nWe now never set sb-\u003es_dirt anywhere in exofs. write_super\nis actually never called. The call to exofs_write_super from\nexofs_put_super is also removed because the VFS always calls\n-\u003esync_fs before calling -\u003eput_super twice.\n\nTo stay backward-and-forward compatible we also write the old\ns_nextid in the super_block object at unmount, and support zero\nlength attribute on mount.\n\nThis also fixes a BUG where in layouts when group_width was not\na divisor of EXOFS_SUPER_ID (0x10000) the s_nextid was not read\nfrom the device it was written to. Because of the sliding window\nlayout trick, and because the read was always done from the 0\ndevice but the write was done via the raid engine that might slide\nthe device view. Now we read and write through the raid engine.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "66cd6cad4919f980dd21307d0150ff251762a264",
      "tree": "4f2d9dc0f9070ce829d03097542e7968e02df41a",
      "parents": [
        "97178b7b6c84bd14660b89474d27931a1ea65c66"
      ],
      "author": {
        "name": "bharrosh@panasas.com",
        "email": "bharrosh@panasas.com",
        "time": "Thu Oct 07 14:28:18 2010 -0400"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Tue Mar 15 15:02:50 2011 +0200"
      },
      "message": "exofs: Override read-ahead to align on stripe_size\n\n* Set all inode-\u003ei_mapping-\u003ebacking_dev_info to point to\n  the per super-block sb-\u003es_bdi.\n\n* Calculating a read_ahead that is:\n  - preferable 2 stripes long\n    (Future patch will add a mount option to override this)\n  - Minimum 128K aligned up to stripe-size\n  - Caped to maximum-IO-sizes round down to stripe_size.\n    (Max sizes are governed by max bio-size that fits in a page\n     times number-of-devices)\n\nCC: Marc Dionne \u003cmarc.c.dionne@gmail.com\u003e\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "97178b7b6c84bd14660b89474d27931a1ea65c66",
      "tree": "b763cc48e6456b944e7bed877ad2a996809124eb",
      "parents": [
        "a8f1418f9e9bd4c487a7b703ff26c5dd5ceb2bf3"
      ],
      "author": {
        "name": "Nick Piggin",
        "email": "npiggin@kernel.dk",
        "time": "Thu Nov 25 12:47:15 2010 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Tue Mar 15 15:02:50 2011 +0200"
      },
      "message": "exofs: simple fsync race fix\n\nIt is incorrect to test inode dirty bits without participating in the inode\nwriteback protocol. Inode writeback sets I_SYNC and clears I_DIRTY_?, then\nwrites out the particular bits, then clears I_SYNC when it is done. BTW. it\nmay not completely write all pages out, so I_DIRTY_PAGES would get set\nagain.\n\nThis is a standard pattern used throughout the kernel\u0027s writeback caches\n(I_SYNC ~\u003d I_WRITEBACK, if that makes it clearer).\n\nAnd so it is not possible to determine an inode\u0027s dirty status just by\nchecking I_DIRTY bits. Especially not for the purpose of data integrity\nsyncs.\n\nMissing the check for these bits means that fsync can complete while\nwriteback to the inode is underway. Inode writeback functions get this\nright, so call into them rather than try to shortcut things by testing\ndirty state improperly.\n\nSigned-off-by: Nick Piggin \u003cnpiggin@kernel.dk\u003e\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "a8f1418f9e9bd4c487a7b703ff26c5dd5ceb2bf3",
      "tree": "9d72e1be99cf2eb4c8a35cfa8ac3df69dfbca01a",
      "parents": [
        "0a935519cca83f26dc15e7577fa6c2b39606a4ac"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Mon Nov 22 18:02:45 2010 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Tue Mar 15 15:02:49 2011 +0200"
      },
      "message": "exofs: Optimize read_4_write\n\nDon\u0027t attempt a read passed i_size, just zero the page and be\ndone with it.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "7eaceaccab5f40bbfda044629a6298616aeaed50",
      "tree": "33954d12f63e25a47eb6d86ef3d3d0a5e62bf752",
      "parents": [
        "73c101011926c5832e6e141682180c4debe2cf45"
      ],
      "author": {
        "name": "Jens Axboe",
        "email": "jaxboe@fusionio.com",
        "time": "Thu Mar 10 08:52:07 2011 +0100"
      },
      "committer": {
        "name": "Jens Axboe",
        "email": "jaxboe@fusionio.com",
        "time": "Thu Mar 10 08:52:07 2011 +0100"
      },
      "message": "block: remove per-queue plugging\n\nCode has been converted over to the new explicit on-stack plugging,\nand delay users have been converted to use the new API for that.\nSo lets kill off the old plugging along with aops-\u003esync_page().\n\nSigned-off-by: Jens Axboe \u003cjaxboe@fusionio.com\u003e\n"
    },
    {
      "commit": "0b0abeaf3d30cec03ac6497fe978b8f7edecc5ae",
      "tree": "6797384d6bbf617b6b1a6d5bb0a307c28c52798c",
      "parents": [
        "f2f1756d7de37cc8ca17705c5bc3dfcbfb589ab9"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Wed Feb 02 21:02:12 2011 +0200"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Wed Feb 02 17:53:27 2011 -0800"
      },
      "message": "Revert \"exofs: Set i_mapping-\u003ebacking_dev_info anyway\"\n\nThis reverts commit 115e19c53501edc11f730191f7f047736815ae3d.\n\nApparently setting inode-\u003ebdi to one\u0027s own sb-\u003es_bdi stops VFS from\nsending *read-aheads*.  This problem was bisected to this commit.  A\nrevert fixes it.  I\u0027ll investigate farther why is this happening for the\nnext Kernel, but for now a revert.\n\nI\u0027m sending to stable@kernel.org as well, since it exists also in\n2.6.37.  2.6.36 is good and does not have this patch.\n\nCC: Stable Tree \u003cstable@kernel.org\u003e\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n"
    },
    {
      "commit": "fe2fd9ed5bf184f797412be8b86f4589d1b77bb8",
      "tree": "45677902196a26d12a9eb56a663e0a9787cc2cae",
      "parents": [
        "571f7f46bf367b29f574ca51a9ca1db5035602bb"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sat Oct 16 19:14:01 2010 +1100"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Mon Oct 25 18:03:07 2010 +0200"
      },
      "message": "exofs: Remove inode-\u003ei_count manipulation in exofs_new_inode\n\nexofs_new_inode() was incrementing the inode-\u003ei_count and\ndecrementing it in create_done(), in a bad attempt to make sure\nthe inode will still be there when the asynchronous create_done()\nfinally arrives. This was very stupid because iput() was not called,\nand if it was actually needed, it would leak the inode.\n\nHowever all this is not needed, because at exofs_evict_inode()\nwe already wait for create_done() by waiting for the\nobject_created event. Therefore remove the superfluous ref counting\nand just Thicken the comment at exofs_evict_inode() a bit.\n\nWhile at it change places that open coded wait_obj_created()\nto call the already available wrapper.\n\nCC: Dave Chinner \u003cdchinner@redhat.com\u003e\nCC: Christoph Hellwig \u003chch@lst.de\u003e\nCC: Nick Piggin \u003cnpiggin@kernel.dk\u003e\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "571f7f46bf367b29f574ca51a9ca1db5035602bb",
      "tree": "39c8557d005982f7212c073b43027672c8e8e7ff",
      "parents": [
        "115e19c53501edc11f730191f7f047736815ae3d"
      ],
      "author": {
        "name": "Joe Perches",
        "email": "joe@perches.com",
        "time": "Thu Oct 21 22:17:17 2010 -0700"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Mon Oct 25 18:02:49 2010 +0200"
      },
      "message": "fs/exofs: typo fix of faild to failed\n\nSigned-off-by: Joe Perches \u003cjoe@perches.com\u003e\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "115e19c53501edc11f730191f7f047736815ae3d",
      "tree": "eddb72bc6ed53acf0bba8a98ebbda438b63997ae",
      "parents": [
        "7aebf4106b4263667696485303af498aa1eea9ef"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "Boaz Harrosh bharrosh@panasas.com",
        "time": "Thu Oct 07 14:28:18 2010 -0400"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Mon Oct 18 20:16:02 2010 +0200"
      },
      "message": "exofs: Set i_mapping-\u003ebacking_dev_info anyway\n\nThough it has been promised that inode-\u003ei_mapping-\u003ebacking_dev_info\nis not used and the supporting code is fine. Until the pointer\nwill default to NULL, I\u0027d rather it points to the correct thing\nregardless.\n\nAt least for future infrastructure coder it is a clear indication\nof where are the key points that inodes are initialized.\nI know because it took me time to find this out.\n\nSigned-off-by: Boaz Harrosh \u003cBoaz Harrosh bharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "7aebf4106b4263667696485303af498aa1eea9ef",
      "tree": "988dcd7a583f4c1d23032f2c866a0b997db2e6bb",
      "parents": [
        "cd07202cc8262e1669edff0d97715f3dd9260917"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "Boaz Harrosh bharrosh@panasas.com",
        "time": "Wed Oct 13 12:55:43 2010 -0400"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Mon Oct 18 20:16:02 2010 +0200"
      },
      "message": "exofs: Cleaup read path in regard with read_for_write\n\nLast BUG fix added a flag to the the page_collect structure\nto communicate with readpage_strip. This calls for a clean up\nremoving that flag\u0027s reincarnations in the read functions\nparameters.\n\nSigned-off-by: Boaz Harrosh \u003cBoaz Harrosh bharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "f17b1f9f1a5882e486aad469b9ac4cb18581707f",
      "tree": "fc8e1025ea9871d7ebe1aad63ce0c5fcb2bdf3ca",
      "parents": [
        "cb655d0f3d57c23db51b981648e452988c0223f9"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "Boaz Harrosh bharrosh@panasas.com",
        "time": "Thu Oct 07 13:37:51 2010 -0400"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "Boaz Harrosh bharrosh@panasas.com",
        "time": "Fri Oct 08 11:26:54 2010 -0400"
      },
      "message": "exofs: Fix double page_unlock BUG in write_begin/end\n\nThis BUG is there since the first submit of the code, but only triggered\nin last Kernel. It\u0027s timing related do to the asynchronous object-creation\nbehaviour of exofs. (Which should be investigated farther)\n\nThe bug is obvious hence the fixed.\n\nSigned-off-by: Boaz Harrosh \u003cBoaz Harrosh bharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "bf25db365428dbd182768baa9850bef7afaac80d",
      "tree": "4373037b00459643f0d661672eb6688f80800d72",
      "parents": [
        "682c30ed2165d5694a414d31eac7c63ac5700fb0",
        "5002dd18c5940ce63b917d84f2b852c3b96009bb"
      ],
      "author": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Wed Aug 11 09:19:43 2010 -0700"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Wed Aug 11 09:19:43 2010 -0700"
      },
      "message": "Merge branch \u0027for-linus\u0027 of git://git.open-osd.org/linux-open-osd\n\n* \u0027for-linus\u0027 of git://git.open-osd.org/linux-open-osd:\n  exofs: Fix groups code when num_devices is not divisible by group_width\n  exofs: Remove useless optimization\n  exofs: exofs_file_fsync and exofs_file_flush correctness\n  exofs: Remove superfluous dependency on buffer_head and writeback\n"
    },
    {
      "commit": "4ec70c9b46b032e7f1b41b543c607d6a33b78a1a",
      "tree": "ab2f2509a13845130fa0a3a28f4a9944bb761e05",
      "parents": [
        "845a2cc0507055278e0fa722ed0f8c791b7401dd"
      ],
      "author": {
        "name": "Al Viro",
        "email": "viro@zeniv.linux.org.uk",
        "time": "Mon Jun 07 11:42:26 2010 -0400"
      },
      "committer": {
        "name": "Al Viro",
        "email": "viro@zeniv.linux.org.uk",
        "time": "Mon Aug 09 16:48:24 2010 -0400"
      },
      "message": "convert exofs to -\u003eevict_inode()\n\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n"
    },
    {
      "commit": "2f246fd0f126f3b3c23a4e6b7109350e83356bd6",
      "tree": "10cc6c830e4ffcc116faaf886e72dd3f0b73d849",
      "parents": [
        "41cce647f8dbe26941bed2158fad0839aab7a294"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Wed Jun 09 18:23:18 2010 +0300"
      },
      "committer": {
        "name": "Al Viro",
        "email": "viro@zeniv.linux.org.uk",
        "time": "Mon Aug 09 16:47:41 2010 -0400"
      },
      "message": "exofs: New truncate sequence\n\nThese changes are crafted based on the similar\nconversion done to ext2 by Nick Piggin.\n\n* Remove the deprecated -\u003etruncate vector. Let exofs_setattr\n  take care of on-disk size updates.\n* Call truncate_pagecache on the unused pages if\n  write_begin/end fails.\n* Cleanup exofs_delete_inode that did stupid inode\n  writes and updates on an inode that will be\n  removed.\n* And finally get rid of exofs_get_block. We never\n  had any blocks it was all for calling nobh_truncate_page.\n  nobh_truncate_page is not actually needed in exofs since\n  the last page is complete and gone, just like all the other\n  pages. There is no partial blocks in exofs.\n\nI\u0027ve tested with this patch, and there are no apparent\nfailures, so far.\n\nCC: Nick Piggin \u003cnpiggin@suse.de\u003e\nCC: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n"
    },
    {
      "commit": "1025774ce411f2bd4b059ad7b53f0003569b74fa",
      "tree": "2be221c205cb5579652a6063e8ee27d1c72d1bbd",
      "parents": [
        "eef2380c187890816b73b1a4cb89a09203759469"
      ],
      "author": {
        "name": "Christoph Hellwig",
        "email": "hch@lst.de",
        "time": "Fri Jun 04 11:30:02 2010 +0200"
      },
      "committer": {
        "name": "Al Viro",
        "email": "viro@zeniv.linux.org.uk",
        "time": "Mon Aug 09 16:47:37 2010 -0400"
      },
      "message": "remove inode_setattr\n\nReplace inode_setattr with opencoded variants of it in all callers.  This\nmoves the remaining call to vmtruncate into the filesystem methods where it\ncan be replaced with the proper truncate sequence.\n\nIn a few cases it was obvious that we would never end up calling vmtruncate\nso it was left out in the opencoded variant:\n\n spufs: explicitly checks for ATTR_SIZE earlier\n btrfs,hugetlbfs,logfs,dlmfs: explicitly clears ATTR_SIZE earlier\n ufs: contains an opencoded simple_seattr + truncate that sets the filesize just above\n\nIn addition to that ncpfs called inode_setattr with handcrafted iattrs,\nwhich allowed to trim down the opencoded variant.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n"
    },
    {
      "commit": "85dc7878c6c2277de2eda2c4d1b11ea5c5b1068a",
      "tree": "dde1a55f77069b824b796420b1510b2547118cd3",
      "parents": [
        "3a09b1be53d23df780a0cd0e4087a05e2ca4a00c"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Mon May 31 18:55:43 2010 +0300"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Wed Aug 04 13:17:55 2010 +0300"
      },
      "message": "exofs: Remove superfluous dependency on buffer_head and writeback\n\nexofs_releasepage \u0026\u0026 exofs_invalidatepage are never called.\nLeave the WARN_ONs but remove any code. Remove the\n\ncleanup other stale #includes.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "0163916f1db7f345963dad1af78b7628c759c6ee",
      "tree": "c33e3551b7825e8700db65b8b27869f6f7d45c72",
      "parents": [
        "a69eee4988752c7196677958b4ed8f4c2b28499a",
        "ddf08f4b90a413892bbb9bb2e8a57aed991cd47d"
      ],
      "author": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Mon May 24 07:57:41 2010 -0700"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Mon May 24 07:57:41 2010 -0700"
      },
      "message": "Merge branch \u0027for-linus\u0027 of git://git.open-osd.org/linux-open-osd\n\n* \u0027for-linus\u0027 of git://git.open-osd.org/linux-open-osd:\n  exofs: confusion between kmap() and kmap_atomic() api\n  exofs: Add default address_space_operations\n"
    },
    {
      "commit": "e00117f14f68d9e54c8aa3d52ebdc76cdbbc4f87",
      "tree": "150ee8e968cef8bf448aaeff258a36c790db8856",
      "parents": [
        "ecc11fabf7ce16309112afe68fac466193ee7520"
      ],
      "author": {
        "name": "Dmitry Monakhov",
        "email": "dmonakhov@openvz.org",
        "time": "Thu Mar 04 17:31:48 2010 +0300"
      },
      "committer": {
        "name": "Al Viro",
        "email": "viro@zeniv.linux.org.uk",
        "time": "Fri May 21 18:31:23 2010 -0400"
      },
      "message": "exofs: replace inode uid,gid,mode initialization with helper function\n\nAck-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\nSigned-off-by: Dmitry Monakhov \u003cdmonakhov@openvz.org\u003e\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n"
    },
    {
      "commit": "200b0700420a78c3ade543761f0901985f41f96b",
      "tree": "521fd32425502856bf38d81e73f4cdf49103a80f",
      "parents": [
        "e40152ee1e1c7a63f4777791863215e3faa37a86"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Mon Mar 22 11:23:40 2010 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Mon May 17 13:50:50 2010 +0300"
      },
      "message": "exofs: Add default address_space_operations\n\nAll vectors of address_space_operations should be initialized\nby the filesystem. Add the missing parts.\n\nThis is actually an optimization, by using\n__set_page_dirty_nobuffers. The default, in case of NULL,\nwould be __set_page_dirty_buffers which has these extar if(s).\n\n.releasepage \u0026\u0026 .invalidatepage should both not be called\nbecause page_private() is NULL in exofs. Put a WARN_ON if\nthey are called, to indicate the Kernel has changed in this\nregard, if when it does.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "5a0e3ad6af8660be21ca98a971cd00f331318c05",
      "tree": "5bfb7be11a03176a87296a43ac6647975c00a1d1",
      "parents": [
        "ed391f4ebf8f701d3566423ce8f17e614cde9806"
      ],
      "author": {
        "name": "Tejun Heo",
        "email": "tj@kernel.org",
        "time": "Wed Mar 24 17:04:11 2010 +0900"
      },
      "committer": {
        "name": "Tejun Heo",
        "email": "tj@kernel.org",
        "time": "Tue Mar 30 22:02:32 2010 +0900"
      },
      "message": "include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h\n\npercpu.h is included by sched.h and module.h and thus ends up being\nincluded when building most .c files.  percpu.h includes slab.h which\nin turn includes gfp.h making everything defined by the two files\nuniversally available and complicating inclusion dependencies.\n\npercpu.h -\u003e slab.h dependency is about to be removed.  Prepare for\nthis change by updating users of gfp and slab facilities include those\nheaders directly instead of assuming availability.  As this conversion\nneeds to touch large number of source files, the following script is\nused as the basis of conversion.\n\n  http://userweb.kernel.org/~tj/misc/slabh-sweep.py\n\nThe script does the followings.\n\n* Scan files for gfp and slab usages and update includes such that\n  only the necessary includes are there.  ie. if only gfp is used,\n  gfp.h, if slab is used, slab.h.\n\n* When the script inserts a new include, it looks at the include\n  blocks and try to put the new include such that its order conforms\n  to its surrounding.  It\u0027s put in the include block which contains\n  core kernel includes, in the same order that the rest are ordered -\n  alphabetical, Christmas tree, rev-Xmas-tree or at the end if there\n  doesn\u0027t seem to be any matching order.\n\n* If the script can\u0027t find a place to put a new include (mostly\n  because the file doesn\u0027t have fitting include block), it prints out\n  an error message indicating which .h file needs to be added to the\n  file.\n\nThe conversion was done in the following steps.\n\n1. The initial automatic conversion of all .c files updated slightly\n   over 4000 files, deleting around 700 includes and adding ~480 gfp.h\n   and ~3000 slab.h inclusions.  The script emitted errors for ~400\n   files.\n\n2. Each error was manually checked.  Some didn\u0027t need the inclusion,\n   some needed manual addition while adding it to implementation .h or\n   embedding .c file was more appropriate for others.  This step added\n   inclusions to around 150 files.\n\n3. The script was run again and the output was compared to the edits\n   from #2 to make sure no file was left behind.\n\n4. Several build tests were done and a couple of problems were fixed.\n   e.g. lib/decompress_*.c used malloc/free() wrappers around slab\n   APIs requiring slab.h to be added manually.\n\n5. The script was run on all .h files but without automatically\n   editing them as sprinkling gfp.h and slab.h inclusions around .h\n   files could easily lead to inclusion dependency hell.  Most gfp.h\n   inclusion directives were ignored as stuff from gfp.h was usually\n   wildly available and often used in preprocessor macros.  Each\n   slab.h inclusion directive was examined and added manually as\n   necessary.\n\n6. percpu.h was updated not to include slab.h.\n\n7. Build test were done on the following configurations and failures\n   were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my\n   distributed build env didn\u0027t work with gcov compiles) and a few\n   more options had to be turned off depending on archs to make things\n   build (like ipr on powerpc/64 which failed due to missing writeq).\n\n   * x86 and x86_64 UP and SMP allmodconfig and a custom test config.\n   * powerpc and powerpc64 SMP allmodconfig\n   * sparc and sparc64 SMP allmodconfig\n   * ia64 SMP allmodconfig\n   * s390 SMP allmodconfig\n   * alpha SMP allmodconfig\n   * um on x86_64 SMP allmodconfig\n\n8. percpu.h modifications were reverted so that it could be applied as\n   a separate patch and serve as bisection point.\n\nGiven the fact that I had only a couple of failures from tests on step\n6, I\u0027m fairly confident about the coverage of this conversion patch.\nIf there is a breakage, it\u0027s likely to be something in one of the arch\nheaders which should be easily discoverable easily on most builds of\nthe specific arch.\n\nSigned-off-by: Tejun Heo \u003ctj@kernel.org\u003e\nGuess-its-ok-by: Christoph Lameter \u003ccl@linux-foundation.org\u003e\nCc: Ingo Molnar \u003cmingo@redhat.com\u003e\nCc: Lee Schermerhorn \u003cLee.Schermerhorn@hp.com\u003e\n"
    },
    {
      "commit": "a9185b41a4f84971b930c519f0c63bd450c4810d",
      "tree": "268cf4e206cca12fb9e1dd68984e7c190e465b46",
      "parents": [
        "26821ed40b4230259e770c9911180f38fcaa6f59"
      ],
      "author": {
        "name": "Christoph Hellwig",
        "email": "hch@lst.de",
        "time": "Fri Mar 05 09:21:37 2010 +0100"
      },
      "committer": {
        "name": "Al Viro",
        "email": "viro@zeniv.linux.org.uk",
        "time": "Fri Mar 05 13:25:52 2010 -0500"
      },
      "message": "pass writeback_control to -\u003ewrite_inode\n\nThis gives the filesystem more information about the writeback that\nis happening.  Trond requested this for the NFS unstable write handling,\nand other filesystems might benefit from this too by beeing able to\ndistinguish between the different callers in more detail.\n\nSigned-off-by: Christoph Hellwig \u003chch@lst.de\u003e\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n"
    },
    {
      "commit": "96391e2bae0f8882b6f44809202a68be66e91dce",
      "tree": "f2a6ece9b3973143293e1221e992c60b07109429",
      "parents": [
        "86093aaff5be5b214613eb60553e236bdb389c84"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Tue Feb 09 11:43:21 2010 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sun Feb 28 03:44:43 2010 -0800"
      },
      "message": "exofs: Error recovery if object is missing from storage\n\nIf an object is referenced by a directory but does not\nexist on a target, it is a very serious corruption that\nmeans:\n1. Either a power failure with very slim chance of it\n  happening. Because the directory update is always submitted\n  much after object creation, but if a directory is written\n  to one device and the object creation to another it might\n  theoretically happen.\n2. It only ever happened to me while developing with BUGs\n  causing file corruption. Crashes could also cause it but\n  they are more like case 1.\n\nIn any way the object does not exist, so data is surely lost.\nIf there is a mix-up in the obj-id or data-map, then lost objects\ncan be salvaged by off-line fsck. The only recoverable information\nis the directory name. By letting it appear as a regular empty file,\nwith date\u003d\u003d0 (1970 Jan 1st) ownership to root, we enable recovery\nof the only useful information. And also enable deletion or over-write.\nI can see how this can hurt.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "86093aaff5be5b214613eb60553e236bdb389c84",
      "tree": "64993f3fff8b60408441e8912aa5690346108492",
      "parents": [
        "5d952b8391692553c31e620a92d6e09262a9a307"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Thu Jan 28 18:24:06 2010 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sun Feb 28 03:44:42 2010 -0800"
      },
      "message": "exofs: convert io_state to use pages array instead of bio at input\n\n* inode.c operations are full-pages based, and not actually\n  true scatter-gather\n* Lets us use more pages at once upto 512 (from 249) in 64 bit\n* Brings us much much closer to be able to use exofs\u0027s io_state engine\n  from objlayout driver. (Once I decide where to put the common code)\n\nAfter RAID0 patch the outer (input) bio was never used as a bio, but\nwas simply a page carrier into the raid engine. Even in the simple\nmirror/single-dev arrangement pages info was copied into a second bio.\nIt is now easer to just pass a pages array into the io_state and prepare\nbio(s) once.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "5d952b8391692553c31e620a92d6e09262a9a307",
      "tree": "b3a1a0490fc98b6304685d64bb4774235ec94a2d",
      "parents": [
        "d9c740d2253e75db8cef8f87a3125c450f3ebd82"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Mon Feb 01 13:35:51 2010 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sun Feb 28 03:43:08 2010 -0800"
      },
      "message": "exofs: RAID0 support\n\nWe now support striping over mirror devices. Including variable sized\nstripe_unit.\n\nSome limits:\n* stripe_unit must be a multiple of PAGE_SIZE\n* stripe_unit * stripe_count is maximum upto 32-bit (4Gb)\n\nTested RAID0 over mirrors, RAID0 only, mirrors only. All check.\n\nDesign notes:\n* I\u0027m not using a vectored raid-engine mechanism yet. Following the\n  pnfs-objects-layout data-map structure, \"Mirror\" is just a private\n  case of \"group_width\" \u003d\u003d 1, and RAID0 is a private case of\n  \"Mirrors\" \u003d\u003d 1. The performance lose of the general case over the\n  particular special case optimization is totally negligible, also\n  considering the extra code size.\n\n* In general I added a prepare_stripes() stage that divides the\n  to-be-io pages to the participating devices, the previous\n  exofs_ios_write/read, now becomes _write/read_mirrors and a new\n  write/read upper layer loops on all devices calling\n  _write/read_mirrors. Effectively the prepare_stripes stage is the all\n  secret.\n  Also truncate need fixing to accommodate for striping.\n\n* In a RAID0 arrangement, in a regular usage scenario, if all inode\n  layouts will start at the same device, the small files fill up the\n  first device and the later devices stay empty, the farther the device\n  the emptier it is.\n\n  To fix that, each inode will start at a different stripe_unit,\n  according to it\u0027s obj_id modulus number-of-stripe-units. And\n  will then span all stripe-units in the same incrementing order\n  wrapping back to the beginning of the device table. We call it\n  a stripe-units moving window.\n\n  Special consideration was taken to keep all devices in a mirror\n  arrangement identical. So a broken osd-device could just be cloned\n  from one of the mirrors and no FS scrubbing is needed. (We do that\n  by rotating stripe-unit at a time and not a single device at a time.)\n\nTODO:\n We no longer verify object_length \u003d\u003d inode-\u003ei_size in exofs_iget.\n (since i_size is stripped on multiple objects now).\n I should introduce a multiple-device attribute reading, and use\n it in exofs_iget.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "d9c740d2253e75db8cef8f87a3125c450f3ebd82",
      "tree": "7217cf62b8d102e00257be6e0675d25852045bc6",
      "parents": [
        "46f4d973f6874c06b7a41a3bf8f4c1717d90f97a"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Thu Jan 28 11:58:08 2010 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sun Feb 28 03:35:28 2010 -0800"
      },
      "message": "exofs: Define on-disk per-inode optional layout attribute\n\n* Layouts describe the way a file is spread on multiple devices.\n  The layout information is stored in the objects attribute introduced\n  in this patch.\n\n* There can be multiple generating function for the layout.\n  Currently defined:\n    - No attribute present - use below moving-window on global\n      device table, all devices.\n      (This is the only one currently used in exofs)\n    - an obj_id generated moving window - the obj_id is a randomizing\n      factor in the otherwise global map layout.\n    - An explicit layout stored, including a data_map and a device\n      index list.\n    - More might be defined in future ...\n\n* There are two attributes defined of the same structure:\n  A-data-files-layout - This layout is used by data-files. If present\n                        at a directory, all files of that directory will\n                        be created with this layout.\n  A-meta-data-layout - This layout is used by a directory and other\n                       meta-data information. Also inherited at creation\n                       of subdirectories.\n\n* At creation time inodes are created with the layout specified above.\n  A usermode utility may change the creation layout on a give directory\n  or file. Which in the case of directories, will also apply to newly\n  created files/subdirectories, children of that directory.\n  In the simple unaltered case of a newly created exofs, no layout\n  attributes are present, and all layouts adhere to the layout specified\n  at the device-table.\n\n* In case of a future file system loaded in an old exofs-driver.\n  At iget(), the generating_function is inspected and if not supported\n  will return an IO error to the application and the inode will not\n  be loaded. So not to damage any data.\n  Note: After this patch we do not yet support any type of layout\n        only the RAID0 patch that enables striping at the super-block\n        level will add support for RAID0 layouts above. This way we\n        are past and future compatible and fully bisectable.\n\n* Access to the device table is done by an accessor since\n  it will change according to above information.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "45d3abcb1a7388b2b97582e13bf9dd21784dcaa5",
      "tree": "e957fdec303c073490c261999d6939c2ecf20352",
      "parents": [
        "22ddc556380cf5645c52292b6d980766646eb864"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Thu Jan 28 11:46:16 2010 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sun Feb 28 03:35:27 2010 -0800"
      },
      "message": "exofs: Move layout related members to a layout structure\n\n* Abstract away those members in exofs_sb_info that are related/needed\n  by a layout into a new exofs_layout structure. Embed it in exofs_sb_info.\n\n* At exofs_io_state receive/keep a pointer to an exofs_layout. No need for\n  an exofs_sb_info pointer, all we need is at exofs_layout.\n\n* Change any usage of above exofs_sb_info members to their new name.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "34ce4e7c23e3da578e459b05c6fb17edecb19e6b",
      "tree": "94713d94514b3d0e89dd05e727eaaae98369b28a",
      "parents": [
        "abe94c756c08d50566c09a65b9c7fe72f83071c5"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Tue Dec 15 19:34:17 2009 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sun Feb 28 03:35:25 2010 -0800"
      },
      "message": "exofs: debug print even less\n\n* Last debug trimming left in some stupid print, remove them.\n  Fixup some other prints\n* Shift printing from inode.c to ios.c\n* Add couple of prints when memory allocation fails.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "efd124b999fb4d426b30675f1684521af0872789",
      "tree": "f9421d61b3c4faf682fc1a52b72b241fa9b37558",
      "parents": [
        "89be503021f550575fc896671b569941140b2c2e"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sun Dec 27 17:01:42 2009 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Tue Jan 05 09:14:32 2010 +0200"
      },
      "message": "exofs: simple_write_end does not mark_inode_dirty\n\nexofs uses simple_write_end() for it\u0027s .write_end handler. But\nit is not enough because simple_write_end() does not call\nmark_inode_dirty() when it extends i_size. So even if we do\ncall mark_inode_dirty at beginning of write out, with a very\nlong IO and a saturated system we might get the .write_inode()\ncalled while still extend-writing to file and miss out on the last\ni_size updates.\n\nSo override .write_end, call simple_write_end(), and afterwords if\ni_size was changed call mark_inode_dirty().\n\nIt stands to logic that since simple_write_end() was the one extending\ni_size it should also call mark_inode_dirty(). But it looks like all\nusers of simple_write_end() are memory-bound pseudo filesystems, who\ncould careless about mark_inode_dirty(). I might submit a\nwarning-comment patch to simple_write_end() in future.\n\nCC: Stable \u003cstable@kernel.org\u003e\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "04dc1e88ad9c9f9639019e9646a89ce0ebf706bb",
      "tree": "403206d1e85e9e487d847694cbe0ecf111b3f02b",
      "parents": [
        "06886a5a3dc5a5abe0a4d257c26317bde7047be8"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Mon Nov 16 16:03:05 2009 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Thu Dec 10 09:59:23 2009 +0200"
      },
      "message": "exofs: Multi-device mirror support\n\nThis patch changes on-disk format, it is accompanied with a parallel\npatch to mkfs.exofs that enables multi-device capabilities.\n\nAfter this patch, old exofs will refuse to mount a new formatted FS and\nnew exofs will refuse an old format. This is done by moving the magic\nfield offset inside the FSCB. A new FSCB *version* field was added. In\nthe future, exofs will refuse to mount unmatched FSCB version. To\nup-grade or down-grade an exofs one must use mkfs.exofs --upgrade option\nbefore mounting.\n\nIntroduced, a new object that contains a *device-table*. This object\ncontains the default *data-map* and a linear array of devices\ninformation, which identifies the devices used in the filesystem. This\nobject is only written to offline by mkfs.exofs. This is why it is kept\nseparate from the FSCB, since the later is written to while mounted.\n\nSame partition number, same object number is used on all devices only\nthe device varies.\n\n* define the new format, then load the device table on mount time make\n  sure every thing is supported.\n\n* Change I/O engine to now support Mirror IO, .i.e write same data\n  to multiple devices, read from a random device to spread the\n  read-load from multiple clients (TODO: stripe read)\n\nImplementation notes:\n A few points introduced in previous patch should be mentioned here:\n\n* Special care was made so absolutlly all operation that have any chance\n  of failing are done before any osd-request is executed. This is to\n  minimize the need for a data consistency recovery, to only real IO\n  errors.\n\n* Each IO state has a kref. It starts at 1, any osd-request executed\n  will increment the kref, finally when all are executed the first ref\n  is dropped. At IO-done, each request completion decrements the kref,\n  the last one to return executes the internal _last_io() routine.\n  _last_io() will call the registered io_state_done. On sync mode a\n  caller does not supply a done method, indicating a synchronous\n  request, the caller is put to sleep and a special io_state_done is\n  registered that will awaken the caller. Though also in sync mode all\n  operations are executed in parallel.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "06886a5a3dc5a5abe0a4d257c26317bde7047be8",
      "tree": "858ac56e120c0473d764fc64a2660e6d79729c8c",
      "parents": [
        "8ce9bdd1fbe962933736d7977e972972cd5d754c"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sun Nov 08 14:54:08 2009 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Thu Dec 10 09:59:22 2009 +0200"
      },
      "message": "exofs: Move all operations to an io_engine\n\nIn anticipation for multi-device operations, we separate osd operations\ninto an abstract I/O API. Currently only one device is used but later\nwhen adding more devices, we will drive all devices in parallel according\nto a \"data_map\" that describes how data is arranged on multiple devices.\nThe file system level operates, like before, as if there is one object\n(inode-number) and an i_size. The io engine will split this to the same\nobject-number but on multiple device.\n\nAt first we introduce Mirror (raid 1) layout. But at the final outcome\nwe intend to fully implement the pNFS-Objects data-map, including\nraid 0,4,5,6 over mirrored devices, over multiple device-groups. And\nmore. See: http://tools.ietf.org/html/draft-ietf-nfsv4-pnfs-obj-12\n\n* Define an io_state based API for accessing osd storage devices\n  in an abstract way.\n  Usage:\n\tFirst a caller allocates an io state with:\n\t\texofs_get_io_state(struct exofs_sb_info *sbi,\n\t\t\t\t   struct exofs_io_state** ios);\n\n\tThen calles one of:\n\t\texofs_sbi_create(struct exofs_io_state *ios);\n\t\texofs_sbi_remove(struct exofs_io_state *ios);\n\t\texofs_sbi_write(struct exofs_io_state *ios);\n\t\texofs_sbi_read(struct exofs_io_state *ios);\n\t\texofs_oi_truncate(struct exofs_i_info *oi, u64 new_len);\n\n\tAnd when done\n\t\texofs_put_io_state(struct exofs_io_state *ios);\n\n* Convert all source files to use this new API\n* Convert from bio_alloc to bio_kmalloc\n* In io engine we make use of the now fixed osd_req_decode_sense\n\nThere are no functional changes or on disk additions after this patch.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "9cfdc7aa9f1b59627029ad00a58c3f59eb2cc383",
      "tree": "62b60dccb98ff71a332fbccd5f69e6a6416818c9",
      "parents": [
        "fe33cc1ee170c0e3b47ab9cbac07083b3446961c"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Tue Aug 04 20:40:29 2009 +0300"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Thu Dec 10 09:59:19 2009 +0200"
      },
      "message": "exofs: refactor exofs_i_info initialization into common helper\n\nThere are two places that initialize inodes: exofs_iget() and\nexofs_new_inode()\n\nAs more members of exofs_i_info that need initialization are\nadded this code will grow. (soon)\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "fe33cc1ee170c0e3b47ab9cbac07083b3446961c",
      "tree": "f90535189f375074f192b91eeaf59c4736cbf748",
      "parents": [
        "58311c43dfc3997a1f7b5883f827443f34108f8f"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sun Nov 01 18:28:14 2009 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Thu Dec 10 09:59:18 2009 +0200"
      },
      "message": "exofs: dbg-print less\n\nIner-loops printing is converted to EXOFS_DBG2 which is #defined\nto nothing.\n\nIt is now almost bareable to just leave debug-on. Every operation\nis printed once, with most relevant info (I hope).\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "58311c43dfc3997a1f7b5883f827443f34108f8f",
      "tree": "0d3630692a0fbb67afd117c562cac3f03ad6cefa",
      "parents": [
        "9f249162fbf1aea1335e13c57fd5355d00e07a47"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Tue Jul 14 11:06:08 2009 +0300"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Thu Dec 10 09:59:17 2009 +0200"
      },
      "message": "exofs: More sane debug print\n\ndebug prints should be somewhat useful without actually\nreading the source code\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "27d2e1491985e95c486d991302e399f5c584b4eb",
      "tree": "7f978b04cbabebe44108f246d7002c60ad9fdd35",
      "parents": [
        "b76a3f93d01fc93a87cb6eba4e854ffe378b4bac"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sun Jun 14 17:23:09 2009 +0300"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sun Jun 21 17:53:47 2009 +0300"
      },
      "message": "exofs: Remove IBM copyrights\n\nBoaz,\nCongrats on getting all the OSD stuff into 2.6.30!\nI just pulled the git, and saw that the IBM copyrights are still there.\nPlease remove them from all files:\n * Copyright (C) 2005, 2006\n * International Business Machines\n\nIBM has revoked all rights on the code - they gave it to me.\n\nThanks!\nAvishay\n\nSigned-off-by: Avishay Traeger \u003cavishay@gmail.com\u003e\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "b76a3f93d01fc93a87cb6eba4e854ffe378b4bac",
      "tree": "528b1a401be9b188cebf59850c2215d7260929aa",
      "parents": [
        "c277331d5fbaae5772ed19862feefa91f4e477d3"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Mon Jun 08 19:28:41 2009 +0300"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sun Jun 21 17:53:44 2009 +0300"
      },
      "message": "exofs: Fix bio leak in error handling path (sync read)\n\nWhen failing a read request in the sync path, called from\nwrite_begin, I forgot to free the allocated bio, fix it.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "fc2fac5b5f11e2bee3bf37215c8746236f5ea188",
      "tree": "1a76933892cd58d820558aa70a853fb590935e7d",
      "parents": [
        "62f469b596dd0aadf046a69027087c18db43734e"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sun May 24 20:04:43 2009 +0300"
      },
      "committer": {
        "name": "James Bottomley",
        "email": "James.Bottomley@HansenPartnership.com",
        "time": "Wed Jun 10 09:00:13 2009 -0500"
      },
      "message": "[SCSI] libosd: Define an osd_dev wrapper to retrieve the request_queue\n\nlibosd users that need to work with bios, must sometime use\nthe request_queue associated with the osd_dev. Make a wrapper for\nthat, and convert all in-tree users.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\nSigned-off-by: James Bottomley \u003cJames.Bottomley@HansenPartnership.com\u003e\n"
    },
    {
      "commit": "62f469b596dd0aadf046a69027087c18db43734e",
      "tree": "2e7fd67763b328fb47c3793e8a9d5a13ed49ea33",
      "parents": [
        "546881aea9787ed5c626ac99ab80158ea9ae0515"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sun May 24 20:04:26 2009 +0300"
      },
      "committer": {
        "name": "James Bottomley",
        "email": "James.Bottomley@HansenPartnership.com",
        "time": "Wed Jun 10 08:59:52 2009 -0500"
      },
      "message": "[SCSI] libosd: osd_req_{read,write} takes a length parameter\n\nFor supporting of chained-bios we can not inspect the first\nbio only, as before. Caller shall pass the total length of the\nrequest, ie. sum_bytes(bio-chain).\n\nAlso since the bio might be a chain we don\u0027t set it\u0027s direction\non behalf of it\u0027s callers. The bio direction should be properly\nset prior to this call. So fix a couple of write users that now\nneed to set the bio direction properly\n\n[In this patch I change both library code and user sites at\n exofs, to make it easy on integration. It should be submitted\n via James\u0027s scsi-misc tree.]\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\nCC: Jeff Garzik \u003cjeff@garzik.org\u003e\nSigned-off-by: James Bottomley \u003cJames.Bottomley@HansenPartnership.com\u003e\n"
    },
    {
      "commit": "ba9e5e98ca2f808fe92b103a8e6ce5271b10cc89",
      "tree": "0ec6eb23adfe0f762585e3a0c0f559bd91b74b11",
      "parents": [
        "e6af00f1d1697ca41ab6a55307066ef3466833a9"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Tue Oct 28 16:11:41 2008 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Tue Mar 31 19:44:34 2009 +0300"
      },
      "message": "exofs: super_operations and file_system_type\n\nThis patch ties all operation vectors into a file system superblock\nand registers the exofs file_system_type at module\u0027s load time.\n\n* The file system control block (AKA on-disk superblock) resides in\n  an object with a special ID (defined in common.h).\n  Information included in the file system control block is used to\n  fill the in-memory superblock structure at mount time. This object\n  is created before the file system is used by mkexofs.c It contains\n  information such as:\n\t- The file system\u0027s magic number\n\t- The next inode number to be allocated\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "e6af00f1d1697ca41ab6a55307066ef3466833a9",
      "tree": "7aa0b64f14a994f30e6bdc8e8c0b7f811038e794",
      "parents": [
        "beaec07ba6af35d387643b76a2920a7a6e22207b"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Tue Oct 28 15:38:12 2008 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Tue Mar 31 19:44:31 2009 +0300"
      },
      "message": "exofs: dir_inode and directory operations\n\nimplementation of directory and inode operations.\n\n* A directory is treated as a file, and essentially contains a list\n  of \u003cfile name, inode #\u003e pairs for files that are found in that\n  directory. The object IDs correspond to the files\u0027 inode numbers\n  and are allocated using a 64bit incrementing global counter.\n* Each file\u0027s control block (AKA on-disk inode) is stored in its\n  object\u0027s attributes. This applies to both regular files and other\n  types (directories, device files, symlinks, etc.).\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "beaec07ba6af35d387643b76a2920a7a6e22207b",
      "tree": "74ffd4738198424f698ae238e4d3164938ef5af7",
      "parents": [
        "982980d753223fda3864038236b7b94e246895cb"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Mon Oct 27 19:31:34 2008 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Tue Mar 31 19:44:29 2009 +0300"
      },
      "message": "exofs: address_space_operations\n\nOK Now we start to read and write from osd-objects. We try to\ncollect at most contiguous pages as possible in a single write/read.\nThe first page index is the object\u0027s offset.\n\nTODO:\n   In 64-bit a single bio can carry at most 128 pages.\n   Add support of chaining multiple bios\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "e806271916ed6068a0e3e4e9298dff0688b88e0d",
      "tree": "53669f4a55fecd82d289c035712d416e5b8dce35",
      "parents": [
        "b14f8ab2844987f013253dd04b708bde7fc1b52d"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Mon Oct 27 18:37:02 2008 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Tue Mar 31 19:44:24 2009 +0300"
      },
      "message": "exofs: file and file_inode operations\n\nimplementation of the file_operations and inode_operations for\nregular data files.\n\nMost file_operations are generic vfs implementations except:\n- exofs_truncate will truncate the OSD object as well\n- Generic file_fsync is not good for none_bd devices so open code it\n- The default for .flush in Linux is todo nothing so call exofs_fsync\n  on the file.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    }
  ]
}