)]}'
{
  "commit": "1344a41637114485fac7afa1505bce2ff862807a",
  "tree": "cf8f84bee2b6e23a17e97beef53791a698256f77",
  "parents": [
    "c3a20692ca5c8eb8cf5d0f489d4fc839ce7593d1"
  ],
  "author": {
    "name": "Dave Johnson",
    "email": "djohnson+linux-kernel@sw.starentnetworks.com",
    "time": "Tue Aug 23 10:10:15 2005 -0700"
  },
  "committer": {
    "name": "David S. Miller",
    "email": "davem@davemloft.net",
    "time": "Tue Aug 23 10:10:15 2005 -0700"
  },
  "message": "[IPV4]: Fix negative timer loop with lots of ipv4 peers.\n\nFrom: Dave Johnson \u003cdjohnson+linux-kernel@sw.starentnetworks.com\u003e\n\nFound this bug while doing some scaling testing that created 500K inet\npeers.\n\npeer_check_expire() in net/ipv4/inetpeer.c isn\u0027t using inet_peer_gc_mintime\ncorrectly and will end up creating an expire timer with less than the\nminimum duration, and even zero/negative if enough active peers are\npresent.\n\nIf \u003e65K peers, the timer will be less than inet_peer_gc_mintime, and with\n\u003e70K peers, the timer duration will reach zero and go negative.\n\nThe timer handler will continue to schedule another zero/negative timer in\na loop until peers can be aged.  This can continue for at least a few\nminutes or even longer if the peers remain active due to arriving packets\nwhile the loop is occurring.\n\nBug is present in both 2.4 and 2.6.  Same patch will apply to both just\nfine.\n\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "95473953c406ebe2cc7217918381b5896f3ace66",
      "old_mode": 33188,
      "old_path": "net/ipv4/inetpeer.c",
      "new_id": "ab18a853d7ce3ca5249606af7f5a1660de6e5182",
      "new_mode": 33188,
      "new_path": "net/ipv4/inetpeer.c"
    }
  ]
}