)]}'
{
  "commit": "da3cc182f17c300a0c36478a3fc270cb4aa6012b",
  "tree": "e592fc1670f03fa72da1a23188a848a45f6cc30c",
  "parents": [
    "73cc84b76420783b1e820c11e72eb8df49da8a5c"
  ],
  "author": {
    "name": "Roman Arutyunyan",
    "email": "arut@nginx.com",
    "time": "Fri Jun 01 16:53:02 2018 +0300"
  },
  "committer": {
    "name": "Roman Arutyunyan",
    "email": "arut@nginx.com",
    "time": "Fri Jun 01 16:53:02 2018 +0300"
  },
  "message": "Events: fixed handling zero-length client address.\n\nOn Linux recvmsg() syscall may return a zero-length client address when\nreceiving a datagram from an unbound unix datagram socket.  It is usually\nassumed that socket address has at least the sa_family member.  Zero-length\nsocket address caused buffer over-read in functions which receive socket\naddress, for example ngx_sock_ntop().  Typically the over-read resulted in\nunexpected socket family followed by session close.  Now a fake socket address\nis allocated instead of a zero-length client address.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "77563709057474d9402e7d96b4a7d570249ad457",
      "old_mode": 33188,
      "old_path": "src/event/ngx_event_accept.c",
      "new_id": "7e9f742a0ccc00866006a68672bd72ee2cc46b92",
      "new_mode": 33188,
      "new_path": "src/event/ngx_event_accept.c"
    }
  ]
}