)]}'
{
  "log": [
    {
      "commit": "151060ac13144208bd7601d17e4c92c59b98072f",
      "tree": "c93ba28042bcb7917c9098b449756cbe84fb0a51",
      "parents": [
        "08cbf542bf24fb0481a54526b177347ae4046f5e"
      ],
      "author": {
        "name": "Tejun Heo",
        "email": "tj@kernel.org",
        "time": "Tue Apr 14 10:54:54 2009 +0900"
      },
      "committer": {
        "name": "Miklos Szeredi",
        "email": "mszeredi@suse.cz",
        "time": "Tue Jun 09 11:24:11 2009 +0200"
      },
      "message": "CUSE: implement CUSE - Character device in Userspace\n\nCUSE enables implementing character devices in userspace.  With recent\nadditions of ioctl and poll support, FUSE already has most of what\u0027s\nnecessary to implement character devices.  All CUSE has to do is\nbonding all those components - FUSE, chardev and the driver model -\nnicely.\n\nWhen client opens /dev/cuse, kernel starts conversation with\nCUSE_INIT.  The client tells CUSE which device it wants to create.  As\nthe previous patch made fuse_file usable without associated\nfuse_inode, CUSE doesn\u0027t create super block or inodes.  It attaches\nfuse_file to cdev file-\u003eprivate_data during open and set ff-\u003efi to\nNULL.  The rest of the operation is almost identical to FUSE direct IO\ncase.\n\nEach CUSE device has a corresponding directory /sys/class/cuse/DEVNAME\n(which is symlink to /sys/devices/virtual/class/DEVNAME if\nSYSFS_DEPRECATED is turned off) which hosts \"waiting\" and \"abort\"\namong other things.  Those two files have the same meaning as the FUSE\ncontrol files.\n\nThe only notable lacking feature compared to in-kernel implementation\nis mmap support.\n\nSigned-off-by: Tejun Heo \u003ctj@kernel.org\u003e\nSigned-off-by: Miklos Szeredi \u003cmszeredi@suse.cz\u003e\n"
    }
  ]
}