)]}'
{
  "commit": "a930d8790552658140d7d0d2e316af4f0d76a512",
  "tree": "143e42bbaa41be61151389e386ba4cecc3bf6b3f",
  "parents": [
    "7c6baa304b841673d3a55ea4fcf9a5cbf7a1674b"
  ],
  "author": {
    "name": "Al Viro",
    "email": "viro@ZenIV.linux.org.uk",
    "time": "Tue Mar 12 02:59:49 2013 +0000"
  },
  "committer": {
    "name": "Linus Torvalds",
    "email": "torvalds@linux-foundation.org",
    "time": "Tue Mar 12 08:29:17 2013 -0700"
  },
  "message": "vfs: fix pipe counter breakage\n\nIf you open a pipe for neither read nor write, the pipe code will not\nadd any usage counters to the pipe, causing the \u0027struct pipe_inode_info\"\nto be potentially released early.\n\nThat doesn\u0027t normally matter, since you cannot actually use the pipe,\nbut the pipe release code - particularly fasync handling - still expects\nthe actual pipe infrastructure to all be there.  And rather than adding\nNULL pointer checks, let\u0027s just disallow this case, the same way we\nalready do for the named pipe (\"fifo\") case.\n\nThis is ancient going back to pre-2.4 days, and until trinity, nobody\nnaver noticed.\n\nReported-by: Dave Jones \u003cdavej@redhat.com\u003e\nSigned-off-by: Linus Torvalds \u003ctorvalds@linux-foundation.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "64a494cef0a00be57d0800637b71caf2537c2694",
      "old_mode": 33188,
      "old_path": "fs/pipe.c",
      "new_id": "2234f3f61f8d8fbc6a1f77dbaae6412130b8a5d4",
      "new_mode": 33188,
      "new_path": "fs/pipe.c"
    }
  ]
}