)]}'
{
  "commit": "8c3916f4bdf9c8388bd70d0b399b3a43daf2087a",
  "tree": "738c44f56265c6fbca20ce8c7ec8aa655ce56803",
  "parents": [
    "9a38a83880c224c6a3fd973ac9ae30a043487f0f"
  ],
  "author": {
    "name": "Chuck Lever",
    "email": "chuck.lever@oracle.com",
    "time": "Fri Oct 03 17:15:23 2008 -0400"
  },
  "committer": {
    "name": "J. Bruce Fields",
    "email": "bfields@citi.umich.edu",
    "time": "Sat Oct 04 17:08:16 2008 -0400"
  },
  "message": "NLM: Always start both UDP and TCP listeners\n\nCommit 24e36663, which first appeared in 2.6.19, changed lockd so that\nthe client side starts a UDP listener only if there is a UDP NFSv2/v3\nmount.  Its description notes:\n\n    This... means that lockd will *not* listen on UDP if the only\n    mounts are TCP mount (and nfsd hasn\u0027t started).\n\n    The latter is the only one that concerns me at all - I don\u0027t know\n    if this might be a problem with some servers.\n\nUnfortunately it is a problem for Linux itself.  The rpc.statd daemon\non Linux uses UDP for contacting the local lockd, no matter which\nprotocol is used for NFS mounts.  Without a local lockd UDP listener,\nNFSv2/v3 lock recovery from Linux NFS clients always fails.\n\nRevert parts of commit 24e36663 so lockd_up() always starts both\nlisteners.\n\nSigned-off-by: Chuck Lever \u003cchuck.lever@oracle.com\u003e\nCc: Neil Brown \u003cneilb@suse.de\u003e\nSigned-off-by: J. Bruce Fields \u003cbfields@citi.umich.edu\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f013aed1153302ea4b23cdc1643f4f6cc3732263",
      "old_mode": 33188,
      "old_path": "fs/lockd/svc.c",
      "new_id": "36396fc058c5b14e988e829bdf80b4ec8075eaa8",
      "new_mode": 33188,
      "new_path": "fs/lockd/svc.c"
    }
  ]
}