)]}'
{
  "commit": "db04dc679bcc780ad6907943afe24a30de974a1b",
  "tree": "b90e13dc98a5217968a3035470d34744bf72d1c2",
  "parents": [
    "9141770548d529b9d32d5b08d59b65ee65afe0d4"
  ],
  "author": {
    "name": "Eric W. Biederman",
    "email": "ebiederm@xmission.com",
    "time": "Sat Mar 09 00:14:45 2013 -0800"
  },
  "committer": {
    "name": "Eric W. Biederman",
    "email": "ebiederm@xmission.com",
    "time": "Sat Mar 09 00:14:45 2013 -0800"
  },
  "message": "proc: Use nd_jump_link in proc_ns_follow_link\n\nUpdate proc_ns_follow_link to use nd_jump_link instead of just\nmanually updating nd.path.dentry.\n\nThis fixes the BUG_ON(nd-\u003einode !\u003d parent-\u003ed_inode) reported by Dave\nJones and reproduced trivially with mkdir /proc/self/ns/uts/a.\n\nSigh it looks like the VFS change to require use of nd_jump_link\nhappend while proc_ns_follow_link was baking and since the common case\nof proc_ns_follow_link continued to work without problems the need for\nmaking this change was overlooked.\n\nCc: stable@vger.kernel.org\nSigned-off-by: \"Eric W. Biederman\" \u003cebiederm@xmission.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b7a47196c8c3577e9cda96125a0157444128a7be",
      "old_mode": 33188,
      "old_path": "fs/proc/namespaces.c",
      "new_id": "66b51c0383da790c1219aa9716d484681f61cde8",
      "new_mode": 33188,
      "new_path": "fs/proc/namespaces.c"
    }
  ]
}