)]}'
{
  "commit": "fa82a491275a613b15489aab4b99acecb00958d3",
  "tree": "1c5d1f5fb9d6c1870891bf088493541564b93bc9",
  "parents": [
    "b914152a6fbd2cd0441bc293ae8b3f3f1a9407b6"
  ],
  "author": {
    "name": "Jeff Layton",
    "email": "jlayton@redhat.com",
    "time": "Thu Jan 22 14:16:04 2009 -0500"
  },
  "committer": {
    "name": "J. Bruce Fields",
    "email": "bfields@pig.fieldses.org",
    "time": "Tue Jan 27 17:26:59 2009 -0500"
  },
  "message": "nfsd: only set file_lock.fl_lmops in nfsd4_lockt if a stateowner is found\n\nnfsd4_lockt does a search for a lockstateowner when building the lock\nstruct to test. If one is found, it\u0027ll set fl_owner to it. Regardless of\nwhether that happens, it\u0027ll also set fl_lmops. Given that this lock is\nbasically a \"lightweight\" lock that\u0027s just used for checking conflicts,\nsetting fl_lmops is probably not appropriate for it.\n\nThis behavior exposed a bug in DLM\u0027s GETLK implementation where it\nwasn\u0027t clearing out the fields in the file_lock before filling in\nconflicting lock info. While we were able to fix this in DLM, it\nstill seems pointless and dangerous to set the fl_lmops this way\nwhen we may have a NULL lockstateowner.\n\nSigned-off-by: Jeff Layton \u003cjlayton@redhat.com\u003e\nSigned-off-by: J. Bruce Fields \u003cbfields@pig.fieldses.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "88db7d3ec120dea33140e757a5ee30601baf220e",
      "old_mode": 33188,
      "old_path": "fs/nfsd/nfs4state.c",
      "new_id": "b6f60f48e94b4038473faf04b766ce706e60a9d4",
      "new_mode": 33188,
      "new_path": "fs/nfsd/nfs4state.c"
    }
  ]
}