)]}'
{
  "log": [
    {
      "commit": "8b56a30caaf9bc1850784f196636c5f550cc7577",
      "tree": "0e1be3d4f929a385c666fd7b269763f59fe215e5",
      "parents": [
        "6abe4a87f7bc7978705c386dbba0ca0c7790b3ec"
      ],
      "author": {
        "name": "Sachin Bhamare",
        "email": "sbhamare@panasas.com",
        "time": "Wed Mar 14 18:01:45 2012 -0700"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Mon May 21 12:24:01 2012 +0300"
      },
      "message": "exofs:  Add SYSFS info for autologin/pNFS export\n\nIntroduce sysfs infrastructure for exofs cluster filesystem.\n\nEach OSD target shows up as below in the sysfs hierarchy:\n\t/sys/fs/exofs/\u003cosdname\u003e_\u003cpartition_id\u003e/devX\n\nWhere \u003cosdname\u003e_\u003cpartition_id\u003e is the unique identification\nof a Superblock.\n\nWhere devX: 0 \u003c\u003d X \u003c device_table_size. They are ordered\nin device-table order as specified to the mkfs.exofs command\n\nEach OSD device  devX has following attributes :\n\tosdname - ReadOnly\n\tsystemid - ReadOnly\n\turi - Read/Write\n\nIt is up to user-mode to update devX/uri for support of\nautologin.\n\nThese sysfs information are used both for autologin as well\nas support for exporting exofs via a pNFSD server in user-mode.\n(.eg NFS-Ganesha)\n\nSigned-off-by: Sachin Bhamare \u003csbhamare@panasas.com\u003e\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "a1fec1dbbc8db974d2582e4040590cebe72171e4",
      "tree": "9dcbe1933b7f40256f40393f3c86dbb16e8fb953",
      "parents": [
        "3e335672e018c06e007f85a5d54afd721fb3d6d5"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Wed Oct 12 18:42:22 2011 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Mon Oct 24 16:55:36 2011 -0700"
      },
      "message": "ore: RAID5 read\n\nThis patch introduces the first stage of RAID5 support\nmainly the skip-over-raid-units when reading. For\nwrites it inserts BLANK units, into where XOR blocks\nshould be calculated and written to.\n\nIt introduces the new \"general raid maths\", and the main\nadditional parameters and components needed for raid5.\n\nSince at this stage it could corrupt future version that\nactually do support raid5. The enablement of raid5\nmounting and setting of parity-count \u003e 0 is disabled. So\nthe raid5 code will never be used. Mounting of raid5 is\nonly enabled later once the basic XOR write is also in.\nBut if the patch \"enable RAID5\" is applied this code has\nbeen tested to be able to properly read raid5 volumes\nand is according to standard.\n\nAlso it has been tested that the new maths still properly\nsupports RAID0 and grouping code just as before.\n(BTW: I have found more bugs in the pnfs-obj RAID math\n fixed here)\n\nThe ore.c file is getting too big, so new ore_raid.[hc]\nfiles are added that will include the special raid stuff\nthat are not used in striping and mirrors. In future write\nsupport these will get bigger.\nWhen adding the ore_raid.c to Kbuild file I was forced to\nrename ore.ko to libore.ko. Is it possible to keep source\nfile, say ore.c and module file ore.ko the same even if there\nare multiple files inside ore.ko?\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.com\u003e\n"
    },
    {
      "commit": "cf283ade08c454e884394a4720f22421dd33a715",
      "tree": "749bf95c36083fe35bdf020d71ab667283b486c4",
      "parents": [
        "8ff660ab85f524bdc7652eb5d38aaef1d66aa9c7"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sat Aug 06 19:22:06 2011 -0700"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Sat Aug 06 19:36:19 2011 -0700"
      },
      "message": "ore: Make ore its own module\n\nExport everything from ore need exporting. Change Kbuild and Kconfig\nto build ore.ko as an independent module. Import ore from exofs\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": "8ce9bdd1fbe962933736d7977e972972cd5d754c",
      "tree": "7fd0047737fe618be909f84f7a2364309fd3e5bf",
      "parents": [
        "cae012d8532879544326fff5fa2ae22a6dfe8e23"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Tue Nov 03 16:46:00 2009 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Thu Dec 10 09:59:21 2009 +0200"
      },
      "message": "exofs: move osd.c to ios.c\n\nIf I do a \"git mv\" together with a massive code change\nand commit in one patch, git looses the rename and\nrecords a delete/new instead. This is bad because I want\na rename recorded so later rebased/cherry-picked patches\nto the old name will work. Also the --follow is lost.\n\nSigned-off-by: Boaz Harrosh \u003cbharrosh@panasas.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": "982980d753223fda3864038236b7b94e246895cb",
      "tree": "c6140a49485c6b556860d69b8095ccb62f918b44",
      "parents": [
        "e806271916ed6068a0e3e4e9298dff0688b88e0d"
      ],
      "author": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Mon Oct 27 19:04:34 2008 +0200"
      },
      "committer": {
        "name": "Boaz Harrosh",
        "email": "bharrosh@panasas.com",
        "time": "Tue Mar 31 19:44:27 2009 +0300"
      },
      "message": "exofs: symlink_inode and fast_symlink_inode operations\n\nGeneric implementation of symlink ops.\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"
    },
    {
      "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"
    }
  ]
}