)]}'
{
  "commit": "fc54c65853dbfd2f70ff827b73344f9de4e4b501",
  "tree": "eba647feaa75df68b852b2d5d948e5ee5f7dbddf",
  "parents": [
    "d647a591dae06ccc96210cea938aa0342ef935fc"
  ],
  "author": {
    "name": "Pavel Emelyanov",
    "email": "xemul@openvz.org",
    "time": "Wed Apr 16 00:41:53 2008 -0700"
  },
  "committer": {
    "name": "David S. Miller",
    "email": "davem@davemloft.net",
    "time": "Wed Apr 16 00:41:53 2008 -0700"
  },
  "message": "[TUN]: Allow to register tun devices in namespace.\n\nThis is basically means that a net is set for a new device, but\nactually also involves two more steps:\n\n1. mark the tun device as \"local\", i.e. do not allow for it to\n   move across namespaces.\n\nThis is done so, since tun device is most often associated to some\nfile (and thus to some process) and moving the device alone is not\nvalid while keeping the file and the process outside. The need in \nability to move a detached persistent device is to be investigated \nlater.\n\n2. get the tun device\u0027s net when tun becomes attached and put one\n   when it becomes detached.\n\nThis is needed to handle the case when a task owning the tun dies,\nbut a files lives for some more time - in this case we must not\nallow for net to be freed, since its exit hook will spoil that file\u0027s\nprivate data by unregistering the tun from under tun_chr_close.\n\nSigned-off-by: Pavel Emelyanov \u003cxemul@openvz.org\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1e655ea631022353487b0a05e474fc1938b65d5e",
      "old_mode": 33188,
      "old_path": "drivers/net/tun.c",
      "new_id": "d91856b19f6fdaff4322576af492d107c2c8e8aa",
      "new_mode": 33188,
      "new_path": "drivers/net/tun.c"
    }
  ]
}