)]}'
{
  "commit": "486bad2e40e938cd68fd853b7a9fa3115a9d3a4a",
  "tree": "498636e706df917e28e62844b16ef05299c2704a",
  "parents": [
    "b891e4a05ef6beac85465295a032431577c66b16"
  ],
  "author": {
    "name": "Jeff Layton",
    "email": "jlayton@redhat.com",
    "time": "Fri Dec 18 16:28:20 2009 -0500"
  },
  "committer": {
    "name": "Trond Myklebust",
    "email": "Trond.Myklebust@netapp.com",
    "time": "Fri Dec 18 16:28:20 2009 -0500"
  },
  "message": "sunrpc: on successful gss error pipe write, don\u0027t return error\n\nWhen handling the gssd downcall, the kernel should distinguish between a\nsuccessful downcall that contains an error code and a failed downcall\n(i.e. where the parsing failed or some other sort of problem occurred).\n\nIn the former case, gss_pipe_downcall should be returning the number of\nbytes written to the pipe instead of an error. In the event of other\nerrors, we generally want the initiating task to retry the upcall so\nwe set msg.errno to -EAGAIN. An unexpected error code here is a bug\nhowever, so BUG() in that case.\n\nSigned-off-by: Jeff Layton \u003cjlayton@redhat.com\u003e\nCc: stable@kernel.org\nSigned-off-by: Trond Myklebust \u003cTrond.Myklebust@netapp.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "3c3c50f38a1c4a773113db4f5388b27bc85453f8",
      "old_mode": 33188,
      "old_path": "net/sunrpc/auth_gss/auth_gss.c",
      "new_id": "66cb89c18347fdef7fe0271fefce3baa739fc2b6",
      "new_mode": 33188,
      "new_path": "net/sunrpc/auth_gss/auth_gss.c"
    }
  ]
}