)]}'
{
  "commit": "c7d13c8faa74f4e8ef191f88a252cefab6805b38",
  "tree": "7735bcd0953efa72c57f5c53ee53d86986de0f0c",
  "parents": [
    "7ae189759cc48cf8b54beebff566e9fd2d4e7d7c"
  ],
  "author": {
    "name": "Yuchung Cheng",
    "email": "ycheng@google.com",
    "time": "Wed Jan 16 15:05:31 2019 -0800"
  },
  "committer": {
    "name": "David S. Miller",
    "email": "davem@davemloft.net",
    "time": "Thu Jan 17 15:12:26 2019 -0800"
  },
  "message": "tcp: properly track retry time on passive Fast Open\n\nThis patch addresses a corner issue on timeout behavior of a\npassive Fast Open socket.  A passive Fast Open server may write\nand close the socket when it is re-trying SYN-ACK to complete\nthe handshake. After the handshake is completely, the server does\nnot properly stamp the recovery start time (tp-\u003eretrans_stamp is\n0), and the socket may abort immediately on the very first FIN\ntimeout, instead of retying until it passes the system or user\nspecified limit.\n\nSigned-off-by: Yuchung Cheng \u003cycheng@google.com\u003e\nSigned-off-by: Eric Dumazet \u003cedumazet@google.com\u003e\nReviewed-by: Neal Cardwell \u003cncardwell@google.com\u003e\nReviewed-by: Soheil Hassas Yeganeh \u003csoheil@google.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1e61f0bd6e2431b39a188eef83945943cf92855f",
      "old_mode": 33188,
      "old_path": "net/ipv4/tcp_timer.c",
      "new_id": "074de38bafbda0c9bf753190d8d1b060face3527",
      "new_mode": 33188,
      "new_path": "net/ipv4/tcp_timer.c"
    }
  ]
}