)]}'
{
  "commit": "5c1469de7545a35a16ff2b902e217044a7d2f8a5",
  "tree": "2a3b48da4dab1516234633ee5e71766801210e49",
  "parents": [
    "812e876e842488221aa54cb4587a8a33445cfa9e"
  ],
  "author": {
    "name": "Eric W. Biederman",
    "email": "ebiederm@xmission.com",
    "time": "Sun Jun 13 03:28:03 2010 +0000"
  },
  "committer": {
    "name": "David S. Miller",
    "email": "davem@davemloft.net",
    "time": "Wed Jun 16 14:55:34 2010 -0700"
  },
  "message": "user_ns: Introduce user_nsmap_uid and user_ns_map_gid.\n\nDefine what happens when a we view a uid from one user_namespace\nin another user_namepece.\n\n- If the user namespaces are the same no mapping is necessary.\n\n- For most cases of difference use overflowuid and overflowgid,\n  the uid and gid currently used for 16bit apis when we have a 32bit uid\n  that does fit in 16bits.  Effectively the situation is the same,\n  we want to return a uid or gid that is not assigned to any user.\n\n- For the case when we happen to be mapping the uid or gid of the\n  creator of the target user namespace use uid 0 and gid as confusing\n  that user with root is not a problem.\n\nSigned-off-by: Eric W. Biederman \u003cebiederm@xmission.com\u003e\nAcked-by: Serge E. Hallyn \u003cserue@us.ibm.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "cc4f45361dbbc8a956f9a9fad2a865dc7f4add33",
      "old_mode": 33188,
      "old_path": "include/linux/user_namespace.h",
      "new_id": "8178156711f9f254c77452d8e3b4d25ded814f5e",
      "new_mode": 33188,
      "new_path": "include/linux/user_namespace.h"
    },
    {
      "type": "modify",
      "old_id": "b2d70d38dff454116a3cba9dee760981f298415b",
      "old_mode": 33188,
      "old_path": "kernel/user_namespace.c",
      "new_id": "25915832291acf2931d2ac7bbabdcad1c3cf3aee",
      "new_mode": 33188,
      "new_path": "kernel/user_namespace.c"
    }
  ]
}