)]}'
{
  "commit": "118d5234636ca3718f47ca2c8a3b117c19dfdffd",
  "tree": "165c54e4e2079c7dab2446535f1e1510df0de783",
  "parents": [
    "d74a790d5237e7f56677030d932bc4f37ec36c92"
  ],
  "author": {
    "name": "Robert Shearman",
    "email": "rshearma@brocade.com",
    "time": "Thu Aug 06 11:04:56 2015 +0100"
  },
  "committer": {
    "name": "David S. Miller",
    "email": "davem@davemloft.net",
    "time": "Sun Aug 09 22:51:42 2015 -0700"
  },
  "message": "mpls: Enforce payload type of traffic sent using explicit NULL\n\nRFC 4182 s2 states that if an IPv4 Explicit NULL label is the only\nlabel on the stack, then after popping the resulting packet must be\ntreated as a IPv4 packet and forwarded based on the IPv4 header. The\nsame is true for IPv6 Explicit NULL with an IPv6 packet following.\n\nTherefore, when installing the IPv4/IPv6 Explicit NULL label routes,\nadd an attribute that specifies the expected payload type for use at\nforwarding time for determining the type of the encapsulated packet\ninstead of inspecting the first nibble of the packet.\n\nSigned-off-by: Robert Shearman \u003crshearma@brocade.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "04306989d05491ead0f83e1ab927b4f006302ff3",
      "old_mode": 33188,
      "old_path": "net/mpls/af_mpls.c",
      "new_id": "8c5707db53c5f6e33987b7215a4b3843c60cd610",
      "new_mode": 33188,
      "new_path": "net/mpls/af_mpls.c"
    }
  ]
}