)]}'
{
  "commit": "6e8fcbf64024f9056ba122abbb66554aa76bae5d",
  "tree": "61fec2bd4815d30110dc2ba7da3b7578fb08a0d8",
  "parents": [
    "acd6e00b8e4db542cb6bc9ddfbb4e18bbe29ce4d"
  ],
  "author": {
    "name": "Alexey Kuznetsov",
    "email": "kuznet@ms2.inr.ac.ru",
    "time": "Thu Aug 17 16:44:46 2006 -0700"
  },
  "committer": {
    "name": "David S. Miller",
    "email": "davem@davemloft.net",
    "time": "Thu Aug 17 16:44:46 2006 -0700"
  },
  "message": "[IPV4]: severe locking bug in fib_semantics.c\n\nFound in 2.4 by Yixin Pan \u003cyxpan@hotmail.com\u003e.\n\n\u003e When I read fib_semantics.c of Linux-2.4.32, write_lock(\u0026fib_info_lock) \u003d\n\u003e is used in fib_release_info() instead of write_lock_bh(\u0026fib_info_lock).  \u003d\n\u003e Is the following case possible: a BH interrupts fib_release_info() while \u003d\n\u003e holding the write lock, and calls ip_check_fib_default() which calls \u003d\n\u003e read_lock(\u0026fib_info_lock), and spin forever.\n\nSigned-off-by: Alexey Kuznetsov \u003ckuznet@ms2.inr.ac.ru\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9be53a8e72c338d7865dadcc747d6003cd1c8b20",
      "old_mode": 33188,
      "old_path": "net/ipv4/fib_semantics.c",
      "new_id": "51738000f3dc4c12c5db72063548b8535f7517e6",
      "new_mode": 33188,
      "new_path": "net/ipv4/fib_semantics.c"
    }
  ]
}