)]}'
{
  "commit": "18dca02aeb3c49dfce87c76be643b139d05cf647",
  "tree": "3e261efdba69b967500a36d8f65ac643c8693d76",
  "parents": [
    "34dc1ad752ad3f55b2a6e6cd8cfcf3504682fec7"
  ],
  "author": {
    "name": "Ricardo Labiaga",
    "email": "Ricardo.Labiaga@netapp.com",
    "time": "Wed Apr 01 09:22:53 2009 -0400"
  },
  "committer": {
    "name": "Benny Halevy",
    "email": "bhalevy@panasas.com",
    "time": "Wed Jun 17 12:43:45 2009 -0700"
  },
  "message": "nfs41: Add ability to read RPC call direction on TCP stream.\n\nNFSv4.1 callbacks can arrive over an existing connection. This patch adds\nthe logic to read the RPC call direction (call or reply). It does this by\nupdating the state machine to look for the call direction invoking\nxs_tcp_read_calldir(...) after reading the XID.\n\n[nfs41: Keep track of RPC call/reply direction with a flag]\n\nAs per 11/14/08 review of RFC 53/85.\n\nAdd a new flag to track whether the incoming message is an RPC call or an\nRPC reply.  TCP_RPC_REPLY is set in the \u0027struct sock_xprt\u0027 tcp_flags in\nxs_tcp_read_calldir() if the message is an RPC reply sent on the forechannel.\nIt is cleared if the message is an RPC request sent on the back channel.\n\nSigned-off-by: Ricardo Labiaga \u003cRicardo.Labiaga@netapp.com\u003e\nSigned-off-by: Benny Halevy \u003cbhalevy@panasas.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e1859614601350c219e23116978a2f40ccc9a96d",
      "old_mode": 33188,
      "old_path": "net/sunrpc/xprtsock.c",
      "new_id": "8975c10591c366ea38786b4566b4639aa9b7f101",
      "new_mode": 33188,
      "new_path": "net/sunrpc/xprtsock.c"
    }
  ]
}