)]}'
{
  "commit": "9852a0e76cd9c89e71f84e784212fdd7a97ae93a",
  "tree": "e655477605be55176a99a01e14e3b60454bd2012",
  "parents": [
    "6610a0bc8dcc120daa1d93807d470d5cbf777c39"
  ],
  "author": {
    "name": "Andrew Morton",
    "email": "akpm@linux-foundation.org",
    "time": "Tue Oct 16 23:30:33 2007 -0700"
  },
  "committer": {
    "name": "Linus Torvalds",
    "email": "torvalds@woody.linux-foundation.org",
    "time": "Wed Oct 17 08:43:02 2007 -0700"
  },
  "message": "writeback: fix time ordering of the per superblock dirty inode lists: memory-backed inodes\n\nFor reasons which escape me, inodes which are dirty against a ram-backed\nfilesystem are managed in the same way as inodes which are backed by real\ndevices.\n\nProbably we could optimise things here.  But given that we skip the entire\nsupeblock as son as we hit the first dirty inode, there\u0027s not a lot to be\ngained.\n\nAnd the code does need to handle one particular non-backed superblock: the\nkernel\u0027s fake internal superblock which holds all the blockdevs.\n\nStill.  At present when the code encounters an inode which is dirty against a\nmemory-backed filesystem it will skip that inode by refiling it back onto\ns_dirty.  But it fails to update the inode\u0027s timestamp when doing so which at\nleast makes the debugging code upset.\n\nFix.\n\nCc: Mike Waychison \u003cmikew@google.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "08b9f83b645e6a1a33b07a489805c6da4bd45c2e",
      "old_mode": 33188,
      "old_path": "fs/fs-writeback.c",
      "new_id": "f8618e0bb62b327c2fc0141aba4687f566495656",
      "new_mode": 33188,
      "new_path": "fs/fs-writeback.c"
    }
  ]
}