)]}'
{
  "log": [
    {
      "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"
    }
  ]
}