)]}'
{
  "log": [
    {
      "commit": "25985edcedea6396277003854657b5f3cb31a628",
      "tree": "f026e810210a2ee7290caeb737c23cb6472b7c38",
      "parents": [
        "6aba74f2791287ec407e0f92487a725a25908067"
      ],
      "author": {
        "name": "Lucas De Marchi",
        "email": "lucas.demarchi@profusion.mobi",
        "time": "Wed Mar 30 22:57:33 2011 -0300"
      },
      "committer": {
        "name": "Lucas De Marchi",
        "email": "lucas.demarchi@profusion.mobi",
        "time": "Thu Mar 31 11:26:23 2011 -0300"
      },
      "message": "Fix common misspellings\n\nFixes generated by \u0027codespell\u0027 and manually reviewed.\n\nSigned-off-by: Lucas De Marchi \u003clucas.demarchi@profusion.mobi\u003e\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": "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": "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": "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": "0e35afbc8b054e04a35faa796c72abb3b82bd33b",
      "tree": "004a19d25dfc45cbbc88464e4e9d711b2027a668",
      "parents": [
        "de6b20385b1c14f97ccdf7da173b4c9a7405083b"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sun May 24 20:02:22 2009 +0300"
      },
      "committer": {
        "name": "James Bottomley",
        "email": "James.Bottomley@HansenPartnership.com",
        "time": "Wed Jun 10 08:57:07 2009 -0500"
      },
      "message": "[SCSI] libosd: osd_req_{read,write}_kern new API\n\nBy popular demand, define usefull wrappers for osd_req_read/write\nthat recieve kernel pointers. All users had their own.\n\nAlso remove these from exofs\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\nSigned-off-by: James Bottomley \u003cJames.Bottomley@HansenPartnership.com\u003e\n"
    },
    {
      "commit": "b14f8ab2844987f013253dd04b708bde7fc1b52d",
      "tree": "52af3569943e17a29d4ed08d2df37211d8dc7ea8",
      "parents": [
        "15f7176eb1cccec0a332541285ee752b935c1c85"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Mon Oct 27 18:27:55 2008 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Tue Mar 31 19:44:20 2009 +0300"
      },
      "message": "exofs: Kbuild, Headers and osd utils\n\nThis patch includes osd infrastructure that will be used later by\nthe file system.\n\nAlso the declarations of constants, on disk structures,\nand prototypes.\n\nAnd the Kbuild+Kconfig files needed to build the exofs module.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    }
  ]
}