)]}'
{
  "commit": "4629ed2e481b2af421ccb2ca3ba6e6b541789f5a",
  "tree": "56e58d926d4553ccb781eb270287ae6f200137e0",
  "parents": [
    "79dde73cf9bcf1dd317a2667f78b758e9fe139ed",
    "441fdee1eaf050ef0040bde0d7af075c1c6a6d8b"
  ],
  "author": {
    "name": "David S. Miller",
    "email": "davem@davemloft.net",
    "time": "Fri May 22 15:53:30 2020 -0700"
  },
  "committer": {
    "name": "David S. Miller",
    "email": "davem@davemloft.net",
    "time": "Fri May 22 15:53:30 2020 -0700"
  },
  "message": "Merge tag \u0027rxrpc-fixes-20200520\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs\n\nDavid Howells says:\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nrxrpc: Fix retransmission timeout and ACK discard\n\nHere are a couple of fixes and an extra tracepoint for AF_RXRPC:\n\n (1) Calculate the RTO pretty much as TCP does, rather than making\n     something up, including an initial 4s timeout (which causes return\n     probes from the fileserver to fail if a packet goes missing), and add\n     backoff.\n\n (2) Fix the discarding of out-of-order received ACKs.  We mustn\u0027t let the\n     hard-ACK point regress, nor do we want to do unnecessary\n     retransmission because the soft-ACK list regresses.  This is not\n     trivial, however, due to some loose wording in various old protocol\n     specs, the ACK field that should be used for this sometimes has the\n     wrong information in it.\n\n (3) Add a tracepoint to log a discarded ACK.\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n",
  "tree_diff": []
}
