)]}'
{
  "commit": "692ebd17c2905313fff3c504c249c6a0faad16ec",
  "tree": "656c80512505d5b117bd01e25d66d88d7cfe9851",
  "parents": [
    "371d217ee1ff8b418b8f73fb2a34990f951ec2d4"
  ],
  "author": {
    "name": "Jan Kara",
    "email": "jack@suse.cz",
    "time": "Tue Sep 21 11:51:01 2010 +0200"
  },
  "committer": {
    "name": "Jens Axboe",
    "email": "jaxboe@fusionio.com",
    "time": "Wed Sep 22 09:48:47 2010 +0200"
  },
  "message": "bdi: Fix warnings in __mark_inode_dirty for /dev/zero and friends\n\nInodes of devices such as /dev/zero can get dirty for example via\nutime(2) syscall or due to atime update. Backing device of such inodes\n(zero_bdi, etc.) is however unable to handle dirty inodes and thus\n__mark_inode_dirty complains.  In fact, inode should be rather dirtied\nagainst backing device of the filesystem holding it. This is generally a\ngood rule except for filesystems such as \u0027bdev\u0027 or \u0027mtd_inodefs\u0027. Inodes\nin these pseudofilesystems are referenced from ordinary filesystem\ninodes and carry mapping with real data of the device. Thus for these\ninodes we have to use inode-\u003ei_mapping-\u003ebacking_dev_info as we did so\nfar. We distinguish these filesystems by checking whether sb-\u003es_bdi\npoints to a non-trivial backing device or not.\n\nExample: Assume we have an ext3 filesystem on /dev/sda1 mounted on /.\nThere\u0027s a device inode A described by a path \"/dev/sdb\" on this\nfilesystem. This inode will be dirtied against backing device \"8:0\"\nafter this patch. bdev filesystem contains block device inode B coupled\nwith our inode A. When someone modifies a page of /dev/sdb, it\u0027s B that\ngets dirtied and the dirtying happens against the backing device \"8:16\".\nThus both inodes get filed to a correct bdi list.\n\nCc: stable@kernel.org\nSigned-off-by: Jan Kara \u003cjack@suse.cz\u003e\nSigned-off-by: Jens Axboe \u003cjaxboe@fusionio.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "81e086d8aa5733c7a86a966827bf7ea18d29baa4",
      "old_mode": 33188,
      "old_path": "fs/fs-writeback.c",
      "new_id": "5581122bd2c00cd1f8727436c531bb5245b03b0a",
      "new_mode": 33188,
      "new_path": "fs/fs-writeback.c"
    }
  ]
}